It started the way most useful things do, by accident. I was building bigger projects with AI, the kind that take weeks instead of an afternoon, and I kept hitting the same wall. The work never stopped feeling like a forever-building process. I could not see what was done, what was left, or where the whole thing actually stood. I have spent more than five years in software consulting, so I know the stacks companies bolt together to run this. And most of that machinery makes no sense when it is just you, at home, with a Claude subscription and an idea.
So I started asking a simpler question. What are we actually renting, and why?
You already own the hard part
Take compute. Almost everyone already has a machine that could do this. The laptop you work on, the old backup one in a drawer, the desktop you stopped upgrading but that still runs fine. It sits there, plugged in most of the day. And the normal move is still to rent someone else's computer to run your software, and hand your work over to be hosted and owned on their terms. You take on a dependency you never needed, pointed straight out of your own house.
The real cost is not the monthly bill. It is the lock-in. You wire your GitHub to a platform because the deploy is convenient, and now you live inside their system. Then one day your site gets popular, the bill arrives, hundreds of dollars, sometimes thousands, and you feel it. I have watched it happen to people whose only crime was making something people wanted to see. If you own your stack, that does not happen. It also means it is on you to keep it running, which is the fair half of the trade.
The moat is gone
Here is what changed. The cost of making software is now a few prompts away, and roughly the same for everyone who shows up. When that is true, the value of software that is closed and locked inside a sandbox starts to disappear. Why use a locked-down tool when the open, editable one does the same job and bends to fit you?
Everyone has felt this with the tools they are handed at work. The Jira, the wiki, the Confluence. They mostly work, and you mostly cannot stand how they are set up. You want the one view that matches how your team actually plans, and you cannot have it. You can beg the vendor to build it, or you can homegrow something on the side. With Loft, that view is one prompt away, and it just works.
I don't think people want to maintain software. I think they want to customize it.
Maintain versus customize
The honest objection is that people do not want to maintain software. That is true. Nobody wakes up wanting to babysit dependencies and chase bugs. But maintaining and customizing are not the same thing, and people have always wanted to customize. There are custom Spotify clients. There are Minecraft mods. There is a whole economy around GTA mods. That is what software has always been: making something fit you a little better.
So Loft gives you the customizing and takes the maintaining off your plate. Your changes are real, and yours. When a new version ships, it merges onto your copy cleanly, so the debugging and the plumbing stay out of your day. You keep the part people actually want, and lose the part nobody signed up for.
It should feel calm
None of this matters if it is hard to use, so how it feels is the thing we care about most. There is a real app, which means you never have to touch a terminal. It connects to the AI you already pay for, and it is agent-native down to one simple rule: anything you can do in the app, your agents can do for you. The least technical person in your family can type a few questions and let the work carry on while they clean the house or sit with the kids.
The feeling we want the first time you run it is the opposite of overwhelm. You brace for a setup, and instead it is just already working. Serve it privately to your own phone in a couple of clicks, or open it to the whole world on your own domain. Quietly. No drama.
Stay above the loop
Software is not at the point where you can take the human out entirely, and it should not be. Someone still has to look and say yes, this is right. But you do not have to sit inside every loop, driving each agent by hand. You sit above it. Your agents run, they report up, you give direction, and you stay the one who approves what ships.
It is the old company org chart, the reviewers and the leads and the planners, folded down onto one person. Every agent runs under the human who deployed it. Their decision, their record, their responsibility. And because you review in batches instead of one ticket at a time, a week of parallel work can land in a pass or two.
A place that is yours
It is called Loft because a loft is a place you own and want to be in. Warm, a little apart from the noise, comfortable. The modules are its rooms. That is the whole feeling. And it is for anyone with an idea that touches software: a budget tracker you wish worked your way, a dashboard for a project only you care about, a small business you want to run without a platform sitting between you and it. Software used to need a company. Now one person, or a very small group, can build and run the real thing.
If you make a mess, that is fine too. I do. I start a strange idea at 4am, wander off, and leave it half-built. Nothing is lost. The context stays in the Loft, so whenever you come back, you pick up exactly where you left off. There is no worst user, because walking away and returning is just how it is meant to work.
We might build something people love and never make a cent from, because the free core is enough on its own. That is a risk we are glad to take. The point was never to become your landlord. The point is that you never need one again.
■