Customer on-site
The system runs inside the customer environment. The customer controls physical infrastructure, network access, credentials, backups, and operating decisions.
Security and ownership
Know where documents run, who can access them, and who owns each control.
Every assessment records the deployment boundary before documents move. On-site deployment and dedicated private hosting have different ownership, support, backup, exit, and erasure requirements.
Two deployment boundaries
Use the boundary that matches the documents and the operating owner.
Dedicated private hosting
The system runs in a single-customer environment operated by InHouse Compute. The scope records data movement, administration, backups, support, exit, and erasure. This is private hosting, not customer on-premises infrastructure.
Control record
Six items are settled before pilot use.
Approved sources
The scope names the document collection, owners, revisions, exclusions, and prohibited data before indexing.
Named access
Pilot users and administrators are approved. Access removal and restricted-document behavior are tested.
No public exposure by default
The private interface uses the agreed network path. Public internet exposure requires a separate review and approval.
Controlled support access
Remote support access is named, time-limited, and removed after handoff unless the support agreement says otherwise.
Backup and source removal
The owner, schedule, restore test, document-withdrawal process, and retention boundary are recorded.
Operating handoff
Credentials, updates, limitations, incidents, support, and exit responsibilities have named owners.
Compliance claims require separate review.
InHouse Compute is not a compliance certification provider. A deployment may support customer privacy and control goals, but HIPAA, CMMC, SOC 2, and similar claims depend on the full environment, policies, controls, contracts, and qualified review.
Have a security team that wants specifics?
Bring them to the free fit review. We'll walk through access, backups, boundaries, and what the pilot will and will not prove.