Who owns your website on a retainer is three questions: site, host, and login. U.S. copyright vests in the author unless assigned. Keep the registrar. Let an operator hold the night-shift login.
Who owns the site, the host, and the login are three different questions, even when one invoice paid for the launch. The site is the words, the images, and the custom code. The host is the box, the DNS, and the backups. The login is who can ship a change at 11pm.
A project hire often leaves you with files and no operator. A retained team holds the operational login, and you still own the name, the content, and the data. Ask all three before you compare monthly numbers. Mix them up and you discover the gap the night the freelancer stops answering email.
I run Kief Studio with Brian, from Shrewsbury, Massachusetts. We are two people, and we have been building together since 2012. Our public model is what LTFI is: hire the department, do not install a box. The billing-shape essay is retainer versus project. If you and I were on a Zoom with the contract open, this is the ownership list I would walk before anyone talks price.
Site means the words, images, and custom code written for you. Under 17 U.S.C. § 201, copyright vests in the author unless it is a work made for hire or you have a written transfer. Independent contractors are usually authors until they assign. Put the assignment in the agreement. Do not assume a paid invoice transferred copyright. A check bought a deliverable. The statute decides who owns the files.
Host means the machine, the DNS, the certificates, the backups. You can own the domain and still rent the box. You can own the box and still not be the person who patches it. Write down whose name is on the registrar and whose name is on the VPS invoice. DNS is the phone book that points your name at an IP. Certificates are the lock on HTTPS. Backups are the copy you can restore. If those four sit in four dashboards with four emails, you have four owners and no owner.
Login means who can deploy, who has sudo, who holds the identity provider. On a project, that is often you plus a freelancer's leftover key. On a retainer, a studio holds the operational login so the night shift is not you. You still hold the business identity: brand, content, customer data. Operational login is the key that ships CSS at 11pm. Business identity is the key that proves the company is yours if you leave.
People collapse those three into one sentence at the kickoff: we paid for the website, so we own it. Then a Saturday restore fails because the only person with the host dashboard is on a plane, and the registrar is still on a personal Gmail from 2019. That is not a hosting outage. That is an ownership list nobody wrote down. Looking good at launch is not the same as being able to restore the box on a Saturday.
Employees' work inside the scope of a job is often work made for hire under U.S. law. A freelancer's theme usually is not, unless the agreement says so in the way the statute requires. I am not your lawyer. I am telling you the failure mode I see: paid launch, no assignment, later you cannot move hosts because the designer still owns the files. Fix it in writing before the launch party.
Massachusetts operators follow the same federal copyright rules as everyone else. Local counsel if the dollars are large. The Copyright Office page for Chapter 2 is the public text. Read the assignment clause out loud with the designer in the room. If neither of you can say who owns the theme after that reading, you do not own the theme yet.
Custom photography, custom illustration, and custom copy sit on the same rule. Stock licenses are different paper. Open-source libraries are different paper again. A LICENSE file in a repo can say you do not own the framework even when you paid for the theme built on it. Ask for a list: what is assigned, what is licensed, what is third-party. Put that list in the same folder as the registrar login. If you later want to change studios, that folder is the difference between a two-week move and a rebuild. Rebuilding because nobody assigned the files is an expensive way to learn § 201.
A six-week build can ship a beautiful site and leave you with a host login you are afraid to touch. The next freelancer inherits tribal knowledge. That is fragmentation wearing a project invoice. Tribal knowledge is the undocumented step that only lived in one person's head. When they leave, the restore runbook leaves with them.
A retained operator answers: we ship, we patch, we restore. You do not log into the server for Tuesday's CSS. You review the page. You own the words. ltfi.ai is that hire. You do not own the LTFI software. You own name, content, data, and custom code unless a LICENSE file says otherwise. Ground truth on this site is the same sentence: hire the department, do not install a box.
The two-person version of that department is how we run the studio model. Output of a larger team, two humans on the calendar. When a system goes down at 2am, there is no escalation chain. The person who built the system is the person who fixes it. The person who wrote the proposal is the person who ships the restore. Coordination cost is why I would rather one operator than four leftover keys. One vendor versus four is the math. Four logins look cheaper until Tuesday night, when each vendor thinks the other one has the certificate expiry mail.
The registrar is the company that records who owns the domain. That account should use your company email, your company card, and multi-factor authentication you control. A retained operator can hold DNS, certificates, and deploy keys. They should not be the only name on the registrar. If the relationship ends, you still have the name. Everything else can be rebuilt. The name cannot.
Ask for a data export drill before you sign. Can you leave with a dump in a week: content, images, customer records, DNS zone, certificate contacts. Owning the stack for client data is the jurisdiction version of that question. The contract should answer site, host, and login in writing. No price list here. Commercial terms live on ltfi.ai.
Turn on registrar lock if your registrar offers it. Registrar lock is a switch that blocks a transfer until you unlock it. Keep the unlock codes in the same place as the assignment PDF. People change jobs. Cards expire. MFA phones get replaced. Walk the list once a quarter so the paper still matches the dashboards. When someone leaves, revoke their deploy key the same day. Shared webmaster mailboxes are how leftover logins survive. One identity provider, named people, a revoke date on the list. That is the login column. The registrar column stays yours.
Write eight lines in complete answers, not slogans. Whose email, card, and MFA device sit on the registrar? Whose dashboard holds DNS and certificates, and who gets expiry mail? Whose name and card sit on the host invoice, and which region does the box sit in? Whose people hold CMS and deploy keys, and how are those keys revoked when someone leaves?
Is there a written assignment on file for custom code, design, and copy? Are stock, fonts, and open-source NOTICE files listed? Can you leave with a dump in a week, tested, not promised? What is the last successful restore date, and who ran it? If four of the first six are the last freelancer, you do not have a website. You have a bet. A bet is fine if you staff it. Most operators I meet did not staff it. They paid for a launch and assumed ownership followed the invoice. The statute and the registrar dashboard both disagree.
A retainer that cannot show you the registrar in your name, an assignment on file, and a restore date is a retainer that holds more of you than you think. Ask. Write the answers on one page. Put the page next to the contract. Practice a restore on a quiet afternoon, the way you would practice a fire drill. A restore you have never run is a story. A restore with a date on the list is an operator. If you are afraid to log in, you do not own the login. You rent hope.
I have sat with owners who could show me a beautiful homepage and could not name the registrar. The last freelancer used a personal Gmail. The card on file was expired. The restore they believed in was a screenshot of a folder on someone else's laptop. None of that felt like a crisis until a Saturday. Then it was the only conversation in the room. If we were filling the page together, I would start with the registrar, then the assignment, then the restore date. Price comes after those three. A cheaper monthly number that hides four leftover keys is not cheaper. It is a second job you did not staff, waiting for a night you did not choose.
At Kief Studio the public rule is simple. You keep the registrar. You keep the words. You keep the customer data. We hold the operational login so patch night is not your second job. Clients stop asking for a status chain because they already know who is on the call. kief.dev is the engineering public square. Architecture notes live on briansgagne.com. I write the ownership list. He designs the box the list describes. That is accountability, not headcount. Managed website and writing without a ten-person team is the same hire written from the calendar side.
You own what the contract assigns. U.S. copyright starts with the author under 17 U.S.C. § 201. Pay the invoice and still get a written assignment for custom code, design, and copy.
Only if you will patch and restore. A retainer that holds the operational login and still lets you export data is a department. A login you fear to use is a liability you staffed with hope.
No. Keep the registrar in your name, on your email and your card. That is the one login that should stay yours even when someone else operates the box.
Owning the host means your name is on the invoice and the machine. Owning the login means you can deploy and restore. You can have one without the other, which is why both belong on the list.
No. LTFI is a hire, not an install. You own your name, content, customer data, and assigned custom code. You do not own the LTFI software.
Website copyright for these files is federal. Massachusetts operators follow 17 U.S.C. § 201 like everyone else. Use local counsel when the dollars or the design inventory are large.
Managed website and writing without a ten-person team: one retained department for site, host, and night-shift login. Brooks: more people, more paths. You keep the registrar and the data. SparkToro 2024: 58.5 percent of US Google searches had no click.
What LTFI is: hire a department, not a box you install. Site, host, identity, and on-call on infrastructure Kief Studio operates. You own name, content, data, and custom code.
IT platform consolidation cost savings vs vendor claims should be scored against waste you already have. Flexera 2025: 27 percent of IaaS and PaaS spend unused. Changing the logo is not savings.
Work With Us
Kief Studio builds, protects, automates, and supports full-stack systems for businesses up to $50M ARR.
Newsletter
Strategy, psychology, AI adoption, and the patterns that actually compound. No spam, easy to leave.
Subscribe
