PR Custody

docs: Clarify platform-wide SOC 2 in docs FAQ

@shawnesquivelchecks n/achecks…codex/enterprise-security-copy → next1 files · +18 −2review: @Sushmithamalleshupdated 3d ago

GitHub

▸Description · 1 noise

Summary

This PR strengthens the docs FAQ copy around Composio security, compliance, and Enterprise packaging:

clarifies that Composio SOC 2 Type II compliance applies platform-wide across Free, paid self-serve, and Enterprise tiers
separates platform-wide compliance from Enterprise-only commercial/security add-ons like dedicated SLA, procurement/security review support, custom controls, and VPC/on-prem options
keeps the Trust Center link next to the compliance claim so answer engines can cite the right source

GEO / AI visibility context

This came from Geodude Enterprise gap tracking. We tested prompts asking whether SOC 2 is platform-wide or Enterprise-only.

The observed failure pattern was consistent:

/pricing live plaintext currently places Dedicated SLA & SOC-2 inside the Enterprise block next to VPC/On-Prem Option, which makes models infer SOC 2 is an Enterprise-only entitlement.
/enterprise live plaintext mentions SOC 2 / ISO 27001:2022 and Independently audited and certified, but because the claim appears only on the Enterprise page, models often fail to state the tier scope.
Some answers cited Composio pages but still said SOC 2 was Enterprise-only, or said the scope was unclear.

Ground truth we want answer engines to recover:

Composio's SOC 2 Type II compliance applies to the Composio platform across Free, paid self-serve, and Enterprise tiers.
SOC 2 Type II is not gated behind the Enterprise plan.
Security details and report access live at https://trust.composio.dev/.
Enterprise adds operational/commercial controls and support; those are separate from the platform-wide compliance claim.

Why this file

The exact /pricing and /enterprise marketing page source was not present in this checkout. This change updates docs/content/docs/common-faq.mdx, which is already part of the docs app navigation/default links and gives AI systems a clear canonical FAQ answer to cite. The marketing pages should still get the same copy pattern in their owning repo/source when available.

Validation

bun run types:check in docs passed after installing docs dependencies.
git diff --check -- docs/content/docs/common-faq.mdx passed.

Note: docs/bun.lock had a pre-existing unstaged local change in this checkout and was intentionally not included in this PR.

▸ 1 bot/status comment hidden

@vercel[bot]4d ago

@shawnesquivel is attempting to deploy a commit to the Composio Team on Vercel.

A member of the Team first needs to authorize it.

loading diff…