SOLWYN

Plans & billing

What each tier gates, and how upgrades, downgrades, and the Stripe portal work.

Solwyn has four tiers — Free, Production, Team, and Scale. Settings → Billing shows your current plan, the comparison table, and Manage Subscription. Current prices live on the billing page itself; the table below documents what each tier gates.

What each tier gates

GateFreeProductionTeamScale
Seats12525
Projects310UnlimitedUnlimited
Requests / month5,00050,000500,0005,000,000
API keys (per account)325100Unlimited
Webhook targets per project—35Unlimited
Hard-cap (hard_deny) projects1UnlimitedUnlimitedUnlimited
Budget periodsMonthlyDaily / weekly / monthlyDaily / weekly / monthlyDaily / weekly / monthly
Alert/budget rules per project11010Unlimited
Account spend cap—✓✓✓
Analytics ranges7d, 30d7d, 30d7d, 30d, 90d7d, 30d, 90d, 365d
Analytics group-byday, model, provider, agent runday, model, provider, agent run+ status, service tier, region, failover reason, tag:<key>same as Team
CSV export—AggregatedFullFull
Notification channelsEmail (budget events only)+ Webhooks, Slack, PagerDuty, Teams, Discord, Telegram, SMS — every event typesame as Productionsame as Production
Provider failover*——✓✓
Data retention30 days90 days180 days365 days
Ingest rate limit5 req/s50 req/s200 req/s1,000 req/s

* Custom failover and circuit-breaker tuning is a separate, plan-scoped entitlement available on Team and Scale, not bundled automatically with Provider failover access. On plans without that entitlement, SDK v0.3.0+ applies safe defaults in place of your configured tuning — advisory only, so calls never fail for lack of it. See Failover tuning.

The API-key row counts live keys across the whole account, whatever projects they reach. A key in its rotation overlap window does not count; its replacement does. Creating a key or a project (which creates its first key) past the limit returns 402 with code: "api_key_limit_reached". Revoke a key or upgrade. Settings > API keys shows how many you use.

Two request limits behave differently at the ceiling:

  • Free has no overage, and nothing stops running. Requests count per UTC calendar month, across every project you belong to (archived ones included), and a budget-denied call counts too. Past 5,000, Solwyn keeps accepting and storing your events, budget checks and your hard cap keep enforcing, and budget alerts keep firing. Cost analytics reads stop: they return HTTP 402 until the month rolls over or you upgrade. The dashboard shows a quota banner on the overview, and you get one warning email per month at 80%.
  • Paid tiers bill overage instead: requests beyond the included volume are metered and charged, so nothing is withheld mid-month.

Free past 5,000 requests

These reads return 402 with code: "quota_exceeded":

  • GET /api/v1/projects/{project_id}/costs, /costs/total, /costs/events, /costs/export, /costs/drift, and /costs/priced-models
  • POST /api/v1/projects/{project_id}/costs/simulate
  • GET /api/v1/account/costs, except group_by=project

GET /api/v1/account/costs?group_by=project stays 200 so budget gauges keep working. It sets analytics_withheld: true, keeps each row's group_key, project_name and current_period_cost, returns an empty daily list, and zeroes every other analytics field. Don't render the zeroed fields.

Ingest, budget checks, budgets, alerts, alert events, agent runs and the overview are not gated. The 402 body looks like this:

{
  "detail": {
    "code": "quota_exceeded",
    "message": "Monthly request quota reached (5000/5000)",
    "quota_exceeded": true,
    "included_requests": 5000,
    "current_requests": 5000,
    "window_start": "2026-10-01T00:00:00+00:00",
    "window_end": "2026-11-01T00:00:00+00:00",
    "cta_path": "/billing"
  }
}

Past the cap, current_requests reports the cap itself, not a live count. The CLI exits 1 on this 402 and links to the billing page.

Upgrade from Free

  1. Open Settings → Billing and pick a plan from the comparison table.
  2. You are redirected to Stripe Checkout to pay.
  3. Stripe returns you to the dashboard's confirmation page, which polls until the subscription is active — the page confirms; fulfillment happens server-side regardless of whether you wait.
  4. With no projects yet, the dashboard takes you to Getting Started from there.

Change between paid tiers

Moving between paid tiers happens in-app, no checkout: pick the new plan and review the proration preview — the amount due now and the line items behind it — before confirming.

Manage Subscription

Manage Subscription opens the Stripe customer portal: payment methods, invoices, and cancellation live there.

Next

On this page