Documentation
Updated
These docs explain how to use Wolkra in the console and through the API: from your first server to networks, load balancers and automation. Each page is short and task-focused.
Looking for general Linux tutorials instead? See the guides.
Start here
- Getting started: create an account, add balance, add an SSH key and launch your first server.
- Create a server: every option explained, from images and plans to labels, placement groups and cloud-init.
- Connect with SSH: log in from Linux, macOS or Windows, reach private servers through a jump host, and use the browser console or rescue mode.
Network and security
- Firewalls: stateful inbound and outbound rules, applied to servers or label selectors, with example rule sets.
- Private networks: your own IP ranges, servers without public IPs, NAT gateways and Elastic IPs.
- Load balancers: layer 4 and HTTP services, targets, health checks and HTTPS.
Storage and data
- Volumes: block storage from 10 GB to 10 TB; attach, mount, grow and move.
- Backups and snapshots: daily backups with 7 restore points, on-demand snapshots and new servers from snapshots.
Account, billing and API
- Billing and balance: prepaid balance, per-hour billing with a monthly cap, card and crypto top-ups and what happens when the balance runs low.
- Account security: two-factor authentication, sessions, roles, projects and the activity log.
- API tokens: create
wk_tokens and call the REST API athttps://api.wolkra.com/v1.
Quick reference
| Item | Value |
|---|---|
| Console | https://console.wolkra.com |
| API base URL | https://api.wolkra.com/v1 |
| API auth | Authorization: Bearer wk_… |
| Location | Frankfurt am Main, Germany (fra1, zone eu-central) |
| Billing | prepaid, per started hour, capped at the monthly price |
| Traffic | unmetered, shared ports up to 10 Gbit/s, fair use |
| Support | tickets in the console, [email protected] |
Common tasks
- Launch a WordPress site: create a server with the WordPress one-click app, then point your domain at it.
- Keep a database private: create a private network, attach the database server without public IPs, and allow its port only from the network in a firewall.
- Add a second web server: create it from a snapshot and put both behind a load balancer using a label selector.
- Store growing data: attach a volume and grow it when needed.
- Automate: create a read/write API token restricted to your CI's address.
Related pages
- Cloud servers and pricing
- One-click apps
- Composer, the visual canvas to draw and apply a stack
- FAQ and contact
Frequently asked questions
Where do I start?
With getting started. It takes you from sign-up to a running server you can log in to, in about five minutes.
Is there API documentation?
The API tokens page shows how to authenticate and which resource paths exist under https://api.wolkra.com/v1.
What is the difference between the docs and the guides?
Docs explain how to do things in the Wolkra console and API. Guides teach general server skills, such as hardening Ubuntu or running Docker Compose, that work anywhere.
How do I get help if the docs don't answer my question?
Open a ticket in the console or email [email protected].