AnkraDocs
Console

Account

Billing and credits

Hourly billing with a monthly cap, server plans, the IPv4 add-on, what else is billed, the 30-day terms of a dedicated uplink, the small trial an account gets without a card and the full access a card unlocks, how credits and coupons pay for usage inside their window, the free trial dev cluster, and monthly invoices.

Ankra Cloud bills by the hour and caps every resource at its monthly price. Prices are in euros and exclude VAT.

A card is required to create resources, whatever credit the account holds. Credit, including the sign-up credit, is spent first once a card is added, but it never stands in for one. See Before you create resources.

How usage is metered#

  • An hourly meter records one usage line per resource per clock hour (UTC) it existed in.
  • A resource's hourly price is its monthly price divided by 730.
  • A dev cluster's server is billed by the second it exists: each hour's line costs the hourly price for the share of that hour the server existed in. A dev cluster that runs for 17 minutes across two clock hours pays for 17 minutes, and the summary and billing log show it as one hour. Its public IPv4 add-on is billed by the hour.
  • A resource never costs more in a calendar month than its monthly price: that is the cap.
  • A stopped server keeps billing: it keeps its disk and its addresses. Delete servers you no longer need.
  • Days and months are UTC.

GET /v1/usage/summary shows the month to date, an estimate for the whole month and a per-resource breakdown; GET /v1/usage/billing-log has one line per resource per day. In the console these are Cost & usage → Summary and Billing log.

Server plans#

Plan Tier Cores Memory Included storage Per month
starter-1c-1g Cost-optimized 1 1 GiB 20 GiB €1.49
starter-1c-2g Cost-optimized 1 2 GiB 20 GiB €2.49
starter-2c-4g Cost-optimized 2 4 GiB 20 GiB €4.99
starter-4c-8g Cost-optimized 4 8 GiB 30 GiB €7.49
starter-8c-16g Cost-optimized 8 16 GiB 40 GiB €14.49
starter-12c-24g Cost-optimized 12 24 GiB 50 GiB €20.49
starter-16c-32g Cost-optimized 16 32 GiB 50 GiB €26.49
cloud-native-1c-1g Balanced 1 1 GiB 20 GiB €3.95
cloud-native-1c-2g Balanced 1 2 GiB 20 GiB €6.95
cloud-native-2c-4g Balanced 2 4 GiB 20 GiB €12.45
cloud-native-4c-8g Balanced 4 8 GiB 30 GiB €21.95
cloud-native-8c-16g Balanced 8 16 GiB 40 GiB €42.95
cloud-native-12c-24g Balanced 12 24 GiB 50 GiB €61.45
cloud-native-16c-32g Balanced 16 32 GiB 50 GiB €79.95
premium-1c-4g Dedicated CPU 1 4 GiB 30 GiB €24.95
premium-2c-8g Dedicated CPU 2 8 GiB 30 GiB €29.95
premium-4c-16g Dedicated CPU 4 16 GiB 45 GiB €59.45
premium-8c-32g Dedicated CPU 8 32 GiB 60 GiB €95.45
premium-16c-64g Dedicated CPU 16 64 GiB 75 GiB €190.45

Plans come in three tiers: starter-* is Cost-optimized, cloud-native-* is Balanced and premium-* is Dedicated CPU. Cost-optimized and Balanced offer the same general-purpose sizes, two GiB of memory per core from 1 core / 2 GiB to 16 cores / 32 GiB plus a 1 core / 1 GiB entry size, so a server moves between the two without changing size. Balanced costs more than Cost-optimized at every size.

Dedicated CPU sells one line with four GiB of memory per core. It starts at premium-1c-4g, 1 core and 4 GiB for €24.95 a month, and runs to premium-16c-64g. A server that moves into Dedicated CPU takes one of these five sizes. The other premium-* plans are no longer sold; a server on one keeps its plan and its price.

Cost-optimized and Balanced are on sale: the console offers their plans for new servers, Kubernetes node pools and edges. A new server starts on Cost-optimized at its cheapest plan; the Balanced plans are on their own tab. Cost-optimized and Balanced servers share host CPUs, each capped at one host CPU per vCPU.

Dedicated CPU is on sale in se-sto2 (Stockholm) and de-fsn3 (Falkenstein), the zones whose sells_dedicated_cpu is true: a new server on a premium-* plan there has each vCPU pinned to a host CPU no other server uses, with no CPU cap. Elsewhere the console shows the tier as coming soon. A server already on a premium-* plan keeps the CPUs it was created with and can change to another plan of the tier that is sold; moving a server into Dedicated CPU in one of those zones gives it dedicated CPUs.

A zone can run out of stock on a tier. The tier then shows Out of stock in that zone, and new servers, new Kubernetes node pools and plan changes into the tier are refused there; the zone's sold_out_plan_families lists such tiers. Servers already on the tier keep it and can change size within it, and existing Kubernetes node pools keep replacing and scaling their nodes. Today Cost-optimized is out of stock in fr-lil1 (France), which sells Balanced.

Included storage is a small root disk that grows with the cores: 20 GiB up to two cores, 30 GiB at four, 40 GiB at eight and 50 GiB from twelve, half as much again on Dedicated CPU. Keep data on volumes (a PersistentVolumeClaim on Kubernetes) rather than on the root disk. You choose the boot disk's size when you create a server (storage_gibibytes, from the image's minimum up to 4096 GiB): a smaller disk costs the plan's price, and every GiB beyond what the plan includes is billed at the storage tier's price per GiB.

Servers created before 20 October 2026 keep the disk and the included storage they were created with, so their bill does not change; a plan change gives them the storage the new plan included before then.

GET /v1/plans (or ankra-cloud plans list) returns the current catalogue with hourly prices; a plan that is sold has is_offered true. Every plan includes a public IPv6 /64. A plan change (POST /v1/servers/{id}/plan, server stopped) is billed from the next hour.

Plans no longer sold#

These Dedicated CPU plans are no longer sold. They are listed for servers that are still on them:

Plan Tier Cores Memory Included storage Per month
premium-1c-1g Dedicated CPU 1 1 GiB 30 GiB €3.49
premium-1c-2g Dedicated CPU 1 2 GiB 30 GiB €7.99
premium-2c-2g Dedicated CPU 2 2 GiB 30 GiB €10.99
premium-2c-4g Dedicated CPU 2 4 GiB 30 GiB €17.49
premium-4c-8g Dedicated CPU 4 8 GiB 45 GiB €31.99
premium-2c-16g Dedicated CPU 2 16 GiB 30 GiB €48.49
premium-8c-16g Dedicated CPU 8 16 GiB 60 GiB €62.49
premium-4c-32g Dedicated CPU 4 32 GiB 45 GiB €87.49
premium-12c-24g Dedicated CPU 12 24 GiB 75 GiB €89.99
premium-16c-32g Dedicated CPU 16 32 GiB 75 GiB €116.49
premium-8c-64g Dedicated CPU 8 64 GiB 60 GiB €170.99

A server or a Kubernetes node pool that is on one of these plans keeps the plan and its price, and a node pool on one keeps replacing and scaling its nodes. The plan cannot be chosen any more: a new server, a plan change into it and a new Kubernetes node pool, edge, VPN gateway or dev cluster on it are refused, and the console no longer offers it. To resize such a server, change it to a plan that is sold. GET /v1/plans still lists these plans, with is_offered false.

The IPv4 add-on#

Every public IPv4 address costs €4.00 a month for as long as it is held, in use or not, billed for every hour it is held. No price includes one. The same price applies to every holder:

  • a server, running or stopped (resource_type: "public_ipv4");
  • a network edge VM (public_ipv4);
  • a floating IP, attached or detached (floating_ip);
  • each public IPv4 address of a load balancer: its frontend address, which is part of the load balancer's line, and the address of each of its VMs, a public_ipv4 line per VM;
  • a router's NAT address, a public_ipv4 line beside the NAT gateway's own;
  • a Kubernetes cluster's API endpoint, which is part of the control plane's line.

Only a public IPv4 address is charged. Where the address of a router's NAT, of a load balancer VM or of a network edge VM is not a public IPv4 address, it costs nothing and has no line. A router says whether its NAT address is charged (nat_address_billed), and the usage summary shows a public_ipv4 line for every address that is.

Ankra assigns the address; you do not choose it or its range. IPv6 is never a line item. Database VMs hold no public IPv4.

For example, a highly available load balancer with the IPv4 add-on holds at most three public IPv4 addresses, its frontend address and one on each of its two VMs: at most 2 × €1.49 + 3 × €4.00 = €14.98 a month, and €6.98 where its VMs' own addresses are not public ones. Without the add-on it holds none and costs €2.98. A router with NAT costs €10.00 a month, and €14.00 where its NAT address is a public one.

Everything else#

Resource Price Billed while
Extra block storage per tier: €0.049 (standard), €0.039 (local-nvme), €0.029 (hdd) per GiB-month it exists, beyond the plan's included boot storage
Backups and snapshots €0.012 per GiB-month they exist
Floating IP €4.00 a month allocated
Router with NAT (shared uplink) €10.00 a month, plus €4.00 a month for every public IPv4 address it holds NAT is enabled and no dedicated uplink is active
Router with NAT on a dedicated uplink €85.00 per 30-day term, 50 TB of transfer through the gateway included, then €2.00 per TB, metered per term. On top, €4.00 a month for every public IPv4 address the gateway holds from the day Ankra activates the dedicated uplink until you remove it or delete the router; see 30-day terms
Network edge VM its plan, plus €4.00 a month for every public IPv4 address it holds it exists
Load balancer €1.49 a month per HAProxy VM, plus €4.00 a month for every public IPv4 address it holds: at most €14.98 for a highly available pair with the IPv4 add-on it exists
Kubernetes control plane development €0.00, highly available production €40.00 a month, plus €4.00 for an IPv4 API endpoint it exists
Managed PostgreSQL db-1c-2g €15.00, db-2c-4g €40.00, db-4c-8g €80.00 a month, plus €0.12 per GiB-month of storage it exists
Object storage €0.015 per GiB-month, per started GiB data is stored
Network transfer 20 TB outbound included per server per month, then €2.00 per TB, billed as you go. What a server sends through its public interface and what it sends through a router's shared NAT gateway both count —

Every server has a 1 Gbit/s outbound port on its public interface; inbound traffic is not limited. Inbound traffic, private-network traffic, private networks and routers without NAT are free. Storages and backups in error state are billed too, since their volume may exist; delete them to stop billing.

Network. Of a server's 1 Gbit/s outbound port, the Cost-optimized tier guarantees 15% (150 Mbit/s) and the Balanced tier 50% (500 Mbit/s).

30-day terms#

A NAT gateway on a dedicated uplink is the one resource that is not billed by the hour. It is billed per term of 30 days:

  • The first term starts when Ankra activates the dedicated uplink. While the request is pending, and if it is declined, the router is billed as an ordinary NAT gateway on the shared uplink.
  • A term costs €85.00 and is charged in full when it starts. It is not prorated and not refunded, and the monthly cap does not apply to it.
  • The term does not include the gateway's address: on top, the gateway is charged €4.00 a month for every public IPv4 address it holds, billed by the hour like every public IPv4 address (see The IPv4 add-on). A gateway whose address is not a public IPv4 address is charged nothing for it.
  • Terms renew automatically every 30 days until you remove the dedicated uplink or delete the router. Removing it in the middle of a term charges nothing further and refunds nothing; a router that still has NAT is billed as a shared NAT gateway again from the next hour. A term that has started is charged, however soon after its start the dedicated uplink is removed.
  • While the dedicated uplink is active the term replaces the shared NAT gateway price: the router has no hourly NAT gateway line.
  • Each term is one usage line (resource_type: "nat_gateway_dedicated_uplink", 720 hours) dated at the term's start, so it is on the invoice of the calendar month the term starts in. A month of 31 days can carry two terms.
  • Each term includes 50 TB of transfer through the gateway; beyond that the price is €2.00 per TB (a TB is 10^12 bytes). See Transfer through a dedicated uplink.

The router shows the state of its dedicated uplink and, while it is active, when the current term ends (dedicated_uplink.term_ends_at).

What the servers on a router's private networks send to the internet through its NAT gateway is metered on the gateway. Only outbound traffic counts. Inbound traffic, traffic between private networks and the traffic of a floating IP do not.

  • Transfer is metered per 30-day term of the dedicated uplink. Each term includes 50 TB; the allowance starts over when a new term starts, and what is left of it does not carry over.
  • Transfer beyond the 50 TB of a term costs €2.00 per TB, charged for the part of a TB that was used. 51.25 TB in a term is 1.25 TB beyond the allowance: €2.50.
  • It is billed on the day it is sent, as a usage line of its own (resource_type: "nat_gateway_transfer", no hours), so it is on the invoice of the calendar month of that day. The monthly cap does not apply to it.
  • The router's page in the console shows how much of the 50 TB the current term has used and, once it is beyond them, what that has cost so far. GET /v1/routers/{id}/transfer answers the same figures. They follow the traffic by about a minute.
  • Removing the dedicated uplink ends the metering against a term. Transfer beyond the allowance that was already sent stays billed.

Transfer through a shared NAT gateway#

What a server sends to the internet through a router's NAT gateway on the shared uplink counts towards that server's own transfer allowance, as if it had sent it through a public interface of its own: 20 TB a month included, then €2.00 per TB on the server's network_transfer line. The gateway counts it by the private address it was sent from, so each server behind a router is metered on its own. The network transfer page shows it as part of each server's outbound traffic (nat_transmitted_bytes). Nothing is billed to the router for it.

While the router's dedicated uplink is active, the same traffic counts towards the uplink's 50 TB per term instead and nothing of it is counted against the servers.

Credits#

A credit is an amount that pays for the usage your account incurs while the credit is valid. Credits are applied to invoices before the card is charged. An account without a card gets only a small, limited trial whatever credit it holds (see Before you create resources); adding a payment method unlocks full access and lets the credit pay. A credit is not a balance that pays any invoice: it pays for the usage whose metered period overlaps its validity window, whenever the invoice for that usage is issued.

For example, a credit valid from 15 September to 15 October pays for the second half of September on September's invoice and the first half of October on October's invoice, and nothing before or after.

  • When an invoice is issued, it spends your credits, the soonest-expiring first, on the earliest covered usage not yet paid, up to what each credit has left.
  • A credit past its expiry is expired and pays for nothing more. Usage outside every credit's window is due.
  • GET /v1/account/credits shows each credit's amount, what is left (remaining_cents), its expiry and status, and the account's total balance_cents. The usage summary carries credit_balance_cents and credit_next_expiry.

The sign-up credit#

Free credit comes with Ankra Cloud used through the Ankra Platform. The account the Platform creates for your organisation, when one of its administrators first signs in to Ankra Cloud with Ankra or when the Platform sets up Ankra Cloud for it, receives a credit of €59.00, valid for 30 days from that moment. It needs no code and is granted once per account. It pays for resources once a payment method is added, which also unlocks full access; until then the account gets only a small, limited trial.

An account signed up for on Ankra Cloud directly, with an email and password or with Google, Microsoft or GitHub, receives no sign-up credit, and the sign-up code cannot be redeemed by hand. Connect it to an Ankra organisation and the organisation's credit on the Platform, including the welcome credit a saved card unlocks there, pays for Ankra Cloud too. Credit granted before 19 November 2026 keeps its amount and expiry.

Coupons#

A coupon is a code Ankra gives you. Redeeming it grants a credit: the coupon's amount, valid from the redemption for the coupon's number of days. Its credit is added to the credits the account already holds, the sign-up credit included when the account has one. Redeem a code at sign-up (the Coupon code field, or a sign-up link with ?coupon=CODE), in Settings → Billing → Credits, or with POST /v1/account/coupons (billing.manage). Codes are not case sensitive, and each account redeems a coupon once. A refused redemption answers 422 with a reason: unknown, inactive, not_yet_valid, expired, exhausted or already_redeemed.

Invoices#

One invoice is issued per closed calendar month that had usage, once the meter has covered the whole month.

  • total_cents is the sum of the capped usage lines.
  • Each credit that paid part of it is a kind: "credit" line with a negative amount and the credit's label, for example Ankra Cloud signup credit; credit_applied_cents is their sum.
  • amount_due_cents = total_cents − credit_applied_cents is what is charged.

An invoice credits pay in full is paid at once. Otherwise the amount due is charged to your default payment method through Stripe; the invoice carries payment_status (open, paid or overdue) and a hosted_invoice_url to view or pay it. Card details are entered only on Stripe's hosted pages and never reach Ankra Cloud. Manage payment methods in Settings → Billing; the first one you add becomes the default.

Before you create resources#

Servers, storages, databases, load balancers, object storage, floating IPs, edges, Kubernetes clusters and node pools and dev clusters are billed. An account with a default payment method creates them without a further check on its credit: credits, including a redeemed coupon, pay for usage first and the card is charged for the rest.

An account without a default payment method may not create anything, whatever credit it holds:

Every billed create answers 402 with reason: payment_method_required until a card is added. Credit, including the signup credit and a redeemed coupon, is spent first once the card is there, but it never stands in for one.

Resources created before this rule keep running on their credit, and Kubernetes node pools may still grow inside the node count or autoscaling maximum they were priced for, so nothing that runs is interrupted. A server that is stopped, by you or by Ankra, is a different matter: starting it again (POST /v1/servers/{id}/start, or a restart of a stopped server) answers the same 402 until a card is added.

What the credit would cover is still reported in standing.credit_cover on GET /v1/account/billing, and in the console under Settings → Billing → Creating resources:

Field In the console What it is
available_cents Credit left What your live credits have left after the usage metered so far. It is the credit balance the console shows.
committed_monthly_cents A month of what you run, at list prices One month, at monthly list prices, of every billed resource the account holds now, and of the nodes its Kubernetes node pools may still add (up to each pool's node count or autoscaling maximum).
spendable_monthly_cents Covered by credit, per month at list prices available_cents minus committed_monthly_cents, never below zero: what the credit would still pay for a month once a card is added.

credit_cover also carries next_expiry, the soonest expiry of a live credit. It is null once the account has a default payment method, and for an organisation that Ankra Platform invoices. While it is set, standing.can_create_resources is false.

A credit pays for nothing after it expires. Usage that no credit pays for appears on that month's invoice (see Credits and Invoices).

An account without a payment method is billed for that usage like any other, from the moment Ankra switched billing it on; usage from before that is never billed. Whether the account has a payment method is judged when the month's invoice is built and decides the whole month. If a payment method is saved before the invoice is sent, the usage is waived instead, as for any account that saved a card before its owner approved paid usage. Otherwise the invoice has no card to charge, so it is overdue as soon as it is sent: the console's notifications and an email to the owners and admins say what is due and by when, the invoice's Pay button under Settings → Billing opens Stripe's page where it can be paid by card, and reminders follow three days and one day before the 7-day grace period ends. An invoice still unpaid then suspends the account for payment (see below).

Add a card in Settings → Billing (the console opens Stripe's page; POST /v1/account/billing/setup-session with the API). Card details are entered only on Stripe's pages. While the account may not create resources the console says so on every page, with the reason, and turns its create buttons off.

An account linked to an Ankra Platform organisation is usually prepaid (standing.billing_arrangement: "prepaid"): it still needs a card, but Ankra Cloud never charges it. You will never be charged without a top-up: the account spends only the credit your organisation tops up on the Ankra Platform billing page. Without a card on file a create answers 402 with reason: payment_method_required, as for any account. With one, a create the credit does not cover answers 402 with reason: credit_required and top_up_url, the Ankra Platform billing page to top up on; adding another card does not help. GET /v1/account/billing reports the same reason and standing.top_up_url, and the console shows Top up on the Ankra platform instead of asking for a card.

An account with a card that is linked to an Ankra Platform organisation whose owner has not yet approved paid usage creates resources only while a credit has money left; after that the create answers 402 with reason: owner_approval_required until the owner approves paid usage in Ankra Platform.

Servers that nothing pays for are not left running for free. When an account billed by card has no payment method on file and no credit left (the same credit balance as credit_cover.available_cents, at zero) and still runs servers it is charged for, the console's notifications and an email to its owners and admins say so and name a date seven days later; a reminder follows about a day before. GET /v1/account/billing shows it as standing.unpaid_usage_since and standing.servers_stop_at. If no payment method was added by then, those servers are powered off. Powering off keeps disks, addresses and data, and you start the servers again yourself once a payment method is saved. Contact support if you cannot add one. The servers Ankra created for a dev cluster or for a managed Kubernetes cluster's node pools are not powered off this way.

When an invoice stays overdue for more than 7 days, the account is suspended for payment: the same creates answer 402 with reason: account_suspended. Nothing you already run is stopped or deleted, and paying the invoice lifts the suspension at once. Ankra staff can also suspend an account; contact support to lift that. GET /v1/account/billing shows your standing: can_create_resources, the reason a create would be refused with, and credit_cover.

The free trial dev cluster#

An account linked to an Ankra Platform organisation that has neither a card nor credit that covers a dev cluster can still try one. It may start one free trial dev cluster:

  • on a plan with at most 2 cores and 4 GiB of memory (for example starter-2c-4g), without the public IPv4 add-on;
  • free: its server is never metered, so nothing it does reaches an invoice;
  • deleted with its server 24 hours after it was created, unless the account saves a card first. Then it is kept as an ordinary dev cluster and billed as its server, by the second, from the next full hour.

One trial runs at a time, and an account may start three in 30 days. GET /v1/account/billing carries dev_cluster_trial: whether one may be started now (is_available), and when not, why (reason is not_linked_to_platform, trial_running, trials_used or dev_clusters_not_offered, with a sentence in detail). A trial dev cluster carries is_trial: true and its trial_expires_at; a converted one carries trial_converted_at. In the console, Dev clusters offers Start a free 24-hour trial dev cluster while the account has neither a card nor credit left to spend, limits the plans to the trial's, and badges each trial with the time it has left.

Reading usage, invoices, credits and payment methods needs the billing.read permission; adding payment methods and redeeming coupons needs billing.manage. Owners and admins have both.

Quotas#

Every account has limits: a new account starts with 6 servers, 12 cores, 24 GiB of memory, 300 GiB of storage, 1 floating IP, 5 routers, 10 private networks and 3 public IPv4 addresses. GET /v1/quotas shows limits and usage (memory as memory_mebibytes); allocations past a limit answer 422, and so does moving a server to a plan that would take the account past its cores or memory.

Public IPv4 addresses and floating IPs are two limits, and an address counts under one of them:

  • Public IPv4 addresses counts the IPv4 addresses your servers hold and, in a location where a floating IP becomes the server's own public IPv4 (Stockholm, se-sto1), the floating IPs you have reserved. Each address counts once, whether it is assigned to a server or kept spare. So with the default limit of 3 you can reserve several addresses there yourself, as long as servers and reserved addresses together stay within the limit.
  • Floating IPs counts the floating IPs that are forwarded to a server by the location's gateways, everywhere else.

Ankra assigns the address of every floating IP and public IPv4; you choose the location, not the range. IPv6 has no limit.

To raise them, request higher limits under Settings, Quotas (or POST /v1/quota-requests with the limits you need and what they are for). A production Kubernetes environment alone needs seven servers, so expect to ask before creating one; its review step links to a request prefilled with what it needs. Ankra staff approve or decline every request and you are notified either way. Nothing changes until a request is approved, and an approval only ever raises a limit. An account has one pending request at a time; withdraw it to ask for something else. Asking needs the operate permission.