Pricing
Akter Cloud charges for what your apps use, by the unit, with no seats and no tiers. The SDKs, the clients, the CLI and akter dev are open source (Apache-2.0) and free to use on your own machine.
Prices
| What | Price |
|---|---|
| Commands | $1.25 per million |
| Queries | $1.00 per million |
| Storage | $0.50 per GiB-month, the first GiB-month free each month |
| Snapshots | $0.10 per GiB-month |
| Computer vCPU | $0.14 per vCPU-hour |
| Computer memory | $0.05 per GiB-hour |
| Computer exec | $0.13 per 1,000 calls |
| Egress | $0.18 per GB |
| Live updates, timers, forks, steps | Free |
An actor isn't charged for being connected or idle: the hosts that run your actors are included in the per-call prices, and an idle app holds no host at all. A computer is charged only while it runs.
Plans
- Free. Every organization gets $5 of usage a month without a card. When it's used up, new spend stops with a typed error until the next month or until you add a card.
- Paid. Add a card on a page Stripe hosts:
akter billing checkout --organization <organization>prints the link. A paid organization pays a $5 monthly minimum that its usage counts toward, so a month with $3 of usage is billed $5 and a month with $40 is billed $40. Card details never pass through Akter, the CLI or an agent. - Spend cap. A paid organization starts with a $50 monthly cap, and every agent key can carry its own. A cap stops new spend when it's reached. Change it with
akter billing set-cap, which a person confirms. - Failed payments. After a failed payment you have 7 days to fix the card before new spend stops.
What is billed
A command or query is billed when it's made with your credentials and Akter Cloud did its work: an authenticated, authorized call answered for your app, including your actor's own errors. Calls refused for authentication or authorization, stopped by a spend cap or a rate limit, or failed on Akter's side are not billed. A retry under the same command id is billed once. The terms of service give the full rule.
Watching your spend
akter usage get --organization <organization>reads a month's usage and spend per meter, for the organization, one app or one key. Usage shows up within about two minutes.akter usage forecast --organization <organization>projects this month's spend to the month's end.akter billing invoices --organization <organization>lists invoices with links to Stripe's pages for them.
Agents read the same numbers through the usage_get, usage_forecast and billing_invoices tools of the MCP server.
Price changes
A new metered unit, or a higher price for an existing one, is announced at least 30 days before it's charged, with the date it starts. Only usage on or after that date is charged at the new price.