Cloud accounts

A cloud account is a connection to a cloud provider where you have — or want strackt to order — servers. Connecting one lets strackt provision, rebuild, and manage servers on that provider for you. Open the page from Settings › Connections › Cloud accounts.

Managing cloud accounts is owner-only. If you're a member rather than the workspace owner, you'll see the accounts the owner connected, but not the controls to change them.

Supported providers

You can connect accounts with these providers:

• Hetzner
• DigitalOcean
• Vultr
• Linode
• TransIP
• Hostinger
• UpCloud

Connect an account

If you have no accounts yet, the page shows a grid of providers to pick from. Once you have one, use Connect another provider to add more.

Choosing a provider opens a guided panel with everything you need:

1. A link to open the provider's console, where you create the credential.
2. The exact permissions ("scope") the token needs — read the guidance shown, so strackt has enough access to order and manage servers.
3. The credential fields. Most providers use a single API token; TransIP uses an account login and a private key.

Give the account a label you'll recognise, paste in the credential, and connect. strackt verifies the credential with the provider before saving it — if the provider rejects it, nothing is stored and you'll see what went wrong, so a typo never becomes a broken connection you have to hunt down later.

Your tokens and keys are stored securely and are never shown back to you. Each account displays a short masked hint (for example dop_v1_••••1a2b) so you can tell which credential is on file.

Account health

Each connected account carries a health status:

• Connected — the provider is accepting the credential. The row shows when it was last checked and how many servers were ordered with it.
• Needs attention — the provider stopped accepting the credential, usually because the token was revoked or expired. Your running servers keep running, but strackt can't order new servers or rebuild existing ones on this account until it's reconnected.

strackt rechecks accounts automatically once a day. You can also choose Recheck on any account to check it right now. A brief network hiccup won't flip an account to "Needs attention" — only the provider actually rejecting the credential does.

Reconnect an account

When a token expires or is revoked, use Reconnect and paste in a fresh credential. strackt verifies the new credential with the provider before replacing the old one, so a bad replacement can never overwrite a working connection. The saved credentials stay in place unless verification succeeds.

Remove an account

Removing an account is always allowed, and strackt shows you which servers were ordered with it before you confirm. Removing it won't touch running servers — but strackt can't order or rebuild on that account until you connect it again.

What's next

• Connect a server — bring a server under strackt's management
• Settings overview — everything else you can configure