Push code. Go live.
Your code deserves to be online. Not stuck in deployment.
Connect your repository and deploy your application without wrestling with Dockerfiles, reverse proxies, or TLS certificates. Choose managed infrastructure or bring your own server.
No Dockerfile. No YAML. No credit card. Already have an account?
Source
Resources & Scaling
Current allocation across all replicas.
From repository to live app, in five steps.
What you do at each step, and what Raklane does for you.
What changes when Raklane deploys for you.
Three things you stop worrying about. The benefit first, then exactly how it works.
Ship the app. Skip the stack.
On a bare server, going live means a Dockerfile, a reverse proxy, TLS certificates, a process manager and a deploy script, each one new to learn and to fix. For supported apps, Raklane does that part, so the work left is your code.
How it works
- Builds an image with Cloud Native Buildpacks: no Dockerfile for Node.js, Python, Go, Ruby, Java or PHP
- Runs your app in a container and restarts it if it crashes
- Routes traffic to it and issues and renews its HTTPS certificates
- Keeps build and runtime logs, live metrics and a history of every deploy
| By hand | With Raklane |
|---|---|
| Detected from your code | |
| Routing set up for you | |
| HTTPS issued and renewed | |
| git push |
A bad release doesn’t take your app down.
Your current version keeps serving while the new one starts. Visitors move over only once the new version passes its health check, and if it fails shortly after going live, Raklane switches back to the previous version on its own.
How it works
- Health check over HTTP or TCP, with a timeout and start-up delay you can tune
- Old replicas keep serving until every new one is healthy
- After go-live, the previous release stays warm for a short bake window
- A failure in that window rolls back automatically; cancel the deploy to roll back right away
- v13 · Health check passedTraffic switched to v13 · v12 kept warm
- v13 · Failing during the bake windowHealth check no longer passing
- v12 · Serving againRolled back automatically
Your server or ours. One dashboard.
Run apps on Raklane Cloud and pay for what they reserve, or connect a VPS you already rent and pay Raklane only a management fee. Move an app between them from its settings.
Compare prices ›Your server stays yours.
Here’s what we touch.
Bring Your Own Compute (BYOC) means Raklane deploys to a server you rent. You run one command on it, over your own SSH session, to install Docker, Caddy and the Raklane agent. This is what that agent can and can’t do.
- How does it connect?
- The agent dials out to Raklane over one mutually authenticated TLS connection. Raklane never connects in, and no port is opened for it. Ports 80 and 443 stay open for your visitors.
- What access does it need?
- It runs as a service with access to Docker on that server, so it can pull, start and stop your app containers and update Caddy’s routes. That is root-level power, so each server gets its own certificate, the enrollment token works once, and the private key never leaves the machine. Raklane never asks for your SSH keys or your cloud account.
- How are secrets handled?
- Environment variables and secrets are encrypted before Raklane stores them, and secrets are never shown again after you save them. Your app receives its environment variables when its container starts on your server.
- Does my traffic pass through Raklane?
- No. Visitors reach your server directly, and Caddy on your server serves HTTPS. If Raklane is unreachable, your apps keep serving; you just can’t deploy until it’s back.
- How do I disconnect a server?
- Move or delete the apps and databases on it, then choose Decommission. Two commands remove the agent from the machine; Docker and Caddy stay unless you remove them.
# Docker, Caddy, and the Raklane agent. Installed and enrolled.
curl -fsSL https://api.raklane.com/install/agent-install.sh \
| sudo bash -s -- --token=YOUR_TOKEN \
--control-plane=https://api.raklane.comWho manages what
Raklane manages
- Building your app’s image
- Deploys, health checks and rollback
- Routing and HTTPS certificates
- The agent, including its automatic updates
- Dashboard, logs and metrics
You manage
- The server, your provider bill and its firewall
- Operating system and Docker updates
- Database backups, unless you turn on Raklane’s backup add-on where available
- Your code and its dependencies
Everything you need.
Nothing you don't.
On our cloud or yours. Exactly the same.
Zero-downtime deploys.
New releases pass a health check first. Bad ones roll back on their own.
Learn more ›Git, your way.
Every push, live. Or review the diff first. Or pin a release and stay put.
Learn more ›HTTPS on every app.
Secure from the very first request. Certificates renew themselves.
Learn more ›Databases. Done.
Postgres or MySQL in a few clicks. Connection pooling built in.
Learn more ›Scales itself.
Load goes up, replicas go up. Load goes down, so do they. Up to 20.
Learn more ›See inside every replica.
Live CPU, memory, network, and disk. Every process. Thirty days of history.
Learn more ›Your server. Our deploys.
One command turns any Ubuntu or Debian server into a Raklane server.
Learn more ›Invite your team.
Four roles. One invite. Everyone on the same page.
Learn more ›Pay only for what runs.
Pause an app and its meter stops. Prefer a flat rate? There’s a plan for that.
Learn more ›Every upload, reviewed.
Before it ships.
Not every project lives in Git. Upload a zip or tar and Raklane keeps it as a version: compared with what’s running, line by line, before anything is built.
- A real diff. Files added, changed and removed, with a line-by-line view of each.
- Nothing ships by surprise. Deploy it when it looks right. Discard it when it doesn’t.
- Every upload, kept. Roll back to any earlier version in one click. Unchanged files are stored once.
@@ -1,8 +1,14 @@ const express = require("express"); +const products = require("./routes/products"); const app = express(); +app.use(express.json()); +app.use("/products", products); app.get("/", (req, res) => { - res.send("Welcome to the shop"); + res.json({ status: "ok", service: "shop-api" }); }); +app.get("/healthz", (req, res) => res.sendStatus(200));
Less plumbing.
More shipping.
Docker, Nginx, Certbot — and a lot of SSH.
- ✕ Provision and patch servers
- ✕ Write Dockerfiles and pipelines
- ✕ Configure proxies and certificates
- ✕ Script rollouts and rollbacks
- ✕ Run and tune your own databases
- ✕ Wire up monitoring and logs
A repo URL and a Deploy button.
- ✓ Paste a repo URL
- ✓ Push to ship
- ✓ HTTPS, automatically
- ✓ Databases in a few clicks
- ✓ Scaling on its own
- ✓ Metrics and logs, built in
And against the other ways to run an app
Compared by category rather than by brand. “Partly” means it depends on what you set up yourself.
| Raklane | Bare VPS | Self-hosted panel | Global PaaS | |
|---|---|---|---|---|
| Billed in rupiah, no card needed | ✓ | ✓ | ✓Your VPS bill | ✕USD, by card |
| Nothing to install, patch or keep running | ✓ | ✕ | ✕You run the panel | ✓ |
| Push to deploy, HTTPS and rollbacks built in | ✓ | ✕ | ✓ | ✓ |
| Managed servers or your own, on one platform | ✓ | ✕ | ~Your own only | ~Managed only |
| Choose who runs your database | ✓Shared, own server or cloud-run | ~You do | ~You do | ~They do |
Push code. Go live.
Create an account, connect your repository, and see your app on a live HTTPS address. Stuck anywhere? Email hi@raklane.com and we’ll help you get it running.
No credit card. Prepaid in rupiah. No contract.