Per production deployment, billed annually. Evaluate free for as long as you like — pay when your reports go to production. Users, agents, and renders are never counted.
Everything quario does, with a watermark on output. No time limit.
One production service, app, bot, worker, or MCP server. Billed annually.
Buy before v1.0 to keep $199 per deployment per year for as long as you renew. Price rises to $999 at v1.0.
Pay by card. Your invoice arrives at once, your key within one business day.
Buy a licenseShip quario inside a product your customers run or buy.
| Evaluate | Deployment $999 $199 | OEM | |
|---|---|---|---|
| LICENSE TERMS | |||
| Production use | — | ✓ | ✓ |
| Use in your own production systems | Watermarked | ✓ | ✓ |
| Users, agents, and renders counted | — | Never | Never |
| Dev / staging / CI environments | Free | Free | Free |
| Redistribute inside your product | — | — | ✓ |
| SUPPORT & SLA | |||
| Community forum | ✓ | ✓ | ✓ |
| Email support | — | 2 business days | Per contract |
| Response-time SLA | — | — | ✓ |
| UPDATES & VERSIONS | |||
| All releases while licensed | Latest only | ✓ | ✓ |
| Perpetual fallback to last version | — | ✓ | ✓ |
| Version pinning & LTS branches | — | — | ✓ |
Use the Buy a license button above. Checkout is Stripe's own page. You choose how many production deployments you're licensing and give the name to print on each key. Stripe adds VAT where it's due and emails the invoice. The license sells through Link, Stripe's merchant of record, so Link is the name on it. Your key arrives within one business day. OEM is the exception: a contract sets those terms, so that button still opens an email.
A single line of small text in the footer of each rendered page: "Rendered with quario (unlicensed)". Nothing else changes — layout, formats, and features are identical to the licensed build.
One production service, application, bot, worker, or MCP server that runs quario under your control. Replicas of the same service behind a load balancer count once. Development, staging, CI, and test environments are free. The people who use it, the agents that call it, and the number of reports it renders are never counted.
One deployment license, for the service that runs the bot. Every employee can ask it for reports; they're never counted.
There are no seats. The MCP server is a deployment: one key on that server covers every agent and every person that calls it.
No. Renders are never metered. One deployment, any volume.
Two deployments, two licenses.
One per deployment. The engine verifies the key offline — no license server, nothing to activate. Put each deployment's key where that service reads its configuration, such as QUARIO_LICENSE on the server running the MCP server.
Buy while quario is pre-v1 and you pay $199 per deployment per year — locked in for every renewal, not just the first. After v1.0 ships, new licenses cost $999. Existing early-adopter licenses never move.
Your deployments keep working. The license is perpetual for every version released during your term; renewal buys another year of updates and support.
Yes. A renewal notice goes out about a month before your term ends. A person writes it by hand, not a billing system, so it's a reminder rather than a charge.
No. A deployment license covers generating documents from your own hosted product. OEM is for shipping quario itself — bundling it into software your customers install, embed, or resell.