VercatusEnterprise
Every domain you own, under your controls.
Vercatus measures each site's Answer Share on 10 answer engines, gives every market team the plays that move it, and reads whether each one moved it. Built for the review your security, legal and procurement teams run.
Up to 25 sites and no single sign-on? Get started with Portfolio
- sites in one workspace
- 10+
- seats included, viewers free
- 50
- answer engines, all included
- 10
- poll on the topics you choose
- Hourly
- days to a verdict on every shipped play
- 45
One workspace
for every market.
Each team sees its own sites, the platform owner sees all of them, and leadership gets the results.
- One view of the estate. Answer Share per site on one scale, the wins, and the top plays across every brand and market.
- Each market on its own terms. Each site has its own verification, topics, competitors and market, and the team that owns it sees only that.
- Results for leadership. Verdicts and wins for those who sign off, and a read-only quarterly review for the board, with your name and logo on it.
- Seats and roles. 50 seats for owners, admins and analysts; viewers are free and unlimited, so every stakeholder can read the results.
- An audit log of every decision. Plays shipped, exports, invitations, role and setting changes: who, when and from where. Append-only.
- Single sign-on. SAML 2.0 and OpenID Connect, enforced per verified domain, so identity stays with your provider.
Every control,
already published.
As they are today. No NDA and no form needed to read them; Enterprise adds a countersigned DPA and an agreement of its own.
- Domain authorisationA customer's site is analysed only once verified by Search Console, DNS record or meta tag.
- Crawler identityNamed user agent, signed page requests in runs and the watch (RFC 9421), a published key, robots.txt honoured by runs.
- Stored data and retentionPage bodies 30 days; derived data for the life of the workspace.
- Access isolationEvery record and request scoped to its workspace; row-level security behind it.
- Model providersRead under no-training terms; content is analysed, not learned from.
- Roles and auditOwner, admin, analyst, viewer and client; an audit log of every play shipped, export and setting change.
- Single sign-onOpenID Connect or SAML 2.0, verified domains and enforcement, set up in the workspace.
- Data processing agreementPublished at /dpa/ with the sub-processor list; signed copies for Enterprise.
PlannedWritten as planned in contracts: a SOC 2 attestation (none is held today), a choice of EU or US data region with EU-only analysis, and shorter retention of page bodies on request.
Fits the stack
you already run.
A play goes to whoever ships the change, with its evidence and its acceptance check. Everything the workspace shows is in the API and MCP.
- Hand-offs
- Claude Code · Codex · Linear · Jira · GitHub · Asana
- Alerts
- Slack · Microsoft Teams · Email
- Outcomes
- Search Console · Google Analytics · Crawler traffic from your edge or logs
- CMS and deploys
- Shopify · Contentful · Sanity · WordPress · Any deploy step
- Build on it
- REST API · MCP server · Signed webhooks · Command-line client, on request
citation.changedThe site entered or dropped out of an answercompetitor.changedA competitor moved past the sitetraffic.changedAI-referred sessions or crawler traffic movedaccess.changedAn AI crawler was refused or servedengine.driftAn engine changed what it cites
A typical onboarding,
week by week.
Not a contract term: the pace is set by whoever owns your DNS, identity provider and ticketing.
- Week 1
Verify and measure
Verify domains, set topics and competitors per market, and read each site's first Answer Share.
- Week 2
Sign-in and teams
Connect single sign-on, test it, and invite teams by role.
- Weeks 3 to 4
The first plays
Ship the top plays, handed to Claude Code, Codex or a ticket. Your CMS or deploys tell Vercatus when each one is live.
- Then every month
Verdicts
Each shipped play is read on days 14, 30 and 45 against topics left alone.
What platform owners and procurement ask.
Anything else your review needs: ask, and we answer in writing.
Talk to salesWhat does Enterprise include?
10 sites and 50 seats to start, with viewers free and unlimited; more of either are set in the agreement. Topics are set in the contract, and the poll runs hourly on the topics you choose. Every engine, Why, Engine Briefs, plays and verdicts are included, with hand-offs, the API and MCP, single sign-on and a countersigned DPA.
Where is our data stored and processed?
The application and the database run in Amsterdam, so workspace data is stored in the EU, and fetched page bodies are deleted after 30 days. Analysis goes to US model providers under the EU-US Data Privacy Framework or standard contractual clauses. A choice of EU or US per workspace, with EU-only analysis, is planned and stated as planned in contracts.
Is our data used to train models, or shared?
No. Analysis runs under a no-training agreement with the model provider. Vercatus Intelligence learns from verdicts and public pages in aggregate, never from a workspace, a site or a question, and shows nothing until enough sites stand behind it. Your analytics, Search Console data and crawler logs stay in your workspace; the only thing pooled from crawler logs is a ratio of observed to modelled AI demand, which names no site.
How do client and site permissions work?
Owners and admins have workspace-wide access. Analysts and viewers can be limited to selected sites; clients always have selected sites and narrower permissions. Use separate client workspaces where that is the required boundary. Branding is separate from access.
How does the data processing agreement work?
The agreement is published at /dpa/ and applies to every workspace as part of the terms, with the sub-processor list. Enterprise customers receive a copy countersigned by Vercatus on request.
Do you hold a SOC 2 attestation?
Not yet. SOC 2 is planned; no attestation is held today and none is implied. The security page lists every control with its true status. Send your review questions through sales.
Which identity providers work with single sign-on?
Okta, Microsoft Entra ID, Google Workspace and any OpenID Connect provider that publishes a discovery document, plus SAML 2.0 identity providers such as ADFS, JumpCloud, OneLogin and PingFederate. Sign-in starts from Vercatus; SAML assertions must be signed.
Can we require single sign-on for everyone?
Yes, per verified domain. An owner turns enforcement on once a connection has signed someone in, so nobody is locked out by a connection that never worked. Password sign-in and sign-up, and Continue with Google or Microsoft, are then refused for that domain, owners included. API keys keep working.
Can we route analysis through our own model provider?
Yes, on Enterprise: analysis routed through your own Anthropic, Amazon Bedrock or Google Vertex AI account, so prompts and responses stay inside your contract.
How is Enterprise contracted and invoiced?
Under its own agreement: Enterprise is quoted and invoiced separately, and the allowances stated there replace the published plan allowances. Tell us how your procurement runs when we first talk.
What does an evaluation look like?
A 30-minute call about your domains, teams and review process; two or three of your own sites set up under the published DPA, with topics and competitors per market and a first Answer Share; the first plays walked through with the people who act and the people who sign off; then a proposal with the allowances in writing. Every play you ship gets a verdict within 45 days.
Start with two of your own domains.
A 30-minute call about your estate and your review, then a first Answer Share on your own topics.
SAML 2.0 and OIDC · Data stored in the EU · Countersigned DPA