Owning your website's source code: why this clause matters more than the price

Clients call us with the same story often enough that we can recite it. The website ran fine for two years. Now they need another page, or a new phone number, or to move hosting. The shop that built it has stopped replying, or quotes a third of a rebuild for a small change.

And they can do nothing, because they do not have the source code.

Three things sellers all call "ownership"

Level 1 — you have an admin login. You can sign in and edit content. You do not have code. If the builder disappears, you lose the website. This is the norm below 10 million VND and is almost never stated plainly.

Level 2 — you have code files that do not run. You receive a zip. Inside is minified code, or a missing config file, or no setup instructions, or an environment variable only the builder knows. Formally it was handed over; practically nobody else can stand it back up.

Level 3 — you have everything needed to rebuild from scratch. Readable source, the database schema, setup documentation, the list of environment variables, and domain plus hosting registered in your name. A developer you hire tomorrow can run the site on their machine in an afternoon.

Only level 3 is ownership. The first two are renting under another word.

Four things that must be in your name

This is not only about code. Check four things, and check them before the final payment:

The domain. Look at whois or the registrar's panel and see who the registrant is. If it is the agency, you do not own your own address. This is the most painful one to lose, because every backlink, every ranking and every printed business card points at it.

Hosting or the VPS. The account must be yours, paid with your card. Giving the builder access is fine; letting them be the account holder is not.

The source repository. GitHub, GitLab, or simply a zip you keep. What matters is having a copy that does not depend on the builder still existing.

The database. A backup, in a readable format, that you download and keep — with restore instructions.

The best test question

When a seller says "full source code handover", ask exactly this:

"If I hand the delivery package to a different developer with no introduction, can they run the website on their machine, and how long would it take?"

A good answer is a number of hours. An evasive answer tells you that you are at level 1 or 2.

One more question is cheaper and works even better: "how many pages is the setup documentation, and can you send it to me now?" A shop with real documentation sends it within ten minutes.

Why we are loud about this

Because it is why SourceViet exists in its current form. Every template we sell ships the complete Next.js source — readable, not minified, no licence server, with setup and deployment documentation. Host it anywhere, including with a provider we have never heard of.

On custom work, the contract says the source code is yours, and the domain and hosting are in your name from day one — we hold access, not ownership.

This is not generosity. It is the business model: we would rather clients come back because the work was good than because they are stuck.

If you are at level 1 or 2

There are still moves, in the order worth trying:

1. Request handover in writing, citing the contract clause if one exists. Many cases end here.
2. If the domain is in their name, register a new domain in yours today. Do not wait for the negotiation to finish.
3. Recover your content yourself. The text and images are yours and can be downloaded. This is the slowest part to recreate.
4. Rebuild on a base you control. For an ordinary business website, rebuilding from a good template takes days and costs less than continuing to pay into an arrangement where you hold no rights.

One thing to do right now, even if your website is running perfectly: look up your domain's whois and see whose name is on it. It takes thirty seconds, and most people reading this will learn something they did not know.