From code to a live address
Most products start the same way: some code on a laptop and the need to put it in front of people. Rimbra takes that code as it is. Connect a GitHub repository, or drop in a folder, a ZIP or a static site, and Rimbra works out what it is, installs what it needs, builds it and starts it.
Every project gets a free address at your-project.rimbra.app from its first deploy, served over HTTPS. When you are ready, put your own domain in front of it. The address never changes when you ship a new version, so links you share keep working.
It knows your framework
Rimbra reads your files to decide how to run them. You do not write a config file for the common cases.
| Your files | Runs as |
|---|---|
| package.json with next | Next.js: builds, then runs the Next.js server |
| Vite, Astro, SvelteKit or Nuxt config | Builds and serves the output |
| index.html | A static site, served as files |
| requirements.txt or pyproject.toml | Python with Uvicorn, Gunicorn or Django |
| composer.json or index.php | PHP |
| go.mod, Cargo.toml, Gemfile, pom.xml | Go, Rust, Ruby or Java |
| Dockerfile | Your container, exactly as you wrote it |
One rule for servers. If your app is a server, listen on the port in the PORT environment variable. Rimbra sets it and routes your address to it.
Watch every build
Each deploy streams its log line by line, from installing dependencies to the moment your app answers. If a build stops, the reason is in the last few lines, next to the commit or upload that caused it.
Deployments move through Queued, Building and Ready, and every one is kept, so you can open an older build, read its log and see what it shipped.
Releases without downtime
A new version starts next to the one that is running. Traffic moves only once the new version answers, then the old one stops. If a build fails, the previous version keeps serving and your visitors never see a broken release.
Settings when you need them
- Root directory, for repositories where the app lives in a subfolder.
- Install, build and start commands, when the defaults are not what you want.
- Environment variables and secrets, added one at a time or imported from a .env file.
- A database connection, added as a variable in one step.
Questions
Does my app need anything special to run?
Only one thing for servers: listen on the port in the PORT environment variable. Static sites and frontends need nothing.
What happens if a build fails?
The live version keeps serving. The failed deployment shows the error in its log, and you can fix it and push again or choose Redeploy.
Can I bring my own Dockerfile?
Yes. When a Dockerfile is present, Rimbra builds and runs your container and skips its own detection.
How many projects can I run?
Free includes 4 projects and 200 build minutes a month. Launch, Pro and Scale raise that to 12, 30 and 100 projects. You can also add single projects to any plan.