Shipping code should feel like one motion
Push, get feedback, merge. Lorx brings your code, your reviews and your CI together so nothing slows you down in between.
We're building the place where every change is built, tested and reviewed before it reaches your main branch, on the git you already know.
- Runs only what changed
- Skips what already passed
- On the git you know
Four principles behind every feature
They decide what we build, 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.
Your laptop is CI
What runs on your machine with bit is exactly what Lorx runs. No more pushing to find out.
No lock-in
Bring your history in, take it out whenever you like. Your code is always yours.
Fast by default
Work that already passed never runs twice. Your time goes to the change, not the wait.
Welcome back!
Sign in to review and merge on the go.
One push, everything in step
Everything on Lorx starts with a push. From there, your code, your review and your CI move together.
Push from any git tool. Your branches, history and activity show up straight away.
It works out which jobs your change affects and skips anything that already passed. Run it with bit before you push.
Open a change request, talk it through line by line and resolve every thread.
Merge when it's ready, or let it merge itself. Protected branches make sure main only changes through review.
How we keep your code safe
You decide who can change what, and nothing sensitive happens on your account without you knowing about it.
Protected branches
Keep direct pushes, force pushes and deletions off the branches that matter. Changes reach them through review.
Scoped access tokens
Each tool gets its own token, limited to the repositories and access it needs. Revoke one without touching the rest.
Confirm what matters
Adding a key or creating a token asks for your password again, and every new key sends you an email.
A log of every sign-in
See every sign-in and security change on your account, with where it came from.
Staying safe: three habits we recommend
- Give every tool its own token, with only the access it needs.
- Protect main, so every change reaches it through a change request.
- Check your security log now and then, and revoke what you no longer use.
Come ship with us
Create your account and push your first repository in a minute.