Your business runs on someone else's computer. Every customer record you have is sitting on it.
A private server is one you don't share. Your AI, your customer data, and the tools you use all day run on a machine set aside for your business — and we're the ones who build it and move you onto it.
ClientCue private servers are machines set up for one business: a private AI that answers questions about your own documents and records, hosting for the sites and apps you depend on, and self-hosted versions of tools you would otherwise rent per seat. We scope the machine to what you actually run, set it up, and move you over; what we stay responsible for afterwards is written into your scope.
Who asks us for a private server?
You hold data you'd rather not hand over
Customer lists, contracts, pricing, case detail. If a breach — or a vendor emailing to say the terms have changed — would be a genuine problem for you, a shared platform is a genuine problem for you.
You rent ten tools and own none of them
Another subscription, another seat, another price rise at renewal. Past a certain size it costs less to run your own, and the decision stops being a technical one.
You were told to “just use the cloud” and it didn't fit
Unusual software, a large archive, a machine that has to sit in your building, something that can't leave your network. Not every workload fits inside a platform's boxes.
What a private server can be
Three shapes, and most builds are a mix of them. Which one you need comes out of a conversation about what you're running and what's worrying you.
Private AI
Businesses that want AI working on their own documents without that material leaving their control.
- A model running on a machine set aside for your business
- Your documents, records, and history loaded in as its knowledge
- Access limited to the people you name
- Nothing sent to a public model, and nothing used to train one
A build fee to set it up and load your material, then monthly for the machine and its upkeep.
Dedicated hosting
Businesses whose site, app, or database has outgrown shared hosting — or never fitted it.
- A machine allocated to you rather than shared with strangers
- Backups on an agreed schedule, with restores tested rather than assumed
- Security updates and monitoring handled for you
- A person to call when it's down
Monthly, by the size of the machine and how much of it we look after.
Self-hosted tools
Businesses paying per seat, every month, for software they could run themselves.
- Your CRM, automations, file storage, or internal apps on your own machine
- Your data in a database you can export any day
- Migration from the tools you're leaving
- Upkeep, so “self-hosted” doesn't quietly mean “your problem now”
A build fee to migrate, then monthly for hosting and maintenance.
How a private server gets built
No two are the same, so nothing gets quoted before somebody has looked at what you actually run.
We look at what you run today
Which tools, how much data, who touches it, and what it costs you if it's down for an hour. A conversation, not a form.
We scope the machine
What it needs to be, what it costs, and exactly what we're responsible for — in writing, before anything is bought.
We build it and move you over
Migration with your old setup still live as a fallback. Monitoring, backups, and updates afterwards are agreed in your scope rather than assumed.
What's settled, and what gets scoped with you
Always included
- The build, the migration, and the handover done by our team rather than handed back to you
- What we stay responsible for afterwards, written into your scope
- Your data exportable by you, any day, in a format you can use elsewhere
Scoped with you
- Where the machine physically lives, and who can reach it
- Backup schedule, how long backups are kept, and how a restore is tested
- Which AI model runs on it, and what it is allowed to read
- Regulated data — medical, legal, financial — scoped against your obligations, never assumed
Same rule as the rest of this site: we print what we know. Everything in the second column is decided with you and written down before you commit to anything.
Questions people ask first
Where does the server actually live?
That's part of the scoping conversation: in your building, in a data centre, or with a cloud provider under your own account. Each costs differently and fails differently, and the right answer depends on what the machine is for.
Is a private AI as good as ChatGPT?
For open-ended writing, the big public models are ahead. For answering questions about your own documents, records, and history, a private instance with your material loaded is usually the more useful one — and it isn't sending your material anywhere.
What happens when it breaks?
Who responds and how quickly is written into your scope and agreed before you sign. We don't publish a response time we haven't committed to you in writing.
Do I have to move everything at once?
No. Most moves start with one system while the old one stays up, and the rest follows once the first has been boring for a while.
Tell us what you're running and what's worrying you.
Half an hour, no slide deck. Bring the software you pay for, the data you'd hate to lose, and whatever made you look this up. You'll leave knowing whether a private server is worth it for you — including if the answer is that it isn't.
Calendar not loading? Call 848-346-1482 or email info@clientcue.io.
Own the machine your business runs on.
Scoped to what you actually run, built by a team you can call.
Last updated