Home Ownership

You own it.
All of it.

Most agencies and SaaS vendors quietly keep the keys — the code lives on their servers, the credentials are in their accounts, and leaving means starting over. We build the opposite way: at handover, the whole thing is yours, and walking away costs you nothing but our phone number.

At handover

What you receive and own.

01

The source code

Every line, hand-written and readable — no obfuscation, no proprietary black boxes you can't open. It's yours to host, edit, extend, or hand to another team. Because we write it by hand rather than assembling it from page builders, there's nothing locked behind a vendor's export button.

You get — all source, in full
Restrictions — none
02

The documentation

How it's built, how it runs, and how to change it — written so your next developer can pick it up without calling us first. A handover includes a walkthrough, so the docs are a reference, not your only lifeline.

You get — docs + a live walkthrough
Goal — you're never hostage to us
03

The credentials & access

The accounts, keys and infrastructure access that run your system are handed to you, in your name. No shared logins we quietly retain, no accounts that revert to us if the relationship ends. When we're done, we hold nothing you'd need to ask for back.

You get — credentials + infra access, in your name
We keep — nothing you'd have to reclaim

Why it matters

Lock-in is a choice.
We don't make it.

Owning your stack isn't a bonus clause — it's the point of building it by hand in the first place.

Host it anywhere

Your infrastructure, your cloud account, your rules. Nothing is tied to servers we control, so you can move it whenever you like.

Replace us freely

Because you hold the code, docs and credentials, another developer can take over cold. We earn repeat work by being useful, not by being the only option.

No black-box rental

Unlike a SaaS you rent forever, a system you own keeps working — and keeps being editable — long after the invoice is paid.

Data & access

Careful with your data.

01

Least access, by default

We ask only for the access a piece of work actually needs, and no more. Credentials we use during a build are handed to you and rotated out of our hands at the end — we don't accumulate standing access to systems after a project ships.

Principle — least access
After handover — we hold nothing standing
02

Host it on your own infrastructure

Where it matters, your system and its data can live entirely on infrastructure you control — including self-hosted AI and RAG, so sensitive content never has to leave your environment. We build our own products this way, so it's a well-worn path, not an experiment.

Option — fully self-hosted, incl. AI/RAG
Data — stays in your environment
03

Honest about what we are

We're an independent studio, and we won't wave certification logos we haven't earned — no invented SOC 2 or ISO badges here. What we offer is truthful, practical care: careful handling of your data and credentials, least-access habits, and formal privacy and terms you can read in full.

Certifications claimed — none we don't hold
Read the fine print — /legal

Ownership you can
read in the contract.