Get started
Getting started
Create an Ankra Cloud account, see who receives the sign-up credit, add a card, deploy your first IPv6-only server and connect to it over SSH.
This guide takes you from no account to a running server you can SSH into. It takes about five minutes.
1. Create an account#
Open cloud.ankra.app/signup and choose Continue with Ankra account. Ankra Cloud has no password of its own: you sign in with the same account you use for Ankra Platform at platform.ankra.app, and creating one there takes a minute if you do not have it yet. Your email address must be verified with that account.
Both products share one sign-in, so if you are signed in to Ankra Platform you are signed in to Ankra Cloud as well, and signing out of one signs you out of both.
The first person in an account is its owner. You can invite teammates later (see Security).
2. Your sign-up credit#
Free credit comes with Ankra Cloud used through the Ankra Platform. When you sign in with Ankra as an administrator of an organisation, the account Ankra Cloud creates for that organisation receives €59.00 of credit, valid for 30 days. There is nothing to claim and no code to enter, and Settings → Billing → Credits shows it with what is left and when it expires. An account signed up for here directly, with an email and password or with Google, Microsoft or GitHub, receives no sign-up credit (see The sign-up credit).
Without a payment method an account gets a small, limited trial to try Ankra, such as one free trial dev cluster. Adding a payment method unlocks full access and lets your credit pay for what you create (see Before you create resources).
If you were given a coupon code, its credit is added to any credit the account holds. Enter it in the Coupon code field
when you create the account, or follow a sign-up link that carries ?coupon=CODE, which fills it in: it is applied
while the account is created, and the overview says what happened to it. Otherwise redeem it yourself in
Settings → Billing → Credits, or with the API:
curl -X POST https://cloud.ankra.app/v1/account/coupons \
-H "Authorization: Bearer $ANKRA_CLOUD_TOKEN" \
-H 'Content-Type: application/json' \
-d '{"code": "CODE"}'
A credit pays for usage incurred while it is valid, on the invoices of those months; see Billing and credits. Each account redeems a coupon once.
Add a card#
You need a card before you create anything, even with credit left; see Before you create resources. Add a card in Settings → Billing → Payment methods; card details are entered on Stripe's page. With a card, credits still pay for usage first, so the card is charged only for what the credit does not cover. An account linked to an Ankra Platform organisation that has neither a card nor credit that covers a dev cluster can start one free trial dev cluster.
3. Add an SSH key#
Servers are reached with SSH keys; there are no root passwords. Add your public key under Settings → SSH keys
(or POST /v1/ssh-keys) so you can pick it when you deploy. If you do not have a key yet:
ssh-keygen -t ed25519 -C "[email protected]"
cat ~/.ssh/id_ed25519.pub
4. Deploy an IPv6-only server#
In the console open Servers → Deploy server and choose:
- Zone:
se-sto1(Stockholm) orfr-lil1(Lille). - Plan:
starter-1c-1gis the smallest (1 core, 1 GiB, 20 GiB storage, €1.49 a month). - Template: Debian 13 or 12 (
debian-13,debian-12), Ubuntu 26.04 or 24.04 (ubuntu-26.04,ubuntu-24.04), Rocky Linux 10 or 9 (rocky-10,rocky-9), AlmaLinux 10 or 9 (almalinux-10,almalinux-9) or Fedora 45 (fedora-45). Log in as the distribution's default user:debian,ubuntu,rocky,almalinuxorfedora. - Network: keep the defaults. The server gets its own routed public IPv6 /64, included in the plan; the public IPv4 add-on (+€4.00 a month) stays off unless you turn it on.
- SSH key: the key from step 3.
Deploying starts a server.create operation; the server is ready when it shows Started.
The same with the CLI (see CLI for installation):
export ANKRA_CLOUD_ENDPOINT=https://cloud.ankra.app
export ANKRA_CLOUD_TOKEN=act_... # Settings → API tokens
ankra-cloud servers create --zone se-sto1 --hostname web-1 --plan starter-1c-1g \
--template debian-13 --ssh-key-file ~/.ssh/id_ed25519.pub --wait
Or with the API directly:
curl -X POST https://cloud.ankra.app/v1/servers \
-H "Authorization: Bearer $ANKRA_CLOUD_TOKEN" \
-H 'Content-Type: application/json' \
-d '{
"zone": "se-sto1",
"hostname": "web-1",
"plan": "starter-1c-1g",
"template": "debian-13",
"ssh_keys": ["ssh-ed25519 AAAA... [email protected]"]
}'
The response is 202 Accepted with the new server and the operation that builds it. Poll
GET /v1/operations/{id} until its status is succeeded.
5. Connect over SSH#
The server's page shows its IPv6 address and a ready-made SSH command (the API returns it as ssh_command). The login
user is the template's default user: debian on Debian, ubuntu on Ubuntu.
ssh debian@2a01:db8:0:2a::1
Your own network needs IPv6 for this. If it has none (some office and mobile networks), either:
- add a bastion network edge to a private network the server is on, then jump
through its IPv4 address:
ssh -J admin@<edge IPv4> debian@<server address>; or - turn on the public IPv4 add-on for this one server (€4.00 a month, billed per hour held).
From the server, IPv6 destinations work straight away. To reach IPv4-only services (some package mirrors, APIs), attach the server to a private network with a NAT gateway edge (NAT64 and DNS64) or a router with NAT; see IPv6-first networking.
6. Clean up#
Servers bill for every hour they exist, running or stopped. Delete what you no longer need:
ankra-cloud servers delete <server-id> --wait
Deleting a server deletes its storages too, unless you keep them (--keep-storages, or ?keep_storages=true on
DELETE /v1/servers/{id}).
Next steps#
- Private networks and network edges for multi-server setups.
- Storage and backups to add data volumes and scheduled backups.
- API overview to automate everything.