What you own

Most software you can buy for your business is a subscription wearing a login page: useful while you pay, gone when you stop. A Botworks build works the other way. If the engagement ends — for any reason, on any terms — here is what stays with you:

The code repository

A private GitHub repository, transferred to your organization. Every line of this portal, its full history, and the documentation — yours. Any developer, or your own AI assistant, can work on it.

The database

Your data lives in a database project under your own account and billing. Customer lists, submissions, photos — exportable at any time with standard tools, because it's standard Postgres.

The deployment

The hosting project and the domain are yours. The app keeps running — and keeps auto-deploying from your repository — whether or not Botworks is in the picture.

The manual

The /documentation page you can read right now: a cold-start guide written so a new hire or an AI assistant can run and change the system without us.

The question to ask any vendor

“What do we keep when we cancel?”

Ask it of every platform that pitches you. With most, the honest answer is: nothing — not the workflows, not the customizations, sometimes not even a clean export of your own records. With this portal, the answer is the four boxes above. One owner-operator we worked with evaluated a venture-backed platform against this model and chose ownership; the deciding factor was exactly this question.

And ownership isn't just an exit clause — it's leverage you use every day. Smart owners already suspect their AI assistants will soon debug and extend software on their behalf. That only works on software you're allowed to touch. Open the documentation page and try it: paste it into your own AI and ask how this system works. That's the test no locked platform can pass.