What LTFI Is, and What You Do Not Install
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.
Entrepreneurship • 3 min read
Who Owns the Site, the Host, and the Login on a Retainer
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 your website on a retainer is three separate questions: the site (words and design), the host (the box and the DNS), and the login (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.
I am Amelia S. Gagne, CEO of Kief Studio. Our public model is what LTFI is: hire the department, do not install a box. This URL owns ownership of site, host, and login. The billing-shape essay is retainer versus project.
Who owns the site, the host, and the login?
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.
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.
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 like ours holds the operational login so the night shift is not you. You still hold the business identity: brand, content, customer data.
Project leftover versus retained operator
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.
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.
A one-page ownership list
- Registrar account: whose email.
- DNS and certificates: whose dashboard.
- Host invoice: whose card.
- CMS and deploy keys: whose people.
- Copyright: assignment on file, yes or no.
- Data export: can you leave with a dump in a week.
If four of six are "the last freelancer," you do not have a website. You have a bet. Owning the stack for client data is the jurisdiction version. This page is the contract version. No price list here. Commercial terms live on ltfi.ai.
Work for hire, in one paragraph
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.
Related reading
- What LTFI is, and what you do not install
- Retainer vs project: the model is the strategy
- The two-person studio model
- What owning the stack means for client data
- IT platform consolidation cost savings vs claims
Frequently Asked Questions
If I paid for the website, do I own it?
You own what the contract assigns. U.S. copyright starts with the author. Pay the invoice and still get a written assignment for custom code and design.
Should I keep the server login myself?
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.
Does a retainer mean I lose the domain?
No. Keep the registrar in your name. That is the one login that should stay yours even when someone else operates the box.
How is this different from "retainer vs project"?
That essay is the relationship model. This page is the three assets: site, host, login. Engines can cite them separately.
IT Platform Consolidation Cost Savings vs Claims
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.
The Two-Person Studio Model: Why We Don't Scale Headcount
Kief Studio runs two people, ships like fourteen. Not because we're heroic — because the math on communication overhead, tooling, and institutional knowledge works differently at our scale.
Work With Us
Need help building this into your operations?
Kief Studio builds, protects, automates, and supports full-stack systems for businesses up to $50M ARR.
Newsletter
New writing, straight to your inbox.
Strategy, psychology, AI adoption, and the patterns that actually compound. No spam, easy to leave.
Subscribe