Deploy apps from Git, a folder or a Docker image
Cloider App Engine runs your code as a web service. Point it at a GitHub, GitLab or Bitbucket repository, a folder on your computer or a Docker image, and Cloider builds it, runs it and serves it over HTTPS on a free cloider.app subdomain or your own domain. There are no servers, clusters or Kubernetes manifests to manage.
- Free *.cloider.app subdomain with HTTPS
- Custom domains
- Free builds, requests and traffic
- Billed by the second
Everything a web app needs to ship
Deploy on every push
Connect GitHub, GitLab or Bitbucket and pick a branch. Every push to it can build and deploy a new version, or click Deploy latest commit when you choose.
Deploy from your computer
cloider deploy packages the current folder, detects its language, framework and port, and prints the live URL. Or drop a folder, a .zip or an HTML file in the dashboard.
Run any Docker image
Deploy a prebuilt image from any registry, pinned to the digest its tag pointed at. Ship the next one with the Deploy button, cloider deploy --app or the app's deploy hook.
Dockerfile or buildpacks
Your Dockerfile is built exactly as written. Without one, Cloud Native Buildpacks build Node.js, Python, Go, Java, Scala, PHP, Ruby and .NET, and plain HTML is served as a static site.
Deploys without downtime
A new version goes live only once every replica answers on its port, or passes its health check, and stays up for 15 seconds. Until then the previous version keeps serving.
1 to 20 replicas
Let Cloider size the app and add replicas as it gets busy, or set a fixed number and size yourself. New apps start on automatic resources with 1 to 3 replicas.
Cron jobs
Run an app on a schedule instead, such as every night at 03:00 UTC. A cron job has no port or address: it starts, does its work and exits.
Logs, terminal and insights
Search live logs, open a terminal in any replica, and follow requests, CPU, memory and replicas on the Insights tab.
Variables and secrets
Plain and secret environment variables, build arguments and build variables, set in the dashboard, with the CLI or through the API.
From source code to HTTPS in four steps
Upload or fetch the source
The dashboard and the CLI zip your folder and upload it. A git app has its branch fetched at the latest commit.
Build an image
Cloider picks a build strategy from the root of your source: your
Dockerfile, a buildpack for your language, or a static web server for plain HTML.Run it
The image is pushed to your account's private registry and started as a container, which listens on the port in the
PORTenvironment variable.Go live when it is healthy
Once every replica answers and stays up for 15 seconds, traffic moves to the new version on its HTTPS address.
# install the CLI on macOS or Linux, then sign in
curl -fsSL https://cloider.com/install.sh | sh
cloider login
# deploy the current folder
cd blog
cloider deploy
# ✓ Deployed version 1 of blog
# https://blog-x7k2.cloider.app/
Pay for the compute your app runs on
An app is billed for the CPU and memory of its running replicas, prorated to the second. Each replica counts the larger of what it is given and what it uses.
| Compute | $35 per compute unit per month |
|---|---|
| Compute unit | 1 vCPU or 3 GB of memory, whichever is larger |
| Image storage | $0.50 per GB per month, the two newest images per app |
| Builds, requests, traffic, HTTPS | Free |
| A paused app | Free |
An app that averages 0.1 vCPU and 256 MB around the clock is 0.1 compute units, $3.50 a month. Every price is on the pricing page.
App Engine questions
What is Cloider App Engine?
Cloider App Engine runs your code as a web service. You give it a GitHub, GitLab or Bitbucket repository, a folder or a Docker image, and Cloider builds it into a container image, runs it on 1 to 20 replicas and serves it over HTTPS on a free cloider.app subdomain or your own domain. There are no servers, clusters or Kubernetes manifests to manage.
Do I need a Dockerfile to deploy an app?
No. Without a Dockerfile, Cloider builds Node.js, Python, Go, Java, Scala, PHP, Ruby and .NET projects with Cloud Native Buildpacks, and serves a folder of HTML files as a static site. With a Dockerfile at the root of the project, Cloider builds exactly that Dockerfile.
Which port should my app listen on?
Listen on the port in the PORT environment variable. Cloider sets it to the app's port, which is detected from the project or defaults to 8080, and only routes traffic to that port. You can change the port on the app's Settings tab.
How much does an app cost?
An app is billed for the CPU and memory of its running replicas, at $35 per compute unit per month, prorated to the second. Builds, requests and traffic are free, and a paused app costs nothing. Its images are kept in your account's registry, which is billed by the data it stores, and Cloider keeps only the two most recently deployed images of each app.
What happens to my running app when a new build fails?
Nothing. The version that is live keeps serving until a new version builds, starts and stays up. A failed build only marks that build Failed, and you can retry it or deploy again.
Is Cloider App Engine an alternative to Heroku?
Yes. Like Heroku, App Engine builds your code with buildpacks or a Dockerfile, deploys on every git push and serves it over HTTPS. Instead of choosing a dyno size, you can let Cloider size and scale the app and pay for the CPU and memory each replica is given or uses, and the same account runs your databases, Kubernetes clusters and object storage.
More answers in the documentation, or contact us.