Skip to main content
Ankra billing is based on worker vCPU usage. Each plan includes a free vCPU allowance - you only pay for usage above that threshold, billed monthly. Playground environments are the exception: they are billed outside the vCPU metering. Pay-as-you-go organisations pay from credit, and saving a payment method unlocks €59 of welcome credit.

Plans

Ankra offers three standard plans. Enterprise is agreed with you by Ankra: the table shows its published rate, it needs a 12-month commitment, and it has its own support terms. An organisation on a plan agreed with Ankra sees Your plan is agreed with Ankra on its Plan panel and changes it through Ankra support.
A 12-month commitment saves 20% on the per-vCPU rate. On Startup, Change plan offers Billed: Monthly or 12-month commitment.

Credit and payment method

Pay-as-you-go organisations pay for resources from credit. A payment method is required to use resources, but credit is always spent first, and you will never be charged without a top-up: your card is only charged when you add credit.

Welcome credit

For a pay-as-you-go organisation, saving a payment method unlocks €59 of welcome credit, valid for 30 days. The credit is no longer granted when the organisation is created - it is added when the card is saved, from guided setup or from Billing. It is granted at most once per card and once per person: a card that already unlocked it for another organisation, or an owner who already received it there, does not unlock it again, and an organisation that already holds Ankra Cloud’s sign-up credit does not receive it either. Credit you have not spent when the 30 days end expires. Welcome credit granted before the amount changed on 24 October 2026, or before the term changed on 13 November 2026, keeps its original amount and expiry date. Until a payment method is saved, a new organisation can run its free playground, but cannot create or import other clusters. It can also spend a small allowance of pipeline minutes and AI each calendar month (UTC), and once that is spent its pipeline runs and AI pause until a payment method is saved. A playground on an Ankra Cloud dev cluster lasts 24 hours without a card.

Top-ups

Add credit from Settings → Plan and billing, view Credit: click Add credit, enter the Amount in euros and, if you have one, a Bonus code, then click Continue to Stripe. You pay on Stripe’s page, and the credit is added once Stripe confirms the payment. Redeem a code beside it adds credit from a code Ankra gave you; each code works once. Both buttons need permission to manage billing. Automatic top-up is off unless you turn it on. Set When the credit falls below (euros), Add this much (euros), At most this much a day (euros) and At most this much a month (euros), and Ankra charges your saved card when the credit falls below the amount you chose. We recommend turning them on for anything you need to keep running, so your services are never paused for lack of credit.

When credit runs out

What happens when your balance reaches zero and nothing tops it up depends on what you are running:
  • On the Ankra platform, nothing that is running is stopped. Creating new clusters and AI usage are paused until you top up. Your running clusters are unaffected.
  • On Ankra Cloud servers, including a playground that runs as an Ankra Cloud dev cluster, new resources are refused. You are notified first, and after a grace period running servers are stopped. They stay stopped until you top up.
Adding credit restores access.

Playground environments

A Playground is a development and evaluation Kubernetes environment on Ankra-hosted infrastructure. Playgrounds are moving to Ankra Cloud dev clusters - a single-node Kubernetes cluster managed by Ankra. This is rolling out, so your organisation may still get a playground on the shared infrastructure described below. An Ankra Cloud dev cluster is one server with 2 vCPU / 4 GB. Without a payment method the free cluster lasts 24 hours. Once a payment method is saved it keeps running, paid from your credit. It is billed as Ankra Cloud usage and is not counted toward your plan’s worker-vCPU metering. The sizes below apply to playgrounds on Ankra’s shared playground infrastructure. They are sold as flat monthly list prices per size, in EUR excluding VAT, on every plan. Storage is bundled into the size. The hourly equivalent is the monthly price over a 730-hour month, for comparison only - billing is per second, not per hour. How playground charges work:
  • Pro-rata by the second. Billing runs from the moment the environment is ready (its ready_at time) until you destroy it. Nothing accrues while it is provisioning.
  • The price you order at is the price of record. Later catalogue changes apply to new orders only, never to an environment you are already running. A resize bills the old price until the resize completes and the new price after.
  • Flat price, nothing else metered. There are no per-vCPU, per-GB, egress, IP or GPU charges for playgrounds. Playground clusters are excluded from the plan’s worker-vCPU metering: they are never billed per vCPU, and they do not consume the 30 free vCPU either.
  • Own invoice line. Playground spend appears as its own line on the invoice, separate from worker-vCPU usage.
  • One free Trial per organisation. The Trial costs nothing and needs no billing plan or card. On shared playground infrastructure it expires when the organisation goes idle; as an Ankra Cloud dev cluster it lasts 24 hours unless a payment method is saved.
  • An organisation memory budget of 8 GB. Paid playgrounds share a budget of 8 GB of advertised RAM per organisation unless a limit increase has been approved. Request one from the size picker or from the Playground memory budget card on the billing page.
Ordering a paid size requires billing permissions in your organisation, a billing plan and a payment card on file. New paid orders refuse while an invoice is overdue.
Playgrounds are for development and evaluation only: no production workloads, no personal data, no backups, and they are excluded from the SLA (Terms of Service clauses 6.2 to 6.4 and 9.9).
See Sizes and Pricing on the Playground page for what each size includes and how to order, resize and destroy one.

Plan and billing in the portal

Open Settings → Plan and billing (/next/organisation/billing). Its views are Overview, Usage, Invoices, Ankra AI and Credit. Anyone whose role holds billing.read sees the page; changing the plan, the payment details and the AI caps needs permission to manage billing, and without it the page says so at the top.

Overview

The overview shows, from the top:
  • This month: what the month will cost if your clusters stay as they are for the rest of it, how much has accrued so far, how much of the month has gone, and when it is invoiced. On Free it reads No charge; on a plan with a fixed monthly fee agreed with Ankra it shows that fee. When playgrounds are running, it says how much of the figure is theirs.
  • Plan: the plan and how it is billed, its price, Term (when it renews) and Payment (Card and details in Stripe or Not added yet). Once a card is saved, Payment details opens Stripe’s customer portal, where you change the card and billing details.
  • vCPU, last 30 days, with a link to Cost by cluster.
  • Recent invoices, with All invoices.
  • The Ankra AI, Ankra Cloud and Image registry storage panels.
While paid usage still waits for an owner, the overview also shows Unlock paid usage: an owner adds a payment method there with Add payment method, then approves paid usage with Confirm charges and unlock. Only an organisation owner can approve charges. The “so far” subtitle shows how much has accrued and what percentage of the month has elapsed.

AI Usage and Free Allowance

The overview also meters your organisation’s AI activity. Every AI request is tracked (tokens per model, priced in USD), and each plan includes a free monthly AI allowance that covers usage served on Ankra’s platform key. The overview shows month-to-date AI usage, the allowance meter, and a self-serve daily AI spend cap (USD/day) you can set as a brake on total AI activity. Every plan also includes $50 a month on the DevOps AI model by Ankra, Ankra’s own model, metered separately: the overview shows that allowance beside the ordinary one. Past it the model bills per token, and once the ordinary allowance or your credit is used up, AI features run on the DevOps AI model while it has room instead of stopping. See Models and Cost for what the allowance covers, what pauses when it is exhausted, and how to keep unlimited AI with your own OpenRouter key.

Usage of every meter

Worker vCPU is one of several things Ankra measures. Usage reports every meter in one place - worker vCPU-hours, playgrounds, managed services, Ankra hosted logs and metrics, and AI - per month or day, split by cluster, application or managed service, with how completely each was measured and what it costs. Managed services and hosted logs and metrics are included during the pilot.

Showback by project

The invoice is one per organisation and never splits by project. For charging teams back internally, Settings → Plan and billing, view Usage, has a By project section while projects are on: per project, the clusters it holds, their current worker vCPU, the worker vCPU-hours over the window and each project’s share of the total, plus the hours no project could claim. The same figures are served at GET /api/v1/org/billing/analytics/by-project?hours=720 and by ankra org usage --group-by project. Hours are attributed to the project a cluster was in when they were metered, so a cluster that moved mid-month is split between the two projects rather than rewritten. Nothing here changes what you are charged: it is a view of the one invoice, not a second one.

Invoices

The Invoices view lists the organisation’s invoices: one a month for the month before, and, for an organisation invoiced monthly that moves to Free during a month, one for that month so far once Ankra has reviewed and sent it. Each row has a PDF download and opens the invoice in Stripe: Pay on an unpaid invoice, View on a paid one. Unpaid invoices are marked Open. The overview’s Recent invoices has the same actions.

Ankra AI spend and caps

The Ankra AI view shows what Ankra AI cost across your organisation: Today against the Daily spend cap, the tokens used today, and This month. Change the caps sets:
  • Daily spend cap: at the cap, Ankra AI stops answering until the next day. Spend on your own model keys counts too. Choose the plan’s cap or Your own cap, in US dollars a day.
  • Soft token cap a day: past it, unattended runs use the quick model for the rest of the day.
  • Hard token cap a day: past it, new unattended runs are refused until the next day. It cannot be below the soft cap.
Empty token caps mean no cap. The caps count each day from midnight UTC. The CLI reads and sets the same caps; none clears one:

Credit

The Credit view holds the organisation’s prepaid credit, which usage draws from hour by hour:
  • Credit: the Balance and each credit line with what is left of it, plus Add credit and Redeem a code (see Top-ups).
  • Automatic top-up: see Top-ups.
  • Statement: every change to the credit, newest first: credit added, usage taken each hour, and credit that expired.
  • Top-up receipts: each time credit was bought with a card, with Stripe’s receipt.
  • How you pay: a company that cannot prepay can Apply for monthly invoicing with its legal name, registration number, VAT number, address and billing contact. Ankra checks the company’s registration, VAT number and credit, and a person decides; until then you keep paying from prepaid credit.
  • Credit programmes: credit Ankra gives to organisations that qualify. A person at Ankra reviews every application, and granted credit is used before credit you buy.

Changing your plan

1

Open the dialog

In Settings → Plan and billing, click Change plan. The dialog lists Free, Startup and Enterprise, with (now) on your current plan.
2

Pick a plan

The dialog says what changes and when:
  • Startup from Free: an owner unlocks paid usage under Unlock paid usage on the overview. Nothing is charged before that.
  • Enterprise: Ankra agrees the price and terms with you, and nothing changes until you have agreed them.
  • Free from a paid plan: Free starts at once, not at the end of the month. Stripe stops billing your current plan. On a plan invoiced monthly, the month so far becomes an invoice that someone at Ankra reviews before it is sent, and a fixed monthly fee on your plan is charged to the end of the month, not in proportion; an organisation paying from credit gets no such invoice. If paid playgrounds are running, Ankra asks you to destroy them first.
  • On Startup, Billed switches between Monthly and 12-month commitment. A running 12-month commitment shows its end date; Ankra support can end it early.
3

Confirm

Confirm in the dialog. Where Stripe needs your payment details, it asks you to confirm them first, and the change takes effect once you have. The Plan panel then shows the new plan.

How Billing Is Calculated

Ankra tracks vCPU usage through periodic snapshots of your clusters:
  1. Snapshots are taken hourly per cluster, recording worker vCPU and total vCPU.
  2. Billable vCPU = worker vCPU minus the free allowance (per hour bucket, aggregated across clusters).
  3. Cost per hour = billable vCPU × effective rate (plan rate adjusted for any annual discount).
  4. Monthly cost = sum of hourly costs for the billing period.
Only worker node vCPU counts toward billing. Control plane nodes are not billed.

FAQ

Worker vCPU is the total vCPU count across all worker nodes in your clusters. Control plane / master nodes are excluded from billing.
Billing starts when your clusters report worker vCPU usage above the free allowance. If you stay within the free tier, there is no charge.
Yes. Plan changes take effect immediately. Your invoice for the month will reflect the prorated usage under each plan.
Annual billing locks in a 20% discount on the per-vCPU rate. You commit for 12 months and are billed monthly at the discounted rate. While it runs, the Change plan dialog shows its end date.
On Startup and Enterprise, usage above the free vCPU allowance is billed at your plan’s per-vCPU-hour rate, and This month on the overview shows the estimate. Free bills nothing: the Change plan dialog describes it as a plan where staying over the allowance for long holds back new clusters and more nodes.

Next Steps

Usage

Every meter Ankra measures, split by cluster, application or service.

Organisations

Manage teams and resources across organisations.