Billing and credits

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

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 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#

Plans come in three tiers: starter-* is Cost-optimized, cloud-native-* is Balanced and premium-* is Dedicated CPU. Every tier offers 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 changes tier without changing size. Balanced costs more than Cost-optimized and less than Dedicated CPU at every size. Dedicated CPU also offers memory-optimised plans with four or eight GiB per core. New servers start on Balanced at its cheapest plan.

Dedicated CPU is coming soon. The console lists the tier and does not offer its plans for new servers, Kubernetes node pools or edges yet. A server already on a premium-* plan keeps it and can change size within the tier.

Included storage follows one rule: the tier's rate times the larger of the memory in GiB and twice the cores. The rate is 10 GiB for Cost-optimized, 12.5 GiB for Balanced and 20 GiB for Dedicated CPU.

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

The IPv4 add-on#

A public IPv4 address costs €4.00 a month, billed for every hour it is held (resource_type: "public_ipv4"). The same price applies wherever one is held: a server, a network edge VM, a load balancer or a Kubernetes cluster's API endpoint. IPv6 is never a line item. Database VMs hold no public IPv4.

Everything else#

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.

Credits#

A credit is an amount that pays for the usage your account incurs while the credit is valid. It 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.

Coupons#

Redeeming a coupon grants a credit: the coupon's amount, valid from the redemption for the coupon's number of days. WELCOME500 grants €500 valid for 60 days. Redeem a code at sign-up (a sign-up link with ?coupon=WELCOME500), 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 Welcome credit WELCOME500; 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 and Kubernetes clusters and node pools are billed, so creating one needs a default payment method or a credit with money left on it (a redeemed coupon counts). Without either, the create answers 402 with reason: payment_method_required; add a card in Settings → Billing.

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. GET /v1/account/billing shows your standing.

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 3 servers, 8 cores, 200 GiB of storage, 1 floating IP, 5 routers and 10 private networks. GET /v1/quotas shows limits and usage; allocations past a limit answer 422. Ask support to raise them.