Development environments in the cloud
Updated
A development environment on Wolkra is a cloud server in Frankfurt that you code on, test on or share as a staging copy, billed by the hour so it costs little when it lives only as long as you need it.
You get a full Linux machine with root access, fast downloads thanks to unmetered traffic, and snapshots to clone a working setup in minutes.
Why develop on a remote server
- Same environment for everyone. Build the setup once, snapshot it, and give each developer an identical copy.
- More power than a laptop. Pick a CPU-optimised or memory-optimised plan for big builds and test suites.
- Linux close to production. Develop on the same distribution and versions you deploy.
- Work from any device. Your environment keeps running when you close the laptop.
- Real public endpoints. Test webhooks, OAuth callbacks and HTTPS against a real domain.
Typical setups
Personal remote dev box
One server with your tools, connected through your editor's remote SSH feature. Code, containers and databases run on the server, and your laptop only shows the editor.
Shared staging server
A copy of production where the team tests changes before release. Use the Docker app for Compose-based stacks or the WordPress app for site work.
Preview environment per branch
Your CI pipeline creates a server for each branch or merge request through the API, deploys the branch, posts the address, and deletes the server after merge. With hourly billing, a preview that lives for a day costs a day.
Throwaway test machines
Need to try a new distribution, test an install script or reproduce a bug on Debian, AlmaLinux, Rocky Linux, Fedora or CentOS Stream? Create a server, test, delete. See operating systems.
Picking a plan
Standard
Shared vCPU for websites, apps, VPNs and development.
| Plan | vCPU | RAM | Disk | Traffic | Hourly | Monthly cap |
|---|---|---|---|---|---|---|
| S0 | 1 | 1 GB | 15 GB | Unmetered | €0.0056 | €3.49 |
| S1 | 1 | 2 GB | 30 GB | Unmetered | €0.0080 | €4.99 |
| S2 | 2 | 4 GB | 40 GB | Unmetered | €0.0144 | €8.99 |
| S3 | 2 | 8 GB | 50 GB | Unmetered | €0.0200 | €12.49 |
| S4 | 4 | 8 GB | 80 GB | Unmetered | €0.0288 | €17.99 |
| S5 | 4 | 16 GB | 100 GB | Unmetered | €0.0400 | €24.99 |
- Light editing and small services: a small Standard plan.
- Compiling, large test suites, containers: a CPU-optimised (c) plan.
- Many services at once or big datasets: a memory-optimised (m) plan.
Plans are billed per started hour from a prepaid balance and capped at the monthly price. You can resize up when a project needs more.
Saving money with snapshots
Powering a server off is not the same as deleting it. The surest way to pause an environment and stop paying for the server is:
- Take a snapshot of the configured server. Snapshots are billed per GB.
- Delete the server.
- Create a new server from the snapshot when you need it again.
This works well for environments you use a few days a month, and for golden images that every developer starts from.
Setting it up
- Create a server from a Linux image and add your SSH key.
- Pass cloud-init user data to install your tools on first boot, so new environments build themselves.
- Attach a free firewall that allows SSH, plus web ports only if you need them.
- Put source code and data you care about on a block storage volume that you can attach to a fresh server.
- Snapshot the result.
The first steps on a new VPS guide covers the basics.
Teams
- Organizations and projects separate client work and keep costs apart.
- Roles (owner, admin, billing, member) and per-project roles control who can create or delete servers.
- Activity log shows who changed what.
- Two-factor authentication and sign-in with Google for every member.
See teams and security.
Private test networks
Recreate production topology with a private network, a load balancer and private-only database servers. The Composer lets you draw that stack, see what it costs per month, and apply it in order, then tear it down when testing ends.
Keep dev servers secure
Dev servers often hold source code and test credentials, so treat them like production: SSH keys only, a firewall that hides dev ports from the internet, and no real customer data on throwaway machines.
Why Wolkra for dev environments
- Hourly billing with no contracts or setup fees. See hourly billing.
- Unmetered traffic for package downloads, image pulls and dataset transfers, with fair use.
- Servers in Germany, with low latency across Europe from the centre of Europe.
Get started
Create an account, add balance, and spin up your first development server in Frankfurt.
Frequently asked questions
Can I use VS Code or JetBrains with a Wolkra server?
Yes. Editors with remote SSH support connect to the server over SSH and run their backend there, so code and tools live on the server.
What does a dev server cost if I only use it during work hours?
Billing is per started hour. Delete the server when you are done and recreate it from a snapshot later.
How do I pause an environment without paying for the server?
Take a snapshot, delete the server, and create a new server from the snapshot later. In between you pay only for the snapshot, billed per GB.
Can I give each developer their own environment?
Yes. Create one server per developer from a shared snapshot, and use projects and roles so each person sees what they need.
Can preview environments be created automatically?
Yes. Use the REST API with a project-scoped token from your CI pipeline to create a server per branch and delete it when the branch is merged.