What we build for ourselves
Before we sell anyone a tool, we use it ourselves. This site is deployed with Orbit. Here's what we've published, with its real status and no dressing up: what's already in production, what works but you can't download yet, and what you can just take for free.
Orbit
Deploy your sites to your own VPS with one command.
See projectOrbit Desktop
A point-and-click interface for Orbit that runs on your laptop, not your server.
See projectTAPE
A multi-site editorial engine for controlled autonomous publishing.
See projectThemes
WordPress themes designed and coded by hand.
See projectEvery project says where it stands
The four are at very different stages, and it would be easy to make them look alike. We don't: the status chip comes before the name, the spec panel gives the version and whether the repository is public, and where there is nothing to download yet, the page says so up front and says why.
Installable today, with a published version. We run it ourselves.
It works and it is tested, and there are screenshots of it here. What there is not, yet, is a download.
Downloadable today, nothing asked in return. The WordPress themes.
It's the part of the work a client site never shows
A case study shows the result. A repository shows the decisions: what was discarded, what was measured, and why a decision went one way and not the other. If you're going to trust us with your infrastructure, this says more about us than any services page.
We use it before we recommend it
Orbit deploys intervolutions.com. If it breaks, it breaks us first.
MIT where we can
Take it, fork it, run it on your own server. There's no paid tier hiding behind it.
Documented for whoever has to audit it
Architecture, threat model and the decisions that were discarded, not just the install steps.
Ready to build something big?
Pick what you want to build, add a few extras, and watch your plan take shape in real time. No emails, no waiting. Go ahead — play.