Deploy a game server, a database, a web service or a static site

Deploy game servers, databases, web services from git or an image, and static sites, in one location or many. Pay as you go or monthly per location.

Run software from our catalogue, such as a Minecraft server or a database, a web service from a git repository or a container image, or a static site. Choose one location or several, with one instance, a running copy, in each. Pay as you go, or monthly per location.

Order now · See pricing

Choose a plan

Choose a tier, a size, how often you pay and a location. The price is for one instance in one location.

Order now

A static site runs no instance, so it needs no plan from this list. It counts as one of your plan’s websites.

What you can deploy

Choose the source when you order: software from our catalogue, your own code or a static site.

Game servers. Choose Minecraft, Terraria, Valheim or another game from our catalogue, and we install it and set it up. Run it from the dashboard, with a console, a file manager, SFTP, databases, snapshots and schedules.
Databases. Run MariaDB, PostgreSQL, MongoDB or Redis, which your apps reach at the server’s address and port. WordPress, Node.js and Python are in the catalogue too.
Web services from git. Connect GitHub and choose a repository, such as a Node.js or Python project. Each push to your production branch builds a new release, with a build we work out from your code. GitLab, Gitea, Forgejo and Gogs connect with a webhook.
Container images. Run an image you have already built as a web service, by its name and tag.
Static sites. Deploy a site whose build makes files, and our edge, the network that answers your visitors, serves them. There is no instance to run. A static site counts as one of your plan’s websites.
Hybrid sites. For a framework such as Next.js, our edge serves the static files, and your instances answer the rest.

Give players a join address at no charge

Where it runs

One instance runs in each location you choose, unless you ask for more.

One location or many. Run a deployment in one location, in several you choose, or in every location, as your plan allows. A server or a database runs one instance in each location, and each keeps its own data.
The nearest instance first. Our edge sends each visitor of a web service or a hybrid site to an instance in their own location when there is one, and to the nearest location that runs one when there is not.
Autoscaling. On Pro and up, set the fewest and the most instances for each location, and we add instances as requests grow and remove them as they fall. Autoscaling stays within your spend limit.
Sleeps when idle. A web service or a hybrid site can sleep when no request reaches it. Its instances stop, and the next request wakes one. On pay as you go, a sleeping instance costs nothing.

Releases, previews and addresses

Each web service, static site and hybrid site comes with these.

Releases you can roll back. Each version you deploy is a release, with its build log. If something breaks, roll back to an earlier release in one step. A rollback builds nothing again, and a static site serves the earlier release’s files at once.
Previews. On Pro and up, each branch and pull request builds a preview at its own address, and on GitHub we post that address on the pull request. Previews sleep when idle, and go when their branch or pull request closes.
Your own domain. Add a domain you own, confirm it with a DNS record, and we get its certificate for you.
Our edge in front. Every address of a web service, a static site or a hybrid site gets a free SSL certificate and a managed firewall, as a website on Edge Proxy does. Add custom firewall rules, rate limiting rules and cache settings, as your plan allows for websites.
Protection. On Pro and up, ask visitors for a password, or to sign in with Coritan as you or your team, on previews or on everything. A bypass token lets your tests and tools through.
Variables for each environment. Set variables for production, previews and development, override one for a branch, and share groups of them between deployments. Import a .env file, and export one with every value not marked secret.

How you pay

Instances are servers, so they are paid on every plan. Your plan adds allowances for what your deployments use.

Pay as you go. We take the time each instance runs from your credit, at its plan’s hourly price. A stopped or sleeping instance costs nothing. Pay as you go opens once you have added a set amount of credit in total. An account billed by invoice pays monthly per location instead. How much credit unlocks hourly billing
Monthly per location. Commit to a number of instances, and pay for them each month or for a longer term, whether they run or not. The order prices each location you choose. Instances that autoscaling adds above those are charged by the hour from your credit.
Allowances with your plan. Your plan includes build minutes, bandwidth, edge requests and room for static sites each month, shared by all your deployments. At an allowance we stop new use instead of charging you: previews sleep and new builds wait for the next month.
Overage and spend limits. Choose Bill past the allowance, and each unit past it is billed, up to your spend limit. At a spend limit, we stop the overage, previews and extra instances, or pause the deployment if you choose. Set a spend limit on a deployment or on the whole account. We email you at 80% and 100% of it, and at 50% on pay as you go.

What each plan includes for App Deployment

Each month, shared by your deployments

Build minutes: 300 minutes on Free, 3,000 minutes on Pro, 10,000 minutes on Business, Unlimited on Enterprise
Bandwidth: 100 GB on Free, 1,000 GB on Pro, 3,000 GB on Business, Unlimited on Enterprise
Edge requests: 1 million on Free, 10 million on Pro, 50 million on Business, Unlimited on Enterprise
Static site storage: 1 GB on Free, 10 GB on Pro, 50 GB on Business, Unlimited on Enterprise

For each deployment

Locations: 1 location on Free, Up to 5 locations on Pro, Unlimited on Business, Unlimited on Enterprise
Previews: Not included on Free, Included on Pro, Included on Business, Included on Enterprise
Password and sign-in protection: Not included on Free, Included on Pro, Included on Business, Included on Enterprise
Autoscaling: Not included on Free, Included on Pro, Included on Business, Included on Enterprise
Logs kept for: 1 day on Free, 7 days on Pro, 30 days on Business, 90 days on Enterprise

Compare every plan

How it works

Choose what to deploy. Choose software from our catalogue, a git repository, a container image or a static site, then the size, the locations and how you pay.
We set it up. We install the software or build your code, and start it in each location you chose.
Run it from the dashboard. Follow each release, open a server’s console, add domains and change variables, all in one place.

Add-ons

A server add-on raises one limit of one server. A pack raises an allowance of the whole account each month.

Guides for App Deployment

Our docs explain each step, from the order to your first release.

App Deployment: What a deployment is, and what you can run on it.
Order a deployment: Choose what to deploy, the size, the locations and how you pay.
Deploy from a git repository: Connect GitHub, choose the production branch and turn on previews.
Host a static site: Set the output directory, redirects and headers.
Host a Minecraft server: Set up a world for your friends, step by step.
Choose locations and scaling: Run in several locations, scale with traffic and sleep when idle.
Add a domain and protection: Use your own domain, and ask visitors for a password.
How App Deployment is billed: Pay as you go or monthly per location, allowances and spend limits.
Take a server snapshot: Save a copy of a server, and turn on automatic backups.

Deploy your first app or server

Choose what to run and where, and we set it up for you.

Order now · See pricing

Frequently asked questions

What can I deploy?

Game servers such as Minecraft, Terraria and Valheim, databases such as MariaDB and PostgreSQL, and WordPress, Node.js and Python from our catalogue. Or a web service from your own git repository or container image, and static and hybrid sites. The order page lists all the software you can choose.

What happened to Container Apps and Apps?

They are App Deployment now, under App Deployment in the dashboard. Each Container Apps server is already a deployment, with the same price, addresses and data. Each app is one too, with the same addresses and data; if it was not billed before, we tell you before it starts on pay as you go.

How is App Deployment different from Cloud Compute?

On App Deployment we install the software you choose or build your code, and run it in the locations you choose. Cloud Compute gives you a whole virtual machine with root access, where you install and look after everything yourself.

Can I pay by the hour?

You can, once you have added a set amount of credit in total. With pay as you go, we take the time each instance runs from your credit, and a stopped instance costs nothing. Set a spend limit, and we email you when the month’s charges reach 80% and 100% of it.

What does a static site cost?

A static site runs no instance, so it costs nothing within your plan’s allowances, which cover its builds, its bandwidth, its requests and its files. It counts as one of your plan’s websites.

Is my deployment protected from DDoS attacks?

Visitors reach a web service, a static site or a hybrid site through our edge, where our network filters out DDoS attacks and a managed firewall checks each request. The shared address of a server, such as a game server, is not filtered, so attach a floating IP, which DDoS Shield filters at no charge, or give players a join address.