Built to be kept, not leased

Somewhere on your computer right now is a folder of things you can no longer open. A document in a format the company retired. Photos locked inside an app that shut down. A tool you paid for every month for years, that one morning simply told you your plan had changed. You didn’t lose those things to fire or flood. You lost them to a business decision made in a room you were never in. This is the ordinary condition of modern software: you rarely own what you use. You rent it, on terms that can be revised while you sleep.

We think that’s a strange way to build the tools an institution runs on. So we don’t.

Rented software is software you can lose

A subscription is a fine thing when it fits what you’re actually doing: paying, month to month, for a service someone genuinely keeps running on your behalf. We’re not against being paid. We’re against the bargain hidden inside so much of today’s software, which is not really “pay us and we’ll keep this running” but “pay us forever, or lose access to your own work.” The data is yours in spirit and theirs in practice. The features you built your week around can be moved behind a higher tier, or deprecated, or folded into something you never asked for. And if the company is acquired, or pivots, or simply stops caring, the thing you leaned on leans back on nothing.

For most software this is merely annoying. For an institution it’s a real danger, because an institution’s records aren’t last quarter’s convenience. They are its memory. A parish knows who was baptized, who was married, who was buried, and when, going back further than anyone now living. That is not data to be held hostage by a payment portal. It is a trust, handed forward from people who are gone to people not yet born.

What it means to build something to be kept

To be kept and not leased, a piece of software has to be built differently from the ground up, not dressed up that way in the marketing. It shows in the boring, load-bearing decisions most people never see. A few of the ones we hold ourselves to:

• Your records live in ordinary, open formats you can read without us, not locked in a shape only our software understands.
• You can export everything, in full, whenever you want, without asking permission and without a phone call to “retention.”
• The door out is as wide as the door in. Leaving is a feature, not a punishment.
• Nothing essential hides behind the next tier up. The thing you depend on doesn’t quietly become the thing you have to pay more to keep.
• If we vanished tomorrow, you would still have every name, every date, every record: intact, portable, and yours.

That last one is the real test, and we hold it on purpose. A studio that builds to be kept has to be honest about its own mortality. We intend to be here for a very long time, and we make our work to be tended for decades rather than shipped and abandoned. But intending to last and forcing you to bet on it are two different things. The healthiest version of this relationship is the one where you stay because the work is good, not because leaving would cost you your history.

Software you can’t leave isn’t loyalty. It’s a lock. We’d rather earn the years than trap them.

Stewardship measures time differently

Rented software is built to a rhythm of quarters. Growth targets, churn numbers, the next release cadence. There’s nothing evil in any of it, but it pulls a company’s attention toward this month, always this month. A tool built to win this month tends to age like a rental car. Nobody’s waxing it. Nobody expects to keep it.

The institutions we build for don’t live at that tempo. A church measures time in feast days and generations. A monastery thinks in centuries without irony. A school counts its life in the students who pass through and come back with their own children. These are long-memory communities, and they can feel, instantly, when a tool was made by people just passing through. It shows in the small carelessnesses: the label that’s almost right, the workflow that assumes you’ll only ever do this once, the update that breaks the thing you relied on because someone upstream had a metric to move.

Building to be kept means building at their tempo instead of ours. It means treating your records the way a good mason treats a wall: plumb, square, and meant to outlast the person who laid it. It means writing software the way you’d build a room your grandchildren will stand in, not the way you’d order an office chair you’ll replace in three years and never think about again. A building is inherited and tended. A chair is used up and thrown out. Almost all software today is a chair. We’re trying to make buildings.

Kept, and cared for

None of this makes us slow, or precious, or nostalgic. Quite the opposite. It is freeing. When you’re not spending your ingenuity on making software hard to leave, you get to spend all of it on making software good to stay with. We can be small, answer our own email, and know the people on the other end by name, because we’re not running on the treadmill of extracting a little more from every account each quarter. The care goes into the work, where you can feel it.

So here is the promise underneath all of it, plainly. What you make with our tools is yours. Your records are yours. Your history is yours to hold, to move, to carry into whatever comes next, with us or without us. We’d love for it to be with us, for a very long time. But we want you to stay because the work keeps deserving you, not because we bricked up the exit while you weren’t looking.

Build a thing to be kept. Build it so it can be handed forward. Then spend your days making it worth keeping. It is a hopeful way to work, because it assumes there will be someone on the other end of the years to hand it to.