Most owners assume that paying for a website means owning it, the same way buying a car means owning the car. Software does not work that way. Ownership of a website is really three separate things: the domain, the source code, and the ability to leave. Lose control of any one of them and you can be locked out of your own asset during the exact dispute where you need it most. This is the part of the buying process that never shows up in a portfolio, so it is worth understanding before you sign. For the broader hiring picture, see our guide to choosing a web design company, and for the full build context, the small business web design guide.

In 30 seconds
Default
the contractor keeps copyright to custom code without an IP clause1
$0 export
Wix and Squarespace offer no portable code export5
Rebuild
leaving a closed builder means rebuilding from scratch, not migrating5

The source-code myth

Here is the part that surprises people. Under US copyright law, when an independent contractor writes custom code, that contractor holds the copyright by default. Settling the invoice does not make the work a "work made for hire." Without explicit language transferring the rights, you have bought an implied license to use the software, and the developer legally retains the right to reuse or resell that same custom codebase, restrict how you modify it, or charge you to keep using it.1

The fix is one clause. The contract must contain an express intellectual property assignment stating that on final payment, all right, title, and interest in the custom work, including source code, design assets, and databases, transfers to you. It should also require the developer to disclose any pre-existing or open-source components so no restrictive license quietly forces its terms onto your business.2

* Key point: No IP assignment clause means you rented the code. The single most important sentence in a web contract is the one that hands you the copyright.

The domain is the real anchor

Your domain is the most valuable digital asset you own. It anchors your search rankings, your brand, and your email. Yet owners routinely let a web designer register it "to save time," which quietly makes the developer the legal registrant. If the relationship sours or a final invoice is disputed, whoever controls the domain can freeze your website and your entire email system at once, and untangling it through a formal dispute is slow and expensive.3

The rule is simple: you register your primary domain yourself, in your own account, at a reputable registrar. The developer gets temporary technical access to point it at the hosting, nothing more. That one habit removes the most common hostage scenario entirely.


Vendor lock-in, the quiet trap

Lock-in is when leaving your provider means devastating switching costs or a full rebuild. It comes in two flavors. The obvious one is a closed platform like Wix or Squarespace: your site lives on their servers in proprietary code, and neither lets you export the design or page structure in a portable format. Outgrow the platform or object to a price increase, and the thousands of hours in that site evaporate the day you cancel.5

The sneakier flavor hides inside supposedly open systems. A WordPress site sounds portable, but if the agency built it with a proprietary page builder or a closed premium theme, the content is stored as proprietary shortcodes, not clean HTML. Deactivate the plugin and the whole front end shatters into unreadable blocks. The lesson: "we use WordPress" is not the same as "you can leave."4 This is closely tied to the migration risk we cover in why website migrations lose traffic.

How to guarantee zero lock-in

To own your site outright, insist on three technical conditions. First, it is built on genuinely open frameworks that compile to standard HTML, CSS, and JavaScript. Second, the entire codebase lives in a Git repository you own. Third, it can be hosted on any commodity provider. Meet those and the site can be moved and maintained by any competent developer on the planet, which is exactly the leverage you want.4 If you want the money side of this decision, our comparison of a website builder versus a custom build runs the five-year numbers.


Frequently asked questions about website ownership

Do I own my website if I paid a developer to build it?

Not automatically. The developer holds the copyright to custom code by default. You need a written intellectual property assignment in the contract that transfers the source code, design files, and databases to you on final payment.

Can I move my Wix or Squarespace site elsewhere?

No. Those platforms do not offer a portable code export, so moving means rebuilding from scratch. That is the tradeoff for the convenience, and it is worth knowing before you invest years of content into one.

What is the single most important ownership clause?

The intellectual property assignment. Without it you have a license, not ownership. Pair it with registering your own domain and an open, exportable codebase, and you control the asset completely.

Own every piece of your website

Everything we build for Shelby and Cleveland County businesses ships with the code in your hands, your domain in your account, and nothing locking you to us. That is the whole point.

Sources: 1. Stratagem Systems, Software Development Contract 2026 2. AI Lawyer, Software Development Agreement Template 2026 3. Domain Name Wire, Designers Holding Domains Hostage 4. Vaza.ai, Website With No Vendor Lock-In 5. Vizantir, Website Builders vs Custom Development