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

How Raklane Works

An end-to-end walkthrough: from your code to a running, reachable app — builds, releases, where apps run, how traffic reaches them, and how you're billed.

This page follows one app from source code to live traffic, so you know what Raklane is doing at every step and where to look when something goes wrong. It assumes you've skimmed Core Concepts.

The whole journey at a glance

1. Your code

An app's source is either a Git repository and branch, or an uploaded archive (.zip/.tar). Private repositories use an access token or SSH key stored as a Secret. Changing the source doesn't deploy anything by itself — it only changes what the next deploy builds.

2. Triggering a deploy

A deploy starts when you:

  • click Deploy or Redeploy in the dashboard,
  • push to the configured branch with auto-deploy set up, or
  • move the app to a different location (Settings → Deployment location).

Deploys are asynchronous: Raklane records the new release and returns immediately, and the dashboard shows progress. Clicking Deploy again while one is in progress doesn't queue a duplicate.

3. The build

Raklane clones your source and runs Cloud Native Buildpacks, which detect your language from files like package.json, requirements.txt, go.mod, or Gemfile and produce a container image — no Dockerfile needed. If your repository has a Dockerfile, Raklane builds that instead. Static apps skip this and serve your files as-is.

The build always happens on Raklane's build system, including for apps that run on your own BYOC server. Your servers never need build tools or spare memory for compiling, and every replica runs the exact same image.

Build output is in the app's Logs (build logs), grouped by stage. If a deploy fails before your app starts, this is where to look.

4. Where your app runs

Every app runs in a deployment location, which you choose when you create it and can change later:

Runs onYou pay
BYOCA server you own and registeredYour provider for the server; Raklane at most a management fee
PAYG cluster (coming soon)Raklane's managed serversPer resource used, from your wallet
Dedicated cluster (coming soon)Raklane's managed servers, from your reserved poolA flat hourly/monthly subscription

Raklane Cloud is coming soon. PAYG and Dedicated clusters aren't open yet, so today every app runs on a BYOC server.

Raklane then picks a machine within that location with enough room for your app's CPU and memory requests. If there isn't enough room, the deploy is rejected up front, rather than failing halfway.

On managed compute, Raklane may start servers on demand. If no server is running when you deploy, your deploy shows waiting for server for a few minutes while one boots. The build keeps going in the meantime, so the wait usually overlaps with it.

See Where Your App Runs for help choosing.

5. Rollout and health checks

Raklane starts the new container(s) next to the currently running ones. Each new replica must pass a health check — an HTTP request to your app's port by default, or a plain TCP connection — before it's considered ready.

  • If a new replica fails its health check, the deploy is aborted. The old release keeps serving, untouched. The new release is marked failed.
  • If they all pass, traffic cuts over.

6. Cutover and the bake window

After cutover, Raklane keeps the previous release running for a short bake window (status baking). If the new release goes bad during that window, Raklane automatically rolls back to the previous one (status rolled_back). Otherwise the new release becomes active and the old one is stopped.

See Deploying Your App for all the details, including canceling a deploy and forcing a rollback.

7. How traffic reaches your app

Every app gets a free default URL the moment it's deployed, and can have any number of custom domains. HTTPS certificates are issued and renewed automatically.

How requests travel depends on where the app runs:

On a PAYG or Dedicated cluster (Raklane's managed compute), your app's hostnames point at Raklane. Raklane's ingress terminates HTTPS and forwards each request to one of your app's healthy replicas. Servers that run your app don't accept connections from the internet at all — Raklane reaches them over an encrypted connection the server opens outward. Your URLs and DNS never change, even when the servers underneath do.

On a BYOC server (your own), your app's hostnames point at your server's IP. Caddy on your server terminates HTTPS and forwards to your container. Visitor traffic never passes through Raklane. See BYOC: Overview & How It Works.

When there are several replicas, requests are spread across all the healthy ones. A replica that becomes unhealthy is taken out of rotation and restarted automatically.

8. While your app is running

Raklane keeps watching every running container:

  • Crashes are restarted automatically, with backoff for an app that keeps crashing.
  • Status shows the active release, its replicas, and domains. Logs shows build and runtime output. Metrics shows CPU, memory, network, and disk usage live and over time, with sizing hints, and Processes shows what's running inside each replica.
  • Scale replicas or CPU/memory from the Resources page without a full redeploy.
  • Pause an app to stop it without losing anything, and resume it later.

9. Databases

A Database (Postgres or MySQL) belongs to a project, not a single app, and runs independently of your app's deploys. Like apps, it runs on your BYOC server (sized by you) — or, once Raklane Cloud opens, on Raklane's managed compute (with a hosting plan). Put its connection string in an environment variable for each app that needs it.

10. Billing

Raklane uses a prepaid wallet. Any BYOC management fee is deducted from it — and, once Raklane Cloud opens, PAYG usage, dedicated hosting subscriptions and database hosting plans too. There's no card on file.

Where to go next