Incorporated · Ottawa
CODE LIFELINE
We write software that answers to no one else’s server. Our own inference, our own git, our own distribution — and the same standard for the systems we build for you.
Unison
The first string in the Hendricks house.
Third parties
No one else’s servers in the critical path.
Assets
Built, shipped, and still maintained.
Lines
Across the seven, and still being written.
Ⅰ · Who we are
One studio. Our own stack.
Code Lifeline Inc. is a software studio in Ottawa. We write code, we ship it, and then we keep it running — which is the part that tells you whether any of the earlier decisions were correct.
What makes the work unusual is where it lives. Our git server is ours. The eighty-billion-parameter model our tools talk to runs on a workstation in this building, not in a datacentre we rent by the token. Our Android app distributes itself from our own manifest. Our sync engine has no central node to lose. None of that is ideology; it is what happens when you keep asking who, exactly, you would be calling when it breaks.
Code Lifeline is the first holding of Hendricks Industries, where it is the 1:1 string — the unison, the fundamental, the note the rest is measured against.
“Anyone can ship a thing once. The question is who answers the phone in year three.”
Code Lifeline Inc.
Ⅱ · The assets
Seven things we built and still run.
Not case studies for clients. These are ours — written here, hosted here, maintained here. They are the argument.
AI Relic
Private infrastructure · active development
A self-hosted AI stack — an 80-billion-parameter coding model on our own GPU, and the coding environment built around it. Nothing leaves the machine.
Read more →Relic
Live in production
A Discord agent with a memory, a voice and an entire simulated economy underneath it.
Read more →Ruins Launcher
Shipping over the air · build 25
An Android home screen that grew into a phone OS layer — and updates itself over the air from our own server.
Read more →Ruins Empire
Live · ruinsempire.com
A community that runs like an organisation and broadcasts like a network: ranks, vetting, shifts and casework on one side, a 24/7 radio station and scheduled TV on the other.
Read more →Conduit
In production · powers two live apps
A media store built around a simple observation: most of what you keep, nobody is looking at. It tiers storage by what is actually being used.
Read more →Univerge
In development · live at univerge.life
A team workspace where chat and time-tracked task boards sit side by side, and one profile carries your affiliations between instances.
Read more →Gravity Sync
Prototype
Peer-to-peer multi-master replication for code projects. Every node is equal; there is no server in the middle.
Read more →Ⅲ · What we do
Work for hire, on the same terms.
We build for other people too, and we build it the way we build our own: so that you could, in principle, fire us and still own everything that matters.
Ⅳ · How we build
Three standards.
Short enough to remember, which is the only reason a list like this ever changes anything.
Own the stack
If a system matters, it should not stop working because a company you do not control changed its pricing, deprecated an endpoint or went away. We build so that the critical path is yours.
Ship it, then keep it
Writing software is the easy half. We stay with what we build, which is the only way to find out whether the decisions were any good.
Say the true thing
An honest estimate beats a comfortable one. If a project should be smaller, or bought instead of built, or not built at all, we would rather tell you early.
Ⅴ · Contact
Open a line.
Something to build, something to take over, or something you are not sure is worth building at all. All three are good reasons to write.
[email protected]