Your cart 0 items
Your cart is empty.
Searching the site...
No matches. Try another word.
Log in
Labs

Pick a template. Click deploy. It is running.

Game servers, bots, databases and self-hosted tools, launched from a catalogue in one click and managed from your browser. No Linux required.

See pricing All the features
Who it is for

Three kinds of people love it here.

For tinkerers

The Minecraft server, tonight.

For tinkerers

The catalogue covers the fun stuff: Minecraft and a shelf of Steam game servers, Discord bots, voice servers like TeamSpeak and Mumble. From idea to invite link: pick the template, name it, deploy. Minutes later you are sending the join link to your friends, and the live console shows the world spinning up. Yours to fiddle with: the file manager and console are right there in the browser when you want to tweak, and scheduled backups have your back when a mod goes wrong.

For small teams

Self-hosted tools without the ops.

For small teams

Run the tools you would rather own: Gitea for code, Grafana for charts, Redis, PostgreSQL, MariaDB and MongoDB for data, RabbitMQ for queues. The ops are our problem. Hard CPU, memory and disk limits keep every app in its lane; backups run on schedule; the nodes, updates and plumbing are ours to worry about. Access, controlled: invite teammates to a specific deployment with exactly the permissions they need, protected by two-factor and OAuth sign-in.

For builders

A safe sandbox for experiments.

For builders

Spin up a Node.js, Python or Java runtime, point it at a database from the catalogue, and try the idea tonight instead of provisioning for a week. Break it without breaking anything: every experiment lives in its own isolated container with hard resource caps. When it is done, delete it; when it works, keep it running. Automate it: a documented API and outbound webhooks mean your experiments can create, restart and manage themselves.

Fair limits, no surprises

Every app in its own lane.

Fair limits, no surprises

Each deployment gets hard caps on CPU, memory, swap, disk and IO, enforced at the container level. Your neighbour cannot eat your lunch. Watch it live: the console shows real-time CPU, memory and network charts next to a live terminal, so you always know what your app is doing.
How it goes

Deployed in four steps.

  1. Browse

    Pick a template from the catalogue.

  2. Name it

    Choose the settings the template exposes.

  3. Deploy

    It launches in its own container with hard limits.

  4. Manage

    Console, files, backups and charts in the browser.

Fair questions.

Do I need to know Linux?

No. If you can fill in a form, you can deploy. The terminal is there when you want it, not because you need it.

What can I deploy?

A curated catalogue: game servers, Discord bots, voice servers, databases, developer runtimes and self-hosted tools, growing steadily.

Is it a full virtual machine?

No, and that is the point. Apps run in isolated containers: faster to start, safer to run, fairly limited. If you need a whole OS, our servers are the better fit.

Who keeps it running?

We run the nodes, the updates and the plumbing. You run your app.

Ready when you are

Deploy something tonight.

The catalogue is waiting.

See pricing Talk to us
Features

Look closer.

The catalogue, the console and everything around them.

Up close

Everything, in detail.

The template catalogue is the front door: every deployable app is a template with sensible settings chosen by us, from game servers and bots to databases and dev runtimes. You see the options that matter and none of the ones that do not.

One click, properly done. Deploy launches your app in its own isolated container on a managed node, with its resources capped and its settings validated. No YAML, no SSH, no surprise dependencies.

The live console is mission control in a tab: a real-time terminal into your running app beside live CPU, memory and network charts. You can see exactly what it is doing, and type straight at it when you want to.

Files without FTP. Browse, edit, upload and archive your deployment's files in the browser; SFTP is there for the traditionalists. Databases for your app come from the catalogue too, provisioned in a click.

Backups that behave: on-demand when you are about to do something brave, scheduled when you would rather not think about it, with remote storage supported. A cron-style scheduler can also restart, run commands or back up on a timetable.

Hard resource limits on CPU, memory, swap, disk and IO keep every deployment honest. Your app gets what you paid for; so does everyone else.

Team access done right: invite subusers to a specific deployment with granular permissions, sign in with two-factor or OAuth, and keep SSH keys where they belong.

Automate everything. A documented API and outbound webhooks let your tools create and manage deployments, and activity logs record who did what, when.

And so much more.

Scheduled tasks. Restarts, commands and backups on a timetable.

SFTP access. For when the browser is not enough.

OAuth sign-in. Google, GitHub, Discord and more.

Two-factor auth. On by choice, recommended always.

Activity logs. Who did what, when.

Webhooks and API. Plug Labs into anything.

Pick your first template.

The price will not slow you down.

See pricing Talk to us
Pricing

Small price. Real resources.

Pick a size, deploy what fits. Placeholder plans until launch.

Pricing

Monthly or yearly.

Monthly

9,99 a month for a deployment with honest resource caps. Start and stop whenever.

Yearly

99 a year. Two months on us for the committed.

Before you commit.

Each plan lists its CPU, memory and disk plainly. Hard limits, honestly stated, no burst roulette.

Step up a size, or graduate to a Calyraen server when you need a whole machine. We will say so honestly when you do.

Yes. Each deployment has its own plan, its own limits and its own console.

Something running by bedtime.

Pick a template and go.

Talk to us The other platforms