For agencies and government contractors whose data has to stay inside a FedRAMP High boundary, we run a separate copy of InsightHire in AWS GovCloud (US). It has its own accounts, its own data and its own keys, and only US persons can administer it.
Updated November 11, 2026.
GovCloud is its own AWS partition, with separate accounts, sign-ins and networks from the commercial cloud. Your deployment shares nothing with our commercial service: no shared database, cache, file storage, logs, backups or encryption keys.
Putting only the database in GovCloud would not keep your data in the boundary, because the application, logs and backups would still sit outside it. So every part of InsightHire that touches your data runs inside GovCloud.
Production runs in one GovCloud region across multiple data centers. A live copy of every database is kept in the second GovCloud region, so we can recover from the loss of a whole region without leaving GovCloud.
Our infrastructure is defined in version-controlled code that is reviewed before it changes. Your GovCloud environment is built from those same templates, so it gets the same controls as our commercial production, plus the GovCloud-specific ones below.
What protects your data inside the GovCloud environment.
Anything that handles your data runs inside GovCloud, is replaced with a GovCloud-hosted option, or stays off. Before go-live you get the full list of services in your deployment, where each runs and what data it sees.
Your users sign in with your own identity provider over SAML or OIDC, with SCIM provisioning, so passwords and MFA policy stay under your control.
Interview summaries and scoring use a language model hosted inside GovCloud (Amazon Bedrock). We do not train AI models on customer or candidate data today.
Notification email is sent from inside GovCloud (Amazon SES).
Features that depend on an outside service, such as speech-to-text, live video, phone calls or background checks, are turned on only if that service is cleared for your deployment. Otherwise they stay off.
Security in GovCloud is shared. Here is who owns each part.
What GovCloud covers, and what it doesn’t.
We build a GovCloud deployment when a customer needs one. It is not running today, and we will tell you plainly where your deployment stands at each step.
AWS GovCloud (US) is FedRAMP High authorized, and that covers the infrastructure layer. InsightHire does not hold a FedRAMP or StateRAMP authorization of its own. If your agency needs one, tell us early so we can plan your review together.
Our SOC 2 program is in place, but we have not been audited yet. The same policies and controls apply to the GovCloud deployment.
If your work involves criminal justice information, we sign the CJIS Security Addendum. Everyone with access to that data gets fingerprint-based background checks and annual security training, and your state’s CJIS Systems Agency reviews the setup.
1
We meet with your security team to confirm which parts of InsightHire you will use, what data you will store, and which requirements apply, such as CJIS.
2
Under NDA, we share an architecture diagram, a data flow diagram, the list of services in your deployment, and our security policies and questionnaire answers.
3
We build your environment in GovCloud from our infrastructure code, turn on only the cleared features, and check every control on this page.
4
Your team tests sign-in, roles and your hiring workflow. If you already use InsightHire, we move your data in an encrypted, logged transfer.
5
After launch you get the same status page, incident notices and 30 days’ notice of any new service that will see your data.
Ready to start? Request a security review and mention GovCloud, or email support@insighthire.com.
Yes. It is the same application your team would use in our commercial service, running as a separate copy inside GovCloud.
No. The two environments share no databases, storage or keys. Data moves into GovCloud only when you ask us to move an existing account, as a one-time encrypted and logged transfer.
No. Candidates still use a private link with a long random token. The link is served from GovCloud and only opens that candidate’s own journey.
Only US persons on our team, only to help when you ask, and every support access is recorded in your organization’s audit log.
Most of them. A feature that relies on an outside service without a cleared option for your deployment stays off until there is one. We list these at the scoping call, before you commit.
We agree on a date at the scoping call. The environment is built from code, so most of the time goes to your security review and testing.