Own the Box: What It Means to Own Your Infrastructure

To own your infrastructure means the accounts, keys, code, data and documentation that run your business are in your name and under your control, even when someone else does the daily work. A good provider builds, secures and runs it. You hold the keys. If a provider cannot say that plainly, keep looking.

What it means to own your infrastructure

Who plugs in the server matters less than what happens on the day you want to change providers. Check five things:

• Accounts. The domain, hosting, email, AI and software accounts are registered to your company, not to the provider.
• Keys and passwords. You can get the administrator credentials, and they are stored somewhere you control.
• Data. Your customers, files and content can be exported in formats other tools can read.
• Code. Custom work you paid for belongs to you, in writing.
• Documentation. How the setup works is written down well enough that another team could run it.

Your domain: the first test of whether you own your infrastructure

The domain is where most owners get caught, because it looks paid for and therefore owned. ICANN, the body that coordinates domain names, explains in its registrant FAQ that the rights to a domain belong to the registrant, the "Registered Name Holder." If a developer registered the name with their own contact details, they may be listed as the registrant of record "even if you have paid them to register and manage the domain name." ICANN also notes you do not buy a domain outright; you hold the right to register and renew it.

Custom code: the catch when you own your infrastructure

Paying for custom software does not automatically make it yours. The U.S. Copyright Office's guide to works made for hire explains that a commissioned work is made for hire only if it falls within one of nine eligible categories and both sides sign a written agreement saying so. Otherwise, the Office notes, the author is ordinarily the person who actually created the work. Under section 204 of the Copyright Act, a transfer of copyright ownership is not valid unless it is in writing and signed by the owner of the rights. If you want the code to be yours, put a written assignment or license for custom work in the contract.

Registrant

The person or company listed as holding the rights to a domain name. Whoever is named here, not whoever paid, controls renewals and transfers.

Work made for hire

Work made by an employee as part of their job, or certain commissioned work under a signed written agreement. The party that hired the creator is both the author and the copyright owner.

Assignment

A signed, written transfer of copyright from the creator to you. Without one, or a work made for hire agreement, a contractor generally keeps the copyright in what they wrote.

Administrator credentials

The logins that can add users, change settings and delete data in an account. Whoever holds them can lock everyone else out.

Why it matters

If you do not own your infrastructure, your options shrink. A price rise, a slow response or a sale of the provider's company becomes your problem, because leaving means rebuilding. The same choices that cause vendor lock-in also decide who really owns your systems.

Ownership also matters for security. Someone has to know who can log in, where backups live and which keys unlock what. The joint advisory on threats to managed service providers from CISA, the NSA, the FBI and partner agencies tells customers to "understand the access their MSP has to their network and the data it houses," and to make sure the contract "specifies whether the MSP or the customer owns specific responsibilities." If only the provider knows, you cannot check their work.

Own your infrastructure without running it yourself

Owning and operating are different jobs. You can own your infrastructure and still hand off the patching, monitoring and late-night fixes. The split that works has three parts:

Put that split in writing before work starts. It costs nothing on day one, and it is very hard to negotiate on the day you want to leave.

How LTFI works

Kief Studio runs LTFI on a server for your company alone, managed, patched and watched by us. Your AI runs on your own AI keys, under your contract with the AI company, billed to you at cost. Your contacts, files and content are yours, and if you leave, we export them for you. See what LTFI does and how a managed setup compares in managed versus self-hosted AI agents.

Frequently asked questions