Real incident · March 2026 · r/googlecloud
$128K in unauthorized API charges.
Refund denied.
Every AI agent you run without spend limits is a blank check with no signature. Solwyn adds hard caps, provider failover, and per-agent attribution — setup takes 90 seconds.
REAL INCIDENTS. REAL INVOICES.
A small company in Japan discovered unauthorized usage of their Gemini API. Charges were already $44K when they noticed. Even after pausing the API, the total climbed to $128K. Google denied the adjustment. The company is now facing bankruptcy.
A 4-person startup shipped a LangChain agent on a Friday. The recursive loop ran for 11 days. The CEO found out from the AWS billing alert — not the engineering team. A $100/day cap would have stopped it at $100.
A staging environment was accidentally left running alongside production for three weeks. Same agents, same traffic, double the bill. A per-project budget would have caught it on day one.
Every one of these was preventable. That's the point.
Five minutes between you and a $47,000 mistake.
No infrastructure changes. No proxy. No new dependencies. Just a wrapper around the client you already use.
Deploy an agent, cross your fingers, check the bill next month.
Deploy an agent that can't spend more than you allow, fails over automatically, and reports every dollar.
Set the limit before the damage starts.
Daily, weekly, or monthly budgets per project. Alert-only mode keeps agents running while you get notified. Hard-deny mode kills the request before it reaches the provider. The SDK enforces caps locally — even if Solwyn's cloud is unreachable, your limits still hold.
When your provider goes down, your agents don't.
The SDK routes to your configured fallback automatically — client-side, no server in the loop. A local circuit breaker tracks provider health and switches in milliseconds. Your users experience zero downtime. You don't get paged.
The agent burning money has a name.
Per-project cost breakdown by model and time period. Real-time spend vs. budget. Trend indicators that show you where costs are accelerating before they become a problem. All powered by metadata — your prompts never leave your environment.
| PROJECT | MODEL | 7D COST | TREND |
|---|---|---|---|
| search-agent | gpt-4.1 | $142.30 | ↑ 23% |
| chat-bot | claude-4-sonnet | $87.50 | ↓ 12% |
| summarizer | gemini-2.5-flash | $12.80 | → flat |
Your prompts never touch our servers.
Not by policy. By architecture.
Solwyn runs inside your process — your LLM calls go straight to the provider, and we're never in the path.
- ✓Token count
- ✓Model
- ✓Cost
- ✓Latency
- ✓Status
- ✓Project ID
- ✕Prompts
- ✕Responses
- ✕System messages
- ✕Function calls
- ✕Conversation history
- ✕Any content whatsoever
We can't leak what we never had.
The dashcam vs. the brakes.
Other tools watch. Solwyn prevents.
Helicone, Portkey, LiteLLM
Every call routes through their servers. They see your prompts. They add latency. When they go down, you go down.
LangSmith, Langfuse
Great dashboards — after the damage. A recursive agent burns $47K overnight. The dashboard shows you the fire. It doesn't stop it.
Local SDK. Budgets enforced before the request leaves your app. Failover handled client-side. Only metadata reaches us.
Your prompts never leave. Ever.
“I built Solwyn after watching a client's staging environment silently double their AI bill for three weeks. The tools that existed could show you the dashboard after the damage was done. None of them could stop it. That's the product I couldn't find, so I built it.”
$47,000 bills don't wait for Monday.
Wrap your client. Set a cap. Deploy. Free tier includes 5,000 requests — no credit card, no sales call, no prompts transmitted.
Start Free Now30-day money-back guarantee on all paid plans. Refund policy