Built for executives, ready for your security review.
SOC 2Compliant
Example: Your security team asks where the data lives and who can see it. This page and the requirements checklist answer most of that before the first call.
750+ connectorsAbout 24 hours to first lookSOC 2 Compliant
- Our cloudSnowfire hosts and runs it for you.
- Your private cloud (VPC)Snowfire runs inside your own cloud account.
- On-premSnowfire runs in your own data center.
Why security review comes first
Executives want faster answers and earlier Signals. Adoption stalls when security expectations are unclear, approvals take too long, or governance depends on manual workarounds. This page answers where the data lives, who can see it, what stays in your control, and what you can send before the call, so review moves forward instead of starting over.
Where Snowfire runs
- Our cloud. Hosted by Snowfire, including a dedicated environment Snowfire operates, logically separated from the shared service, for teams that need residency without building the stack themselves.
- Your private cloud (VPC). Snowfire runs in a dedicated cloud account you govern, in your AWS, Azure or GCP account, with network ingress and identity you control.
- On-prem. On-site and hybrid programs keep critical data and processing inside facilities you control. These are scoped as strategic engagements.
Every option keeps the same Signals, Metrics and Chat. Each comes with a requirements checklist covering identity, networking, storage, model access, connectors and operational responsibilities, so your team knows what to provision and what Snowfire operates. You can export all of your data at any time and switch models freely.
For private deployments, your team aligns with us on approved model endpoints, including customer-managed inference where your policy requires it. Connector and egress planning documents which integrations call external services, so security can approve data flows before go-live.
Who can see it
- Enterprise sign-in. Single sign-on through your identity provider, such as Okta or Microsoft Entra ID, with multi-factor authentication.
- Role-based access. Org admins manage users and roles, and can filter by role, status and last login.
- Access per connector. Choose which teams and roles can reach data from each connector.
- Scope of what syncs. Turn a table or a column on or off, and review the change before you save.
What stays in your control
- Connector health. Data Management shows each connector’s health, with a plain-language reason when a sync is unhealthy.
- Document lifecycle. Retirement dates, notices when a file is deleted or disabled, and disabled files hidden from chats.
- Governed schedules. Org admins can edit any scheduled prompt. Other owners edit only their own.
- Answer integrity. Figures are checked against the data shown, and a table appears only when a lookup returned rows.
What you can send ahead
- SOC 2 Compliant. Review our security posture and request documentation in the Snowfire Trust Center.
- Encryption. In transit (TLS 1.2 or later) and at rest.
How a review works, step by step
- Review the posture. Start with this page and the Connectors page.
- Pick the deployment option. Our cloud, your private cloud (VPC) or on-prem, matched to your residency requirements.
- Walk the requirements checklist. Identity, networking, storage, model access, connectors and operational responsibilities, with your security and platform teams.
- Plan connectors and data flows. Decide which systems connect first, what syncs and who can reach it.
- Approve and launch. Start with one live workflow and expand from there.
Questions security teams ask
- Can we keep data in our own cloud account? Yes. The customer private cloud option runs Snowfire in your AWS, Azure or GCP account, with network ingress and identity you control.
- Can we limit who sees each system’s data? Yes. Define which teams and roles can access data from each connector, and choose which tables and columns sync.
- Can we approve every external data flow? Yes. For private deployments, connector and egress planning documents which integrations call external services before go-live.
- Where are the detailed controls? Exact controls and subprocessors are documented during procurement. Bring your questionnaire to the first call.
What each stakeholder sees
- CISO and security team: SOC 2 compliance, encryption, sign-in and access controls, and the deployment options, with exact controls and subprocessors documented during procurement.
- CIO and IT: Connector health, sync scope, users and roles, and the requirements checklist for private deployment.
- Procurement: A clear path to evaluation, with exact controls and subprocessors documented during procurement.
- Executives: Faster answers that their security team has already reviewed.
Example: a CISO with a residency policy
Example · A residency policy A CISO’s policy requires company data to stay in the company’s own cloud account. The security team picks the customer private cloud option, walks the requirements checklist with Snowfire, approves its own model endpoint, and documents the connector data flows before go-live. Executives get the same Signals, Metrics and Chat as any other deployment.
Reviewing Snowfire for IT? Bring your questions, and your security team, to the demo.
Questions
Is Snowfire SOC 2 Compliant?
Yes.
Do you support single sign-on and multi-factor authentication?
Yes. Single sign-on works through your identity provider, such as Okta or Microsoft Entra ID, and multi-factor authentication is supported.
Can Snowfire run in our own cloud?
Yes. Snowfire runs in our cloud, your private cloud (VPC) in your AWS, Azure or GCP account, or on-prem.
Can we use our own model endpoint?
For private deployments, yes, including customer-managed inference where your policy requires it.
How do we report a vulnerability?
Use the Responsible Disclosure link in the site footer.
Where can we see service status?
Use the Status link in the site footer.