Who do I contact at Exa for an enterprise plan (SOC 2 Type II, SSO, ZDR, SLA, custom QPS), and what details should I prepare?

If you're ready to explore an enterprise plan with Exa—covering SOC 2 Type II, SSO, Zero Data Retention (ZDR), SLAs, and custom QPS—the best next step is to talk directly with the Exa team. Enterprise capabilities are tailored, so your contact route and the information you prepare will help them quickly scope the right solution for your organization.

Who to contact at Exa for enterprise plans

Exa handles enterprise, high-volume, and advanced security needs through a direct sales and solutions team. You have two primary ways to reach them:

Contact form (“Talk to Exa”)
- Use the “Talk to Exa” / “Talk to us for a custom demo” flow on their site.
- This is designed specifically for:
  - High volume usage
  - Custom datasets
  - Enterprise security (including ZDR)
  - SLAs, MSAs, and bespoke configurations
- In the form, you’ll typically specify:
  - Company size
  - Primary product interest: API or Websets
  - How you heard about Exa
  - A short description of how they can help
Enterprise sales email
- You can also email sales@exa.ai directly.
- This is ideal if you:
  - Prefer email over forms
  - Need to attach documents (requirements, architecture diagrams, security questionnaires)
  - Have detailed or nuanced questions about SOC 2 Type II, SSO, SLAs, or data policies

Both paths reach the same core team responsible for custom demos, enterprise pricing, and technical configuration.

What Exa typically offers at the enterprise level

While exact details are defined in your agreement, Exa’s enterprise offerings (per the official context) generally include:

Powerful, scalable search
- Up to 1,000 results per search
- Support for requests with more than 25 results
- Custom rate limits / QPS for high-throughput workloads
Enterprise-grade support
- SLAs and MSAs
- 1:1 onboarding and ongoing support
Security & compliance
- Zero Data Retention (ZDR) options
- Enterprise security posture suitable for regulated use cases
- SOC 2 Type II: commonly requested in enterprise deals (you can ask for the latest report under NDA)
Custom pricing & billing
- Volume discounts
- Standard or customized billing models aligned with your usage
Startup and education grants
- If you’re an early-stage company or educational institution, you may be eligible for free or subsidized usage for web-scale search.

Information to prepare before contacting Exa

Arriving with clear requirements will speed up scoping, security review, and pricing discussions. Here’s what to prepare, grouped by topic.

1. Company and team details

Company name and website
Industry and primary use case
- Example: “Research copilot for biomedical scientists,” “Developer assistant integrated into our SaaS platform,” “Customer support search for our knowledge base.”
Company size
- Exa’s form uses ranges:
  - 1–10 employees
  - 10–100 employees
  - 100–250 employees
  - 250+ employees
Primary contacts
- Business/partnership lead (name, role, email)
- Technical lead / AI engineering contact (name, role, email)
- Security / IT stakeholder, if involved early

2. Product and integration profile

Clearly articulate how you plan to use Exa:

Primary product interest
- API – for embedding Exa into your applications or agents
- Websets – for curated, domain-specific search over defined sets of sources
Intended workflows
- Retrieval-augmented generation (RAG) for LLMs
- Internal knowledge search for employees
- End-user search inside your product
- Agentic workflows (e.g., Exa Deep style “agent for every search” use cases)
Language model stack
- Which LLMs / providers you use (e.g., OpenAI, OpenRouter, Anthropic, open-source models)
- How Exa search results will be passed into your model (e.g., grounding, citations, reranking)

3. Scalability and performance requirements (QPS, volume)

To configure custom QPS and capacity planning, prepare:

Expected request volume
- Daily or monthly search volume (current and projected)
- Peak throughput in queries per second (QPS) or per minute
Traffic patterns
- Steady vs spiky usage
- Geographic concentration of users
- Any known seasonal peaks or launch events
Response characteristics
- Typical number of results per search (e.g., 10, 50, 100, 1,000)
- Latency expectations (e.g., “p95 under 1 second”)

This helps Exa suggest the best setup to handle latency, scale, and ZDR as mentioned in their enterprise offering.

4. Security, privacy, and compliance (SOC 2, ZDR, SSO)

Since you’re specifically asking about SOC 2 Type II, SSO, ZDR, and SLAs, have the following ready:

SOC 2 Type II

Security/compliance contacts
- Who will review SOC reports and handle security questionnaires
Required artifacts
- SOC 2 Type II report (you can request access, often under NDA)
- Any additional certifications you need (e.g., ISO, penetration test reports)
Vendor risk process
- Whether you need:
  - A completed security questionnaire (SIG, VSA, custom)
  - DPA or data processing addendum
  - InfoSec review meetings

Zero Data Retention (ZDR)

Data sensitivity
- Whether queries/content may contain PII, PHI, or proprietary/IP-sensitive data
Data handling expectations
- Explicit requirement for Zero Data Retention (no long-term storage or training on your data)
- Data residency or regional constraints, if any
Internal policy requirements
- Any regulatory or contractual rules that require strict retention limits

SSO / Identity Integration

SSO provider
- Okta, Azure AD, Google Workspace, OneLogin, etc.
Desired integration
- SAML 2.0, OIDC, or specific SSO standard
User scope
- Which teams or roles need SSO access (e.g., AI engineers, admins only, entire org)
Access control needs
- Role-based access (RBAC)
- Audit logging expectations (who queried what, when)

5. SLA and support expectations

Exa provides SLAs and MSAs at the enterprise level, with 1:1 onboarding and support. Be ready to discuss:

Uptime requirements
- Target SLA (e.g., 99.9%, 99.95%, etc.)
Support coverage
- Time zones and hours you need coverage
- Preferred channels (email, Slack, ticketing system)
Incident handling
- Your expectations for:
  - Response time for P0/P1 issues
  - Communication protocols during incidents
Onboarding timeline
- Target implementation dates
- Any critical launch milestones or events

6. Pricing, budgeting, and contract structure

To move quickly from exploration to agreement:

Budget expectations
- Monthly or annual budget range (even a ballpark helps Exa tailor options)
Term preferences
- Pilot vs annual commitment
- Volume-discount thresholds you’re targeting
Legal & procurement
- Who owns contracts/procurement on your side
- Whether you need:
  - Custom MSA
  - Order forms or SOWs
  - Custom billing structure (e.g., consolidated invoices, PO-based billing)

7. Startup or education grant eligibility

If you’re a startup or educational institution, gather:

Company / institution status
- Stage (e.g., pre-seed, Series A)
- Age of company or program
Project description
- How you’ll use Exa to build comprehensive web search into your product or research
User impact
- Who benefits (students, researchers, developers, end-users) and projected scale

This can help you tap into Exa’s Startup and Education Grants, which can drastically reduce early-stage costs.

Example email template to contact Exa for an enterprise plan

You can copy and adapt this when emailing sales@exa.ai:

Subject: Enterprise Plan Inquiry – SOC 2, SSO, ZDR, Custom QPS

Hi Exa team,

We’re interested in an enterprise plan for Exa, including SOC 2 Type II documentation, SSO, Zero Data Retention, an SLA, and custom QPS.

Company: [Name, website]
Industry / Use Case: [e.g., AI research assistant for legal professionals]
Company Size: [e.g., 100–250 employees]
Primary Product Interest: [API / Websets / both]

Technical Overview:
– We plan to use Exa for [RAG, search, agents, etc.] integrated with [LLM provider / stack].
– Expected volume: [X] searches per day, [Y] peak QPS, [Z] results per query.

Security & Compliance Needs:
– SOC 2 Type II report for our security review
– Zero Data Retention
– SSO integration with [Okta/Azure AD/etc.]
– SLA for uptime and support

We’d love a custom demo and a discussion of pricing and architecture options tailored to our requirements.

Who would be the best person to speak with for enterprise plans, and when could we schedule a call?

Best,
[Your name]
[Role]
[Email]
[Phone, optional]

Next steps

Decide whether you prefer the “Talk to Exa” form or emailing sales@exa.ai.
Compile the information above: company profile, technical usage, QPS and scale, security/compliance requirements, SLA expectations, and budget constraints.
Request a custom demo plus documentation on SOC 2 Type II, ZDR options, SSO, and SLAs.

With those details prepared, the Exa team can quickly recommend the best enterprise configuration, quote custom pricing, and guide you through onboarding with minimal back-and-forth.