At your site
Customer on-site
The system runs inside your environment. Your organization controls the physical infrastructure, network access, credentials, backups, and operating decisions.
Choose where private AI runs
On-site or hosted?
Both are private deployment options. The main difference is where the system runs and who operates the physical infrastructure.
Reviewed September 30, 2026. This comparison is educational and is not a compliance determination.
Two deployment options
Start with the location that fits your team.
Define the approved data, network route, administrators, backups, support, and exit plan for either option.
Off-site, single customer
Dedicated private hosting
The system runs in a single-customer environment operated by InHouse Compute. Approved data leaves your site and is processed in that environment over an agreed network route.
At a glance
Compare who operates each part.
Responsibilities and technical details belong in the written deployment scope.
- Physical location
- On-site: customer-controlled location. Hosting: approved off-site facility.
- Data movement
- On-site: data can remain within the customer site. Hosting: approved data travels to the hosted environment.
- Infrastructure operations
- On-site: customer-owned unless separately supported. Hosting: responsibilities are set by the hosting agreement.
- Access and exit
- For both: name administrators and support access, and document backup, export, retention, and deletion terms.
Common questions
Know what the location means.
Does dedicated private hosting keep data at our site?
No. The system runs off-site, so approved data travels from your site to the hosted environment for processing over the agreed network route. The data path and operating terms should be documented before use.
Is either option automatically more secure or compliant?
No. Location alone does not settle access, identity, backups, incident response, contracts, or regulatory requirements. The right choice depends on your full environment and qualified review; no certification is implied.
Can we move from hosting to on-site later?
Potentially. Portability depends on the model and software licenses, data stores, integrations, hardware, and an agreed export and handoff plan. Settle those details before the pilot if a move may be needed.
Choose with your real workflow
Get a written deployment recommendation.
A fit review can compare your documents, users, site constraints, connectivity, hardware, support needs, and exit plan before a pilot is scoped.