pricing
Create an account to get the public project ID used by the SDK. Browser usage is metered by Monthly Active Browsers and paid tiers add commercial use rights, support, usage analytics, included server hours, and simple server-time overage. Server-runtime usage is included during beta.
Free
20K MAB after beta
Non-commercial projects, education, tutorials
$20/mo
10K MAB
Indie commercial apps, early-stage products
$100/mo
100K MAB
Growing SaaS, embedded docs at scale
$500/mo
1M MAB
Large product surfaces, agencies
Custom
> 1M MAB
SLA · private CDN · on-prem · indemnity
the metering unit
A Monthly Active Browser (MAB) is a single browser installation that calls Runtime.boot() at least once during a calendar month for a project ID. The SDK can ping on each boot, and the server deduplicates usage when presenting or billing MAB, so a single user reloading a tab fifty times still counts as one MAB.
Multiple browsers from one person — laptop and phone, say — count as separate MABs. We don’t fingerprint, IP-track, or correlate across origins. After beta, non-commercial projects include 20,000 MAB per month.
Browser Python runs in the same browser-runtime usage model as Node. Server-runtime sessions are tracked separately from MAB. They let Verklet show workspace activity, enforce beta quotas, and bill server execution without treating every command as another active browser.
server runtime
A server hour is one hour where a Verklet server runtime is active for a project. Browser-only execution does not use server hours.
We show included usage as hours because it is easier to reason about, but usage is measured by the minute. Starter includes 40 server hours, Pro includes 300 server hours, and Scale includes 2,500 server hours each month.
Extra server time is billed at $0.30/hr on Starter and Pro, and $0.18/hr on Scale. Enterprise customers can commit to custom server-hour pools.
Server runtime access is grant-based. Production apps should mint short-lived grants from their own backend, keep privatevks_... secrets off the client, and use account caps as the budget boundary.
questions
Any use that is part of a product, service, or workflow your company sells or relies on to make money. If you are running tutorials, demos, education, or your own personal project, you are on the Free tier.
Everything is free during the beta, including the server runtime while it is in beta. We give commercial workspaces seven days written notice before we charge anything. Your usage during beta does not count against any future limits. Non-commercial projects get 20,000 MAB and browser-runtime access after beta.
Yes. Create an account, select or create an organization, and Verklet provisions a project ID for that organization. The ID is public and is used to load the right runtime assets, choose the compatible package registry, and report usage. It is not a secret and is safe to ship in browser code.
During beta, server-runtime access is included but still controlled by allowed origins, short-lived grants, and project caps. After beta, paid tiers include server hours for workloads that need managed server execution. Extra server time is billed by the minute and shown as hours on invoices: $0.30/hr on Starter and Pro, $0.18/hr on Scale.
Most customers use the default hosted runtime assets and registry. Enterprise customers can ship Verklet assets from their own CDN; talk to us if you need that.