Skip to main content
Enterprise review should separate three kinds of evidence:
  1. Product behavior visible in the current Entelligence app
  2. Public statements published by Entelligence
  3. Contractual commitments in your security package, DPA, order form, or support agreement

​
Verified public and product evidence

SOC 2 Type II

The current public homepage states SOC 2 Type II. Request the current report, audit period, system scope, exceptions, and bridge letter.

Privacy policy

Review the published policy for personal-data processing, U.S. transfers, retention language, and privacy contact details.

Workspace controls

The audited app exposes Member/Admin roles, provider authentication, repository controls, API keys, billing, and Slack delivery.

Security package

Request the documents and deployment commitments that are not established by the UI or public website.
A badge or public statement is not a substitute for the underlying report. Confirm the audited boundary, period, complementary customer controls, exceptions, and whether your purchased deployment and products are in scope.

​
Evaluation workstreams

  1. Choose one measurable use case.
  2. Connect one source with minimum scope.
  3. Use an Admin and a normal Member test account.
  4. Verify a read-only result.
  5. Test one reversible write only when required.
  6. Record access, audit, rollback, and deletion evidence.
  7. Pilot with a small group.
  8. Review product value and operational burden.
  9. Expand repositories, teams, and actions in stages.
  10. Revalidate after a connector, model, deployment, or policy change.

​
Do not infer from the UI

The current settings audit does not establish contractual behavior for SSO/SAML, SCIM, data residency, exact retention, immutable audit logs, model-provider terms, availability, recovery, support access, packaging, or price.

​
Next step

Start with architecture and data flow, then use the administrator checklist.