Why post-SaaS
Renting made sense when software was expensive. It isn’t anymore.
SaaS existed because building and changing software cost a team. Agents have made changing it cheap. What comes next is ownership: the source, your data and your accounts, with help keeping it running when you want it.
Why SaaS existed
Software as a service was never about the software. It was about who paid for the engineers.
Building a support desk or a status page took a team. Running it took another. Nobody sensible wanted to fund either for a tool that was a means to an end, so one company built the thing once and rented it to everyone. You gave up your data, your price and your say over the roadmap. In exchange you never had to think about it.
That trade rested on one assumption: that changing software stays expensive. Coding agents now change working software from a plain description. When changing the thing is cheap, the rent stops being a bargain and starts being a toll.
Ownership used to mean maintenance
What SaaS really sold you out of was the burden. Running software yourself meant a repository, a server and your weekends. Build it all yourself and every update after that is yours to build.
Open source offers editable starting points, often well maintained, and capable agents can adapt them. Run Edit Run has to earn its place by saving the whole effort of reaching the product you want and keeping it there.
Your agent can change any part of the source. Written requirements and tests help it keep what matters to you when an improvement arrives.
What ownership means here
Written baseline requirements guide our products. A product’s release evidence should show which of them apply and what has been verified. A few of them:
- Independence. The deployment makes no request to the marketplace or the product’s author. There is no telemetry, phone-home, licence check or kill switch.
- Export and import. The required outcome is a complete export of records and attachments, and their restoration.
- Outbound flows. User data leaves the deployment only through the external services the product declares.
- Retention. Leaving Managed takes the running app offline at once. Its databases, files and key-value data are kept for 30 days, then deleted automatically. Download required exports first; see the leaving terms for source retention and export limits.
- Failure is visible. A job that fails after its retries is marked failed where an operator can see it. Nothing is dropped silently.
These are requirements, not a promise of a service or of production readiness: check a product’s release for what it actually does before you adopt it.
Why pay for MIT code
Because the code was never the expensive part. Keeping it running and improving is.
Running a product yourself is free under the MIT licence. Assisted and Managed plans charge for deploying, updating and looking after an installation, in your Cloudflare account or ours. For HappyToHelp, the first product, Assisted is in early access with hands-on onboarding and Managed is in early access.
Payment buys that work, never permission to keep using the code. Your licence does not depend on a subscription, and it stays yours if you leave.