The code forge that reviews before you push
Host your code on plain git, run CI with a native actions engine, and get an automatic review on every change — from the web or from bit, our Rust CLI.
CR #42anna · feat/dag5/5checks ✓annaApproved · CR #42✓approved
lorx review2 findings · lease.rs!1 high
alivaMerged · CR #39✓mergedEverything Your Code Needs, Built In
Hosting, CI, code review and the CLI come from one team and one codebase, so they work together from the first push.
Explore the productActions
Engine
Workflow run #318
2m 31s
Automatic
Code Review
Review findings
Change
Requests
#42
Git hosting that's just git
Every repository is a real git repository. Clone it however you like, and bring your history over with one push.
Runners on any machine
Warm microVMs start jobs in under a second. Attach your own machines to any Lorx, even the cloud.
From push to merge in three steps
One push starts CI and an automatic review at the same time, so feedback arrives before your teammates even open the change.
Add Lorx as your git remote and push. Any git client works, and nothing about your repository changes.
The jobs in .lorx/ci.yml that your change affects run automatically, and the review engine leaves inline comments with a severity on each one.
Resolve the findings, watch the checks turn green, and merge. Branch protection enforces both.
Try bit
cargo install --git https://github.com/hallelx2/lorx bit
Your code, protected at every step
Every job runs in its own sandbox, every push lands on three replicas, and nothing reaches your main branch without the checks you require.
Sandboxed runners
Containers for your own branches. Firecracker microVMs for untrusted changes from forks.
Scoped secrets
Secrets are masked in logs and never exposed to runs from forks.
Replicated storage
Every push is written to three replicas and acknowledged on quorum.
Branch protection
Require passing CI and a clean review before anything merges.
lorx/lorx · this week
bit: add cr createhallelx2 · CR #44+212Approvedactions: plan job graphanna · CR #42+38Approvedrunner: renew leasesabrar · CR #41+9Changesdocs: architecturealiva · CR #40+64PendingBuilt for teams that ship every day
Code owners, required checks and a shared review queue keep a busy repository moving without anything slipping through.
- Branch protection with required checks
- Code owners and multi-step approvals
- Self-hosted runners with labels
- Lorx Projects: issues that move themselves on push, review and merge
Choose How You Run Lorx
Lorx is open source, and Cloud runs the same code. No feature is Cloud-only — Cloud adds the operations: replication, a microVM fleet and a global edge.
Compare every featureSelf-hosted
For teams who run their own infrastructure
Free · Apache-2.0
- Hosting, actions, review and Projects
- Everything in one process with
lorx serve - Bring your own review model
Lorx Cloud
For teams who want it managed
Soon · [pricing TBA]
- The same code, fully managed
- A warm microVM runner fleet
- Replicated storage and a global edge
No. Every repository on Lorx is a real git repository, served over git's own HTTP and SSH protocols. You keep git, your editor and your habits; Lorx adds the forge around them.
No. Plain git works for everything. bit adds what git can't do on its own: opening change requests, running CI locally and reviewing before you push. Anything bit doesn't recognise is passed to git.
Yes. bit ci import converts a GitHub Actions workflow into one .lorx/ci.yml file, where top-level keys are jobs and a bare string is a command. Toolchains and caches are inferred from your lockfiles, so most of the setup steps disappear.
The diff, the files it touches, your repository's rules in .lorx/review.yml and AGENTS.md, and earlier review threads. It posts inline comments with a severity and reports a check that branch protection can require. Self-hosted, you choose the model: Anthropic, OpenAI or one you run locally.
Yes, and safely. Assigning an issue to an agent gives it a copy-on-write workspace and a short-lived token scoped to one repo, branch pattern and set of actions. Every change records which agent, model, session and task produced it, and an operation log lets you undo any step.
Get the bit Command Line
bit is git with your forge built in: a single static binary, written in Rust. Open change requests, run CI locally and review your changes before you push, all from the terminal.