Orbit: Push to Git, Run on Flux

Fluxers! Here is a small secret about the page you are reading: it was deployed by Orbit. We write an article, push it to a Git repository, and Orbit builds the site and rolls it out to Flux nodes on its own. Nobody logs into a server. Nobody writes a Dockerfile.

Orbit is Flux’s deploy-from-Git platform, and it has quietly become one of the most popular ways to run anything on the network. Its image, runonflux/orbit, is the single most deployed public image on Flux — behind 243 public applications at the time of writing, ahead of every game server and database, plus well over a hundred private deployments on top.

What it does

Point Orbit at a repository on GitHub, GitLab or Bitbucket. It works out what the project is, installs the right tools, builds it, and deploys it across Flux nodes. From then on, every push to your chosen branch triggers a fresh build and deploy automatically.

That is the whole workflow. You keep writing code the way you already do; Orbit turns commits into a running application.

It figures out your stack

Orbit supports more than 100 frameworks and runtimes, and detects them from the files already in your repository rather than asking you to describe them:

• JavaScript and TypeScript — Next.js, Vite, React, Vue, Nuxt, Remix, SvelteKit, Astro, Express and more, with the Node version read from .nvmrc or package.json, and Bun supported too.
• Python — Django, Flask and FastAPI, with the version from runtime.txt or pyproject.toml.
• Ruby and PHP — Rails and Laravel, versions from .ruby-version, Gemfile and composer.json.
• Go, Rust, Java and .NET — Gin, Actix, Rocket, Spring Boot and ASP.NET Core, versions from go.mod, Cargo.toml, pom.xml or build.gradle, and the .csproj target framework.
• Elixir, Erlang and Dart as well.

Static sites and single-page apps go through the same zero-configuration flow as full-stack applications.

Not just static sites

This is one of Orbit’s real advantages over static-first hosts. Orbit runs your application as a full, long-running container, so backends and servers work natively — Django, Rails, Express, Go and Rust APIs, background workers and persistent processes, the things serverless platforms handle awkwardly or not at all.

Built to keep you online

• Automatic rollback. A failed build never replaces a working deployment. Orbit keeps the last good version live, so a bad commit cannot take your site down, and build logs stream in real time so you can see what went wrong.
• Deploy previews. Pull requests and branches can get their own preview deployments.
• Monorepos. Set PROJECT_PATH to a subfolder and Orbit builds just that package, so several apps can live in one repository.
• Custom domains with SSL. Point a CNAME at your deployment and certificates are handled automatically through the Flux reverse-proxy network.
• Location choice. Pick where in the world your instances run.
• Polling mode. If you cannot install a webhook, Orbit can watch your branch instead.

Genuinely decentralized hosting

What sets Orbit apart from Vercel or Netlify is where the application ends up. Your container runs on real, dedicated hardware across Flux’s network of thousands of independently operated nodes, run by separate operators around the world — not in one company’s data centre. The Standard and Pro plans run your app on two nodes at once, so there is no single point of control and no single point of failure.

And because the capacity comes from a decentralized network rather than a centralised provider’s margins, the same money buys dedicated CPU and RAM rather than a shared, metered allowance.

Plans

• Custom — from $0.99 a month: configure your own resources, from 0.1 to 15 cores, 100 MB to 59 GB of RAM, and 1 to 820 GB of storage, across 1 to 3 instances.
• Standard — $2.49 a month: 1.5 vCPU, 4 GB RAM, 15 GB SSD/NVMe, two instances.
• Pro — $3.99 a month: 2 vCPU, 6 GB RAM, 20 GB SSD/NVMe, two instances.

Pay by card through Stripe, or in FLUX with Zelcore or SSP. You never need to own crypto to use Orbit.

Let an AI agent drive it

Orbit includes its own MCP server, so a compatible AI agent can inspect repositories, validate a deployment, deploy apps, read logs, check status, trigger builds, control instances and renew subscriptions — with you approving each action in your agent client. Connect one from the Orbit dashboard under Connect an agent.

Start in three clicks

Head to orbit.runonflux.com or find it in the Flux apps hub, paste your repository URL, set the port, and launch. The full guide, including framework specifics and troubleshooting, is in the Flux documentation under Deploy with Git.

Then push a commit, and watch it go live. It is how this blog gets published every day.