A Forge That Works the Way git Does
Lorx exists so that shipping code feels like one motion: push, get feedback, merge.
We're building a code forge where every push is built, tested and reviewed before a teammate has to look — on plain git, in the open, for teams of any size.
Four principles behind every feature
They decide what we build, what we charge for, and what we'll never ask you to give up.
git first
We never replace git. Your repository is always a real one you can take anywhere.
Local is CI
What runs on your laptop with bit is exactly what runs on the server.
Built for agents
Workspaces, scoped tokens and provenance, so people and agents ship side by side.
One codebase
Cloud and self-hosted are the same code. No feature is Cloud-only.
Welcome back!
Sign in to review and merge on the go.
One Push, Two Engines
Lorx is a small set of Rust services — or one process, with lorx serve. A push becomes an event; the actions engine turns it into jobs and the review engine turns it into comments.
Serves git over HTTPS and SSH using gix, handles the API and sign-in, and emits an event on every push.
Reads .lorx/ci.yml, works out which jobs your change affects, skips steps that already passed, and schedules the rest onto runners.
Leases a job with a heartbeat, starts a warm microVM next to your git storage, and streams logs back. If a runner dies, its job is requeued.
Reads the change, the files it touches and your rules, then posts inline findings and a check status. Self-hosted, it runs on the model you choose.
How we keep your code safe
A forge runs other people's code all day. We isolate every job, keep secrets away from untrusted runs, and let you decide what reaches your main branch.
Sandboxed runners
Every job gets its own container. Changes from forks run in Firecracker microVMs.
Scoped tokens and secrets
Secrets never reach fork runs. Agents get short-lived tokens limited to one repo, branch pattern, path and action.
Replicated storage
Every push is written to three replicas and acknowledged on quorum. git keeps working even if the web app is down.
Branch protection
Require passing CI and a clean review before anything merges.
Staying safe: three habits we recommend
- Never commit a token. Store it as a scoped secret and reference it from your workflow.
- Make the review check required on main, and give agents tokens scoped to a branch pattern.
- Use microVM runners for public repositories that accept changes from forks.
Want to build this with us?
Lorx is open source. Issues, ideas and pull requests are all welcome.