Customers
Customers we’re rolling out to, one team at a time
VeriFlow is in private beta with a small set of design-partner teams. Rather than a customer wall, this page is the candid disclosure of where the rollout is today and what the production shape of the product looks like — so a team evaluating VeriFlow can see the trust surface, the tier shapes, the audit posture, and the dual intake for Teams and Enterprise in a single place.
Honest disclosure
Currently in private beta
No customer logos, no named quotes, no customer counts, no ARR numbers, and no NPS tiles ship on this page. The trust surfaces VeriFlow publishes today are the trust surfaces the trust pages already document — encryption in transit and at rest, per-repo and per-review-run isolation, the GitHub App permissions map, the audit-logging posture, and the SOC 2 Type II readiness timeline.
VeriFlow is being rolled out to a small set of design-partner teams, one at a time, in collaboration with their security and platform groups. The shape of those rollouts is what informs the production posture documented on /security and the tier breakdown documented on /pricing. The program is not yet at general availability — the Teams and Enterprise tiers are open to new design partners now, and a public self-serve Free tier is part of the same release track.
Named customer references — design partners willing to speak to their rollout on the record — land as those partnerships move out of the NDA-incubation window. The pattern here mirrors the team grid on /about: the role-flavored copy ships today, the named roster lands as the names become public. Same honesty standard on both surfaces.
A team evaluating VeriFlow today can take the outcomes in the band below and verify each one on the existing trust pages. The dual intake — self-serve Teams or an Enterprise conversation through the contact form — is the path forward regardless of which tier the rollout sits on.
Outcomes
What a design-partner rollout gets today
Three outcome shapes the production rollouts are landing on. Each card is grounded in a tier feature on /pricing and a control band on /security — so the claim is verifiable on the existing trust surfaces, not on a fabricated customer stat.
The Teams tier is sized for an engineering org that wants every pull request reviewed on day one — 500 PRs reviewed / month, up to ten connected repositories, and seating for twenty reviewers per repo, with a one-business-day support SLA. See the tier breakdown on /pricing and the per-review-run isolation shape on /security.
The Enterprise tier includes SAML plus SCIM as part of the plan, and the boundary the agent never crosses is set at install time: the GitHub App sees only the repositories you grant, and nothing else in the workspace is reachable. The full permissions map and webhook-subscription list lives on /security; the pricing tier rows live on /pricing.
Enterprise customers get a 1-hour SLA, a dedicated CSM, and the full audit-logging posture: every webhook delivery (accepted and rejected), every review run with the diff version it consumed and the comments it produced, and every App install / scope change with actor and timestamp — defaulted to twelve months retention, with extension available. The audit-logging band is the same surface the rollout brief references on /security; the SLA and CSM shape is part of the Enterprise row on /pricing.
No customer count, NPS score, or named testimonial is shown above — the outcome cards stay grounded in the pricing tier features and the security controls documented on the existing trust pages.
Ready to start?
Teams is the self-serve intake — pick a name, point VeriFlow at the repositories you want reviewed, and the agent is running on day one. Enterprise is a conversation through the contact form — SAML, data residency, the SLA cadence, and the audit-log shape are part of the same intake, so the engineering and security teams on both sides line up on the rollout plan before the first review posts.