FAQ
Quick answers to common questions about deploying and running apps on Raklane.
Do I need a Dockerfile?
No. Raklane builds your app using Cloud Native Buildpacks, which detect your language/framework automatically from common project files (package.json, requirements.txt, go.mod, Gemfile, and similar) and produce a container image without you writing one. If your repository already has a Dockerfile, Raklane builds that instead. You can point it at another path or always use buildpacks in the app's Settings → Build. If you don't have a repo at all, a Static app skips building entirely and just serves your files. A docker-compose.yml can be deployed as a stack (in invite-only early access): each service becomes an app or a database.
How do I know if my deploy worked?
Check your App's Status page. active means it's live and serving traffic. See Logs & Status.
Does Raklane cause downtime when I deploy? No — deploys are zero-downtime by default. New replicas are started and health-checked while the old ones keep serving traffic; only a healthy new deploy ever receives traffic. See Deploying Your App.
Can I roll back a bad deploy? If a new deploy fails its health check, Raklane never cuts traffic to it in the first place — the previous version keeps running automatically, nothing to do. If a problem only shows up after cutover, Raklane keeps the previous release warm for a short window and rolls back to it automatically if something goes wrong during that window. See Deploying Your App.
Why didn't my environment variable change do anything? It will — on your next deploy. Running containers don't pick up environment variable changes live; redeploy to apply them. See Environment Variables.
Can I deploy from a private repository?
Yes — create a token or ssh_key secret with access to the repo and reference it in your App's source configuration. See Secrets → Private repositories.
Can deploys happen automatically when I push code? Yes. In the default Auto Deploy mode, Raklane checks your branch for new commits about once a minute on any Git host, and a GitHub webhook makes it instant. You can also choose to review a diff first, or pin a release. See Auto-Deploy & Deploy Modes.
Where do my apps run? On a server you own — that's Bring Your Own Compute. Register any Ubuntu or Debian server with one command, and Raklane deploys onto it while you keep full control of it.
Can I run apps on Raklane's servers instead? Soon. Raklane Cloud adds two more places an app can run, both on Raklane's servers: PAYG (billed per resource used) and Dedicated (a flat subscription). Until it opens, every app runs on a BYOC server. See Where Your App Runs.
Does Raklane need SSH access or cloud API keys for my BYOC server? No. You run one install command yourself. After that, a small agent on your server opens an outbound, encrypted connection to Raklane. Raklane never logs into your server and never asks for cloud credentials. See BYOC: Overview & How It Works.
Does my BYOC server build my code? No. Builds always run on Raklane. Your server only pulls the finished image and runs it, so it doesn't need spare memory or build tools.
How is Raklane different from a server panel or a managed app platform? Compared with a server panel (self-hosted or hosted), Raklane builds your code off your server, never logs into it over SSH, and rolls a bad release back on its own. Compared with a managed app platform, your app runs on a server you choose and keep, and you pay a small fee in rupiah instead of usage in USD. Some things aren't here yet, such as one-click apps. See Raklane Compared.
Does traffic to my BYOC app go through Raklane? No. Visitors connect directly to your server, where Caddy serves your app over HTTPS. Your apps even keep serving if Raklane's control plane is temporarily unreachable.
Can I use a cheap VPS that shares its public IP with other servers (port forwarding / NAT VPS)?
Not currently. Your apps are served on ports 80/443 of your server's public IP, and on a shared-IP VPS those ports belong to the provider, not to you. The server may enroll and show Healthy, but your apps won't be reachable. Use a server with its own public IPv4. See Shared-IP VPS are not supported.
What happens to my BYOC apps if my wallet runs out? Nothing stops. If a BYOC management fee stays unpaid past the grace period, only new deploys to your servers are paused until you top up. See BYOC Billing.
Can I spread one app across several of my own servers? Not yet. Each registered server is its own cluster, and an app's replicas all run on the server you choose. See Managing BYOC Servers.
Does Raklane back up databases on my BYOC server?
Not yet — built-in backups are coming soon. Until then, the data lives only on your server's disk, so back it up yourself with your provider's disk snapshots or pg_dump/mysqldump.
Why does my deploy say "waiting for server"? Raklane is starting a server with room for your app. It continues on its own, usually within a few minutes, and your build runs in the meantime.
How do I run more than one instance of my app? Set a replica count when deploying. See Deploying Your App → Replicas.
How do I see how much CPU and memory my app actually uses? Open the app's Metrics tab — live usage against your limits, history up to 30 days, and hints when you're close to a limit or oversized. The Processes tab shows what's running inside each replica. See Metrics & Processes.
Can I limit how much CPU/memory my app uses? Yes, per replica, when deploying. See Deploying Your App → Resource limits.
What's the difference between a Deployment app and a Static app? A Deployment app is built and run as a container process (a web app, API, or service). A Static app is served as-is with no build step or server-side process — use it for plain HTML/CSS/JS. This is chosen when you create the app and can't be changed later. See Managing Your App.
Can I invite people to work on my apps with me? Yes — invite teammates into your Organization with a role that controls what they can do. See Teams & Organizations.
Can Raklane provision a database for me? Yes — Postgres or MySQL, provisioned per-project so every App in it can connect. See Databases.
How does billing work? Raklane uses a prepaid wallet — top up credit, and any BYOC management fee is deducted from it. Your server's compute is billed by your provider, never by Raklane. There's no card kept on file. See Billing & Wallet.
Can I get a refund on a top-up? No. Top-ups are final: once credit is added to your wallet, it can't be refunded or withdrawn back to your bank account. It can only be spent on Raklane. Top up only what you expect to use. (A top-up request that's rejected during review never reaches your wallet, so there's nothing to refund.) See Billing & Wallet.
Can I scale my app up without redeploying it? Yes — change the replica count or CPU/memory limits directly from your App's Resources page; Raklane applies it in the background without a build or restart. See Deploying Your App → Changing replicas or resources without redeploying.