Terms of service

version: 2026-11-11-draft

PLACEHOLDER, NOT LEGAL TEXT. This draft has not been reviewed by a lawyer and is waiting for Dallen's legal review. It describes how Akter Cloud works today so the sign-up flow can show and record acceptance. Don't rely on it as an agreement until this banner is gone and the version above changes.

These terms cover your use of Akter Cloud: the Cloud API, the akter CLI when it talks to Akter Cloud, and the hosted MCP server. The open-source packages (@akterjs/* and akter) are licensed under Apache-2.0 on their own; these terms don't change that license.

Your account⁠

You sign up with an email address and a one-time code. You're responsible for keeping access to that mailbox and for every session, agent key and agent you allow to act for you.
An agent you connect, through the CLI, an agent key or the MCP server, acts as you within the roles and limits you gave it. You're responsible for what it does.
Akter asks a person to confirm dangerous actions, such as deleting an app. Don't build systems that confirm on a person's behalf.

Your apps and data⁠

You keep your rights in the code you deploy and the data your actors store. You give Akter the rights it needs to run, store, back up and export them for you.
You can export your data at any time with akter export. Deleting an environment or an account deletes its data after the retention period stated in the docs.
Don't use Akter Cloud to break the law, to harm others, to attack or overload other systems, or to store data you have no right to store.

Usage, limits and billing⁠

Usage is metered and priced as published. Spend caps on your organization and on agent keys stop new spend when they're reached.
A new metered dimension, or a higher price for an existing one, is announced at least 30 days before it is charged, with the date it starts, which is the earliest it can start. Only usage on or after that date is charged at the new price; earlier usage never is.
A command or query is billed when it's made with your credentials and Akter Cloud did its work for it: an authenticated, authorized call answered on your app's behalf, including your actor's own errors and the refusal of a malformed payload, such as one that doesn't match the call's schema. It isn't billed when it's refused for authentication or authorization (a 401 or 403, including an actor refusing a caller its rules don't allow), stopped by a spend cap, refused by a rate limit or an admission limit (such as a store past its disk ceiling or a session past its watch limit), or when it fails on Akter's side (a 5xx, an actor that's unavailable, or a request that hangs or is cancelled). A retry under the same command id that returns the recorded outcome is billed once.
An actor isn't charged for being connected or idle: the hosts that run it are included. Commands and queries are charged per call, stored data per GiB-month, and an actor's computers for the time they run.
Payment is handled by Stripe. Card details never pass through Akter, the CLI or an agent.

Service⁠

Akter Cloud is provided as is, without warranties beyond those the law requires. Availability targets, if any, are stated separately.
Akter may suspend an account that breaks these terms or puts the service or other customers at risk, and will say why where it can.
These terms may change. A change gets a new version, and you'll be asked to accept it before your next sign-up or as described in the change.

Contact⁠

Questions about these terms: the contact address will be added at legal review.