Skip to content
Ant0 Docs
Create free account

Accounts and plans

The desktop app signs in with an Ant0 account. Free account creation is open, and paid plans can be bought in your account and paid in cryptocurrency.

Free account creation is open. Paid plans are on sale: the workspace owner chooses a plan in the workspace’s billing controls and pays its invoice in cryptocurrency. The billing controls always show the sales availability the account service reports for that workspace.

Use Create free account, enter an email address and password, then verify your email with the six-digit code. A new account starts on the Free plan. Accounts support optional two-factor authentication. Human verification runs on the separate verify.ant0.link host; ant0.link/turnstile redirects there.

Install the desktop app from the download page and sign in with the same account. Account support: {{public:support}}

The web account navigation separates Overview, Workspace, Billing, Security & devices and Downloads & help. Workspace includes a selector and searchable Members, Invitations and Folders tabs where the current plan allows teams. Search covers loaded records; use Load more when another page is available. Open a row’s Details to inspect complete access information and choose an edit or removal action. Creation and changes open focused dialogs. Owners can manage non-owner members; managers can manage operators and starters. Operators and starters see only their granted folders. Folder access is edited with each member’s role, or chosen when creating an invitation. Removing a folder moves its live profiles to the selected destination and removes that folder’s grants.

Workspace billing separates Service, Seats, Invoice and Plans. Add paid seats and Manage renewal seats open quantity dialogs. Confirmed changes appear in dismissible notifications. Unknown request outcomes stay visible with their original recovery actions; closing a dialog does not cancel a submitted request.

Invitation links are emailed by the account service; creating one does not confirm email delivery. Accepted members still need device-key enrollment from an owner or manager in Desktop → Team. Ownership transfer and recovery remain in the desktop app. Owners can open each workspace’s billing controls.

If a team request’s outcome is unknown, the tab retains its exact operation key and request through workspace navigation and reloads. Refresh workspace access, then choose Retry original request. The page does not automatically repeat writes after refreshing a session. Resolve pending requests before signing out or closing the tab; signing out clears this tab’s retained recovery data. No invitation token or device private key is included in this recovery record.

Plan limits count live and trashed profiles. Each seat allows two active devices. Web account access registers this browser as a counted device; browser and desktop devices share the same allowance.

PlanProfilesSeatsMonthly priceYearly price
Free51$0
10 profiles101$9$90
50 profiles502$24$240
200 profiles2003$59$590
1,000 profiles1,0005$149$1,490

A year costs twelve months for the price of ten. Extra seats cost $5 per month or $50 per year on the plan’s billing interval. The listed seats are included plan limits; Free has no purchasable extras. Extra seats allow additional devices but do not enable plan features such as teams on the 10-profile plan.

Payment is by cryptocurrency only. There is no card, PayPal or bank-transfer payment.

  1. Open Billing for your workspace. Only the workspace owner can see it.
  2. On Plans, select the plan, the monthly or yearly interval and any extra seats, then choose Create invoice. The account service confirms the price and applies any workspace credit before the invoice exists.
  3. Choose a payment provider and open its hosted invoice: BTCPay pays on-chain Bitcoin to our own BTCPay Server at pay.ant0.link; NOWPayments opens its own hosted invoice. Availability is reported by the account service and checked again when the payment quote is requested.
  4. Pay the hosted invoice. Opening checkout does not confirm payment, and the amounts are quoted for a limited window; Refresh payment status shows what the service has confirmed.

Your plan limits change when the payment confirms, not when the invoice is created. On-chain Bitcoin confirmation is not instant: the invoice stays open until the network confirms it and the account service settles it. If workspace credit covers the full amount, an invoice can settle immediately without an external payment.

The account shell supports an initial extra-seat quantity with a paid-plan purchase. Owners with a supported funded allocation can use Add paid quantity to request an absolute extra-seat target. The service quotes each funded term separately. Additions activate only after eligible payment; creating an unpaid invoice does not grant capacity. If workspace credit covers the full amount, or the prorated amount rounds to zero, creation can settle immediately and activate eligible additions. Quoted time elapsed before activation returns as workspace credit, shown separately from the immutable base and seat charges.

Next unpaid renewal changes the quantity at the final paid-through boundary, preserving every already-paid future term. Members and devices must fit before a reduction can be scheduled. The lower future capacity immediately limits new admissions. Reset unpaid reduction restores the final paid allocation for the next unpaid renewal; it does not purchase seats or change paid invoices. Renew the same plan by paying its existing renewal invoice, not by creating another plan checkout.

The capacity summary separates active entitlement, the new-admission cap and the dated renewal allocation. Legacy or manually granted, unpriced seats are identified as unsupported for commercial seat changes; no purchase or refund value is invented. Existing invoice recovery and cancellation remain available. Sales availability is reported independently of these management controls, and financial cancellation does not remove a security suspension.

What the app sends while you are signed in

Section titled “What the app sends while you are signed in”
  • Authentication in the desktop app sends the email address and password over TLS, a hardware-derived device identifier and hash, platform, app version, and Ed25519 and X25519 public device keys. The web account shell instead uses a persistent random browser-device seed and sends the identifier and hash derived from that seed, not a hardware fingerprint. The service stores a password hash rather than the password. Session records include IP address and user agent.
  • Claiming a profile sends its UUID, identity key and optional operating-system or browser hints. The cloud stores claim and audit hints and the persona it issues.
  • Heartbeats send the number of running profiles, app and default-engine versions, integrity hashes, and device and workspace identifiers. The server also receives the request IP address and country.
  • Profile names and notes, cookies, browser storage and proxy details are stored locally. Optional crash reports can contain profile identifiers or operator-entered diagnostic text.

See What leaves your computer for every connection, including crash reports and proxy checks.

The background service refreshes its licence on start and periodically. Existing profiles have a three-day offline grace period; creation is blocked while offline.

StateWhat it meansWhat works
ActiveLicence current.Everything.
Offline · reconnect within N hThe server could not be reached. You have a 3-day grace period.Existing profiles start; nothing new is created.
LockedNo valid licence (grace period over, or signed out).Locked profiles cannot start. Cookie export works only for a profile that was already running.
SuspendedThe account was suspended (see the acceptable use policy).Nothing starts. Support: {{public:support}}

There is no self-service account-deletion control or deletion API. Privacy and data-rights requests: {{public:privacy}}. Identity verification may be required. Automated retention cleanup is scheduled, but no account-deletion deadline or warning-email cadence is guaranteed. Local profile data remains under your control, subject to the optional crash-report exception above.

The desktop installer does not bundle a CLI or SDK. Portable CLI and MCP archives are listed on the download page when a release includes them. Profiles and their data stay on your computer; sync is an explicit per-profile action.