We got tired of renting our own business.
ARK is a small team building the kind of software we wanted to use ourselves: tools that live on servers we control, store data we can read, and bend to whatever shape our business happens to be this quarter. Six apps, one philosophy, no monthly bill for the privilege of logging in.
Why this exists
Somewhere along the way, “software” stopped meaning something you buy and started meaning something you rent. The CRM bill goes up every year. The chat tool doubles its seat price. The docs platform deprecates the feature you depend on, and there is no version to pin to — you get whatever they decide to ship on Tuesday.
Your data lives on their disks. Your workflows live inside their product decisions. The exit ramp gets narrower every time they add a feature.
We think that is a bad deal — especially now, when a small team with AI can reasonably maintain a stack of tools that used to require a whole vendor behind them. ARK is the stack we built for ourselves, packaged for anyone else who would rather own their tools than rent them.
The philosophy
Three ideas we keep coming back to.
Buy once. Keep forever.
One payment, the full source. If our servers disappear tomorrow, your CRM still runs. Perpetual license, no phone-home, no kill switch. The code is on your machine because it is yours.
Your database, your rules.
ARK apps run on your Supabase project. Every row, every file, every audit log lives in an account you control. Export it, migrate it, query it, back it up with your existing tooling. Nobody else needs a seat at your database.
Fork it. Shape it. Ship it.
The code is readable, the schema is documented, and Claude Code (or your AI of choice) can drop into the repo and make the changes you need. Add a field, rewire a workflow, bolt on an integration — without waiting on a roadmap.
All your tools, traveling together.
An ark is a vessel that carries everything important through a storm. That is how we think about a business’s software: the CRM, the chat, the standups, the docs, the meeting notes, the dashboards — they all need to make it across together, through every migration, rebrand, and pivot.
Each ARK product is an animal on the ark. They are distinct creatures with their own personalities, but they share a boat. One login, one database, one backup strategy, one set of people who understand the whole thing.
When you outgrow one, the rest come with you. When you want to change one, the rest keep working. The fleet moves together.
Who this is for
Operators who like owning things.
Small teams, technical founders, boutique agencies — anyone who runs a lean shop and would rather deploy once than approve a vendor PO every quarter.
People who want to change the thing.
If you have ever filed a feature request and watched it sit for two years, ARK is for you. The codebase is small, readable, and designed to be edited — by you, or by an AI you point at it.
What ARK is not
We are not a Fortune 500 company. We do not have a sales team, a customer success org, or a pager rotation for your deployment. Support is email, from the people who wrote the code, and it is best-effort.
ARK apps are self-hosted. That means you are the ops team. We make the deployment path as boring as possible (one-click Supabase and Vercel, documented end to end), but you will at some point look at a database and a DNS record. If that sounds fine, welcome in. If it sounds like a dealbreaker, a SaaS competitor is probably a better fit.
Board the ark.
Six apps. One payment each, or grab the whole suite. Your servers, your data, your code, forever.