Pricing
Ten dollars a person. Everything included.
One price, the whole product. Analytics and AI are not a higher tier, and seats are the only thing that scales.
Cloud
Recommended
$10
per user, per month
Run by us, on Cloudflare. The whole product, with nothing held back for a higher tier.
- Collections, maps and all twelve field types
- Realtime editing, comments and version history
- The generated typed client and Vite plugin
- REST API, SDKs, CLI and webhooks
- First-party cookieless analytics
- AI drafting, suggestions and delegated tasks
- Unlimited collections, entries and projects
- Email support
Self-hosted
Free
on your own infrastructure
The same product, deployed to your own Cloudflare account. Open source.
- Collections, maps and all twelve field types
- Realtime editing, comments and version history
- The generated typed client and Vite plugin
- REST API, SDKs, CLI and webhooks
- First-party cookieless analytics
- AI drafting, suggestions and delegated tasks
- Your own database, storage and queues
- Community support on GitHub
Enterprise
Custom
quoted against what you need
For organisations that need contracts, review and a person to call.
- Everything in Cloud or self-hosted
- Roles and per-collection publish permissions
- Audit log and data residency review
- Security review and a signed agreement
- Onboarding and migration help
- A named contact and an SLA
The questions this page gets asked.
- What counts as a user?
- Anyone with a seat in your workspace. Readers of your site are never counted, and neither are API requests from your application.
- Is the free self-hosted version cut down?
- No. It is the same code, running on your own Cloudflare account. You provide the database, storage and queues, and you keep the whole product.
- What happens if we stop paying?
- Your content stays reachable through the API and the CLI so you can export it. Locking your own words away from you would be a strange way to earn a renewal.
- Do you charge for traffic?
- No. Analytics ingest runs on its own budget and does not spend your API quota, because a busy site makes far more tracking calls than content reads.
Still weighing it up?
The comparison pages put Stet next to whatever you are using now, and say what that product does better.