What should you ask before hiring someone to set up a private AI?
Short answer: Ask ten things: who owns the account, where it runs, which model, what is logged, who patches, can you leave, what costs extra. Use it on any provider.
Apply for a place From $10,000 setup, then $48,000 a year. Five places a week.
Who owns the cloud account, the admin login and the keys?
You should own all three: the cloud account the AI runs in, the admin login (the top-level sign-in that can change anything), and the keys (the secret codes that unlock your data). If the provider owns them, you rent the setup and cannot leave.
A good answer: "The account is in your name, you hold the admin login, and we get limited access that you can remove." A red flag: "We host it all under our account, you just log in." Ask the same question about what happens if the provider disappears. A good provider has written documentation and gives you your own admin access from day one, so a stranger could take over.
- Good: account in your name, your admin login, documented handover.
- Red flag: the provider's account, the provider's keys, no written docs.
Where does it run, and which model does it use?
Ask for the exact place it runs (your cloud account, your own hardware, or the provider's) and a list of every person or company that can reach that hardware. A good answer names the location and says who has access and why. A red flag is "it's in the cloud, don't worry about it."
Then ask which model it uses and under what license. A license is the rule set for how you may use the model, including for business. A good provider names the model, shows you the license text and points you to the vendor's current terms. A red flag is a vague "our own proprietary model" with nothing to read. Our guide to model licenses explains what to look for.
What is logged, where, and who can read the logs? Do they train on your data?
Ask for a plain list of what is logged (chats, files, sign-ins), where the logs are stored, how long they are kept and who can read them. A good answer is specific: "Sign-in events are logged here, chats are stored here, only these two people can read them." A red flag is "we don't really log anything" or the opposite, "we keep everything forever."
Ask directly: do you train on my data, and do you keep a copy? A good answer is a clear no to training, plus a statement of who holds the files. A red flag is hedging, or an answer that points you to terms you have not been shown.
Who does updates, patching and backups, and is a restore ever tested?
Someone must own updates, patching (installing security fixes) and backups, and you should know who it is by name or role. A good answer says what is done, how often, and who is paid to do it. A red flag is "it just keeps itself updated."
The key follow-up is whether a restore (bringing the backup back into a working system) has ever been tested. A backup nobody has restored is a hope, not a backup. Ask to see the steps. Our page on backing up private AI data shows what a sound plan covers.
Then ask the exit question: can you leave and keep the working setup? A good answer is yes, with your account, your files and the documentation handed over. A red flag is a contract that ties the setup to the provider's tools or fees.
What is in the price, what is billed extra, and what will they refuse to promise?
Ask for a written list of what the price includes and what is billed extra, such as hourly training and support, and cloud compute (the rented computing power). A good answer separates setup, ongoing fees and pass-through costs. A red flag is "it depends" with no numbers or rates in writing.
Freeborn answers these ourselves. The cloud account is in your name, we do not hold your files, traffic uses HTTPS, keys are stored encrypted, we do not train on your data, and you can walk away with the setup. Hands-on training and on-call support are extra, by the hour. Ask every provider the same questions, including us.
Finally, ask what they refuse to promise. Honest providers refuse to say a system is "perfectly safe" or "zero risk", or that a result is sure. Any provider who promises absolute safety, total privacy or a sure outcome is a red flag, because no system earns that.
How do you test the answers?
Do not accept spoken answers. Ask for each answer in writing, so you can compare providers side by side and hold them to it later.
Ask to see the admin console (the control screen) of a demo account, so you see what you would control. Ask for the restore steps and, if you can, watch one done. These three checks take little time and show quickly who has done the work before.
- Ask for every answer in writing.
- Ask to see the admin console of a demo account.
- Ask for the restore steps, and watch a restore if possible.
What are the limits?
A checklist cannot prove a provider is honest. It only makes vague or evasive answers easy to spot. Reference checks with past customers and a small paid first step lower the risk further, because you learn how the provider works before you commit.
This page is general information, not legal, medical, financial or tax advice. If your data is covered by rules you must follow, ask your own counsel or compliance officer. If you would rather have a person do the work, see our private AI setup service. If you would rather build it yourself, start with our DIY guides and an honest list of the work. More answers sit in the Freeborn Labs FAQ.
Questions
How long does a private AI setup take?
It depends on scope: how many people, which files and which tools. Ask the provider for a written plan with steps and dates, and be wary of a fixed promise made before they have asked about your needs.Do I need an IT person to hire a setup provider?
Not necessarily, but someone on your side should be able to read the answers and hold the admin login. A good provider explains each step in plain words and trains that person.Can I check the setup myself after it is built?
Yes. Sign in to the cloud account to see who has access, what is running and what it costs. Ask the provider to walk you through it and to write down what you should look at.What documents should I get at handover?
Ask for a list of accounts and who owns each, how to sign in as admin, where the keys live, the backup and restore steps, the model name and license, and who to call when something breaks.Should I compare costs before choosing a provider?
Yes, using the same written questions for each. Our page on what a private AI setup costs shows what to expect, and the server choice guide covers where it runs.Related guides
- Done-for-you private AI setup service
- What it takes to do this yourself
- How Do You Check a Local AI Model's License Before Using It?
- How Do You Back Up a Private AI System?
- How much does a private AI setup cost?
- Private AI answers
- Private uncensored AI: the full guide
- All guides to getting your own private AI agent
Apply for a place
Takes thirty seconds. No payment now.
Adults only (18+). Private uncensored AI · Terms · Privacy · All guides