Launch offerYour first 90 days of BYOC are free for one server — connect a server you already rent. Until January 15, 2027.Claim it →

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?

New accountsSign up and get IDR 10,000 of free credit, valid for 14 days. Offer ends December 30, 2026.Claim it →
How it works

From repository to live app, in five steps.

What you do at each step, and what Raklane does for you.

Point Raklane at your code.

Paste a GitHub, GitLab or Bitbucket URL and pick a branch. Private repository? Add an access token once. No repository? Upload a zip instead. Turn on auto deploy and every push ships.

Why Raklane

What changes when Raklane deploys for you.

Three things you stop worrying about. The benefit first, then exactly how it works.

Less deployment work

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
How Raklane works ›
By handWith Raklane
Write a Dockerfile Detected from your code
Configure Nginx Routing set up for you
Run Certbot HTTPS issued and renewed
Write a deploy script git push
Safer releases

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
Deploys and rollbacks ›
  1. v13 · Health check passedTraffic switched to v13 · v12 kept warm
  2. v13 · Failing during the bake windowHealth check no longer passing
  3. v12 · Serving againRolled back automatically
Choose your infrastructure

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.

Your own serverAvailable now
  • Any Ubuntu 20.04+ or Debian 11+ VPS with its own public IPv4 address
  • Your provider bills the server; Raklane bills a management fee per server, hourly, from a prepaid wallet
  • Apps and databases included up to an allowance
Raklane CloudAvailable now
  • No server to rent or maintain
  • Pay by the hour for what your apps reserve, or a flat monthly plan
  • Managed Postgres and MySQL
Compare prices ›
Security and architecture

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.
Run on your server
# 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.com

Who 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
Archive uploads

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.
Pricing

Simple prices.
In the open.

Prepaid. No contracts. No card on file.

Dedicatedfrom IDR 84,000/monthA fixed slice of compute at a flat price.
Your own serversfrom IDR 40 You pay your provider. We never bill the compute.
Compare

Less plumbing.
More shipping.

On a bare VPS

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
On Raklane

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.

RaklaneBare VPSSelf-hosted panelGlobal 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.