u/Drysetcat

If you were on-call during the late-april opus 4.7 capacity squeeze, you probably already have opinions about this. If you were not, the short version: a lot of teams discovered mid-incident that what they had configured as failover was not actually functioning as a reliability mechanism.

Spent most of last weekend going through public post-mortems from teams that ran through it, partly to figure out whether our own posture would have held up. The pattern i kept seeing was that teams running through gateways found their gateway degrading in lockstep with the upstream it was proxying. The gateway did not have anywhere else to send the traffic, so it was effectively a more polished error returner. Some teams had multi-provider failover configured, but the failover only saved them if the secondary provider was healthy. During a few hours of the worst window, the major providers were degrading in correlated fashion.

This is making me think about gateways less as developer-convenience infrastructure and more as a serious dependency choice with the same kind of reliability questions you would ask of a database or a queue. Three concrete things i am now asking when i look at one.

Does the gateway hold any inference capacity itself, or is its entire serving capacity contingent on healthy upstreams? For workloads where a 30-minute degraded window is tolerable, pure-proxy is fine. For tier-1 inference, it is not. Some newer entrants keep their own compute on the back end as a degraded-mode fallback. Not frontier-class, not a substitute, but it converts service fully down into service in degraded mode where some quality drops but it still answers. Whether that distinction matters depends on what you are building.

What is the migration blast radius if you need to bypass the gateway entirely? Most gateways normalize traffic to a single api shape, which is useful until the incident requires hitting a provider direct. Then the normalization becomes a migration tax. We did not have a good answer for this in our runbook before april and i am still working on what the right one is.

Can you charge back by on-call team after the incident? If your gateway only gives you workspace-level rollups, you cannot answer which team consumed extra budget retrying through the degradation. That is a gap that quietly becomes a problem at scale.

I do not have a clean conclusion. Mostly april reminded me that reliability decisions for ai infra need to be made on the messy case. The gateway category is still maturing toward primitives that genuinely help under degradation rather than just under healthy load.

Would be useful to hear how teams here are writing runbooks for this failure mode specifically, especially the bilateral-degradation case where two upstreams are correlated. Mine still feels weak on it.

Spent the last six months accumulating ideas in a Notion doc like some kind of hoarder. Finally got sick of myself and decided to actually score them properly instead of just picking whatever felt exciting that week.

I took 20 sub niches that kept appearing in indie dev communities and Reddit threads, scraped competitor counts from G2 and Product Hunt, pulled search volume estimates, and scored everything on three axes (build difficulty, market saturation, solo dev fit, each 1 to 10). Ran the whole pipeline on a MuleRun agent overnight so I didn't have to sit there tabbing between 47 browser windows like a maniac.

The result that genuinely surprised me: AI writing tools scored dead last. Saturation 10 out of 10. Solo dev fit is abysmal because users expect constant model upgrades you can't deliver alone. The market is a bloodbath and it's only getting worse. If you're still considering this category, the data is screaming at you to stop.

Top scorer was niche specific invoice and proposal generators for freelancers in regulated industries. Think construction compliance docs, medical billing templates. Saturation scored 3 out of 10. Solo dev fit hit 9. The existing tools are all bloated horizontal SaaS that freelancers in these verticals actively hate. You don't even need to be clever here, just build the narrow version that actually works for their paperwork.

Second was micro analytics dashboards for Shopify stores doing under $50k per month. Triple Whale and Lifetimely price out small merchants, and the alternatives still require too much setup. There's a real gap for something dead simple that costs $9 a month and shows five numbers.

Third surprised me the most: lightweight tenant screening for small landlords with fewer than 10 units. I found exactly two tools targeting this segment specifically, both with mediocre reviews. Willingness to pay is real ($15 to $30 per screening), churn is naturally low, and the state by state regulatory complexity actually acts as a moat because big players don't want to bother with it for such a small TAM.

Changelog generators pulling from GitHub and Linear seemed wide open until I counted 8 to 10 competitors already. The twist: review timestamps suggest most users churn within 3 months. So either the category is fundamentally broken or every existing solution just sucks. Haven't decided which.

The pattern was almost comically consistent. Every niche that would get engagement on Twitter ("AI powered X", "creator economy tool", "social media scheduler") scored worst on the composite. The stuff you'd never post about publicly, regulated industries, small landlords, local service compliance, scored best. I'm now building in one of the top 5 and honestly the boringness of it feels like a competitive advantage in itself.

Over the past few years i've tried way too many random online side hustles. I tried print-on-demand because youtube made it sound like free passive income. Instead i spent weekends choosing t-shirt fonts and got zero sales. Then i tried making notion templates even though i barely used notion myself. I remember spending more time designing the logo and landing page than actually building templates. After that came reselling, which mostly turned my apartment into a mini warehouse. At one point i had boxes stacked next to my bed and started using inventory as a nightstand. Honestly the funniest part is how attached you become to products once you buy inventory yourself. Suddenly every cheap desk organizer becomes a "premium productivity solution" in your head. Eventually i realized the only side hustles i could stick with were the ones where i actually enjoyed researching products and spotting things people wanted.

Once i stopped obsessing over finding the "perfect business idea," things became way less stressful. I also learned supplier research gets messy really fast once you test multiple products

At one point i had screenshots, spreadsheets, bookmarks, supplier chats, and random notes everywhere. Still not making life-changing money or anything, but at least now i treat side hustles more like experiments instead of huge life decisions. Honestly i think that mindset shift helped more than any youtube tutorial ever did.

Every time I try to snag a deal on figures from japan the proxy fees chip away at the savings. Buyee wants 500 yen per item now. ZenMarket is supposedly cheaper but their shipping quotes always end up higher than expected somehow. FromJapan has some commission structure I still can't fully make sense of.

Most of what I buy is prize figures and smaller scale stuff from Mercari Japan, usually 1,500 to 3,000 yen range. At that price the proxy fee is a real chunk of the total. Consolidating helps spread the international shipping across more items but it doesn't touch the per-item fees.

Went down a rabbit hole comparing proxy fee pages last week and Onemall stood out with 200 yen per item and apparently free-fee coupons sometimes. If that's real and the shipping rates aren't inflated to make up for it, it changes the math on bigger hauls. But I haven't actually placed an order through them so who knows.

I've been burned before by services that look cheap up front then tack on fees for photos, storage, special packaging, whatever else they can think of. So I don't take advertised prices at face value anymore.

Honestly at this point I just want to see a real receipt comparison, not marketing pages. Per-item fees are one thing but the final shipping invoice is where I always end up surprised.