Priced per project.
Not per seat.

One site, app or brand: its own models, entries, media, API keys and team. Each project has its own plan and its own bill, so a busy site never pushes a quiet one onto a bigger plan.

No. Every plan includes seats for the people who edit, and viewers are free and unlimited. Adding a teammate never changes your bill.

Every read our CDN serves for you, cache hits included, because that is what the CDN charges us for. Traffic from the Capa editor never counts, and neither do the requests our own rewarm makes. Image and file requests are not counted as API requests; they count toward bandwidth.

Paid plans keep serving. Usage past the allowance is billed at the rates above on your next invoice. Capa alerts you in the admin at 80% and 100%, and you can set a spend cap. On Free, uploads and new models pause at the limit and reads keep working.

Publishing purges and refills what changed in about 3 seconds, on every plan. With background rewarm, Capa also fetches cached responses again shortly before they expire, so a read is back in cache before a visitor asks for it.

A message to the Assistant costs 2 credits, and each model, field or entry it drafts costs 1. "Add a blog model with six fields" uses about 9. Credits reset every month and do not roll over. Everything the Assistant drafts waits for a person to publish it.

Yes. Each project has its own card and invoices. Hand the project over and your client adds theirs; you keep whatever role they give you.

Yes. An upgrade applies straight away and you pay the difference for the rest of the period. A downgrade applies at the end of the period, so you keep what you paid for.

Two months free on Starter, Pro and Scale when you pay for a year up front. Agencies with five or more paid projects get 20% off on top.

When you need more than the largest plan includes, an uptime SLA, invoices with purchase orders, custom terms, or a named engineer. Tell us about your projects and traffic and we will size it with you.