Pricing
Builder and Team subscriptions. BYOK OpenRouter tokens are billed by OpenRouter, not marked up by Strix.
Strix sells the router, not OpenRouter tokens. Bring your OpenRouter key (required for the 7-day trial and for BYOK production). OpenRouter bills model usage on that key.
Plans
| Builder | Team | |
|---|---|---|
| Price | $29 / month | $99 / month |
| Plan id | starter | pro |
| Seats | 1 user | 3 included, then $20 / seat |
| API keys | 2 | 10 |
| Included routed requests | 50,000 / mo | 250,000 / mo |
| Included memory derives | 2,000 / mo | 2,000 / mo |
| Memory projects | 5 | 50 |
| Request overage | $0.40 / 1k requests | $0.40 / 1k requests |
| Derive overage | $0.002 / derive | $0.002 / derive |
| Public models | Nine strix-* ids | Nine strix-* ids |
Trial is 7 days. An OpenRouter key is required. Existing spend and request guardrails still apply.
What is metered
- Routed requests — one count per chat completion (including streaming), not per SSE chunk.
- Memory derives — one count per background derive job.
- Not marked up — BYOK OpenRouter
usage.cost. Strix does not applyDEFAULT_MARKUP_PCTto your key.
Managed inference (optional)
If you have no stored OpenRouter credential and run on the platform key, Strix may add 15% on OpenRouter cost, labeled managed inference. BYOK customers are not charged this line.
Checkout
Dashboard Billing starts hosted Stripe Checkout for Builder or Team once STRIPE_BUILDER_PRICE_ID and STRIPE_TEAM_PRICE_ID exist and STRIPE_BILLING_ENABLED is on. Those price IDs are not invented here. Enforcement (BILLING_ENFORCEMENT_ENABLED) stays off until explicitly enabled after meters look sane; this release does not flip it.
When STRIPE_BILLING_ENABLED is false, the dashboard may show Builder/Team as active for accounts with stored OpenRouter BYOK or an assigned paid plan (shadow paid, UX only). That does not enable enforcement or charge Stripe.