What you own when FCT builds it

Most software work leaves you holding something you cannot move. The code sits in an agency's repository. The domain is registered to them. The hosting is under their account, the analytics under their login, and the only person who knows how any of it fits together is the person you just stopped paying.

We do it the other way, and we would rather you read the terms now than ask for them later.

Your code

You get the source at each paid milestone, not at the end of the project. It lands in your repository, with us as a collaborator on it rather than the owner. That includes the architecture notes and the runbook, written so another developer can pick the work up without calling us first.

There is no proprietary layer you have to keep licensing. If a piece of what we build only runs because of something of ours, we tell you before we build it, and you decide.

Your accounts

Anything with a bill attached is in your name and paid by you directly. AI model providers especially: we are never between you and that invoice, which also means we are never marking it up.

For the accounts that exist purely to run something, the rule is ownership versus custody. A website is the clearest case, so here it is in full.

Your domain

We register it through Cloudflare Registrar with you as the registrant. Your name, your email, your ownership, on day one. Not transferred to you later, and not held in escrow against the invoice.

We keep it in our Cloudflare account and we host the site there too. Making a business owner create and manage a Cloudflare account in order to have a website is a chore nobody wants. Registrant is ownership. The account is custody. Those are two different things, and only one of them is ours.

The domain and hosting are $36 a year, renewed by us. A .com costs us about $11, so the rest covers the hosting and the renewing.

Your data

For Second Brain OS, the workspace is plain files on your own machine. Identity, context, memory, skills, automations. You can open any of them in a text editor, move the folder to a new computer, or read it yourself in ten years.

For anything we build that stores your business's data, the database is yours and an export is a normal feature rather than a favor.

When you leave

On request we transfer the domain out to your own registrar and hand you the code. No fee, no notice period, no last invoice attached to the handover.

If we host your site and you want it elsewhere, that is a transfer and a deploy, and we will tell your new developer how it is wired.

Nothing we build requires us to keep running it. That is a design constraint we hold while building, not a promise we make at the end.

What we keep

Our own internal tools, our engineering, and the way we work. The runtime we run our own company on is ours, and when we engineer one for you, that one is yours.

We also keep learning from the work, which is the honest reason we can move quickly. What we never keep is your content, your customers, or a login you need in order to run your own business.

Put it in the contract

Every line above belongs in the agreement, not just on this page. When we scope the work, ask for it in writing, and read it. If any company you are considering will not put ownership terms in a contract, that answer is itself the answer.