nibrun

One-click deployment for any single-binary app.

Small apps don't need to scale. They need a machine and a disk.

Try it out

Visit nibrun.com/apps to see the available apps you can deploy in one click.

Why

A compiled binary is already a whole application in one file. Whatever language produced it, nothing has to be installed on the other side. The only two things it still needs are somewhere to run and somewhere to read and write files.

For an app that five people use, most of the rest is ceremony:

What it usually gets	What it actually needs
❌ A container image	✅ A machine to run on
❌ A managed Postgres	✅ A disk to write to
❌ An object storage bucket
❌ A load balancer, for one instance
❌ A VM to ssh into
❌ A firewall to open
❌ TLS to renew
❌ An OS to keep updated

What it is

nibrun is those two things and nothing else: a Firecracker microVM of its own (1 vCPU, 256 MiB) and a data/ directory that survives every redeploy. It answers on an HTTPS subdomain the moment it boots, sleeps after five minutes idle, and wakes on the next request in ~120 ms.

If your app needs to be more than one machine, it has outgrown this — and that is not a roadmap, it is the design.

Deploy your own app

Create an HTTP app (use the bun-full-stack-starter template) and compile it to a single Linux x86_64 binary. Then deploy it:

For Agents

Prepare the app and deploy it to nibrun using the deploy-to-nibrun skill.

Install it using:

npx skills add ilbertt/nibrun

For Humans

Use the dashboard

Drag and drop the binary onto app.nibrun.com.

Use the CLI

curl -fsSL https://nibrun.com/install.sh | sh

nib run ./my-server

Take it with you

nib apps export .
tar -xzf my-app.tar.gz
./my-server

The same binary you uploaded, the same bytes that were on the disk, and a .env of the variables it was deployed with. There is no managed database to migrate off, because there never was one.