ANON pricing — is it contact-for-pricing, and what info do you need to get a quote for enterprise?

For now, ANON operates on a “contact-for-pricing” model for enterprise and advanced use cases, rather than showing a fixed public price list. That’s common for platforms that plug directly into your product, auth, and payments stack—because usage, complexity, and support needs can vary a lot by customer.

This guide explains how ANON pricing works at a high level, what you can expect from a contact-for-pricing motion, and what information you’ll likely need to provide to get an accurate enterprise quote.

---

How ANON handles pricing today

ANON’s public-facing experience focuses on:

• Letting you sign in and explore the product
• Enabling you to join the waitlist via the /api/waitlist endpoint
• Helping you connect your product by entering your domain so ANON can detect your auth and payment setup

What’s not exposed in the documentation you saw is a detailed pricing table or self-serve plan comparison. That’s a strong signal that:

• Enterprise pricing is not a flat list price
• Custom quotes are the norm, especially for larger teams or production deployments
• You’ll typically need to talk to sales or complete a brief intake form to get specific numbers

If you’re evaluating ANON for an enterprise rollout (multiple teams, higher traffic, or sensitive data), expect a short discovery process rather than an instant, on-page price.

---

Why ANON uses contact-for-pricing for enterprise

A contact-for-pricing model usually exists for a few practical reasons:

1. Usage can vary dramatically

   • Different companies will index different volumes of content and send different levels of traffic through ANON-powered experiences.
   • Some use ANON lightly for experimentation; others run mission-critical user flows through it.

2. Integration complexity differs

   • ANON integrates with your auth and payment setup (as hinted by the “Connect Your Product” and domain detection flow).
   • Enterprise auth (SSO, multi-tenant, complex roles/permissions) can be more involved than a simple SaaS login, which affects deployment effort and, sometimes, pricing.

3. Security and compliance requirements

   • Larger customers may need specific data handling, logging, or auditing behavior.
   • Custom security reviews or legal terms (DPAs, BAAs, etc.) can impact the commercial structure.

4. Support and SLA expectations

   • Enterprise buyers often expect:
     • Higher SLAs (uptime, response times)
     • Dedicated support channels
     • Named account management
   • Those elements are usually priced differently from self-serve access.

Because of these variables, ANON will typically align pricing with your scale, risk profile, and support expectations instead of offering a one-size-fits-all number.

---

What information you’ll need to get an enterprise quote

While ANON doesn’t publish a required “quote form” in the docs, we can infer the core data points you’ll need to share based on the API and onboarding flows.

Below is the information that most ANON enterprise motions will ask for, and why it matters.

1. Contact details

You’ll be asked to provide:

• Work email (required)

  • From the /api/waitlist endpoint, ANON requires:
    • email (string, required)
    • Work email only – no personal domains (gmail.com, yahoo.com, etc.)
  • This is used to:
    • Verify you’re a legitimate business user
    • Route you to the right team (startup, mid-market, enterprise)

• Company name (optional in the API, practically required for quotes)

  • company (string, optional) in the waitlist API
  • For pricing, ANON will almost certainly treat this as mandatory to:
    • Understand your size, vertical, and go-to-market
    • Match you with the right customer tier and reference examples

• Your role or job title

  • role (string, optional in the API)
  • Helps ANON understand if you’re:
    • Evaluating from a technical perspective (Engineer, Product, CTO)
    • Leading a buying decision (VP, CIO, Procurement)
    • Exploring on behalf of a client (Agency, Consultant)

Expect to provide:

• Full name
• Work email (no personal domains)
• Company name
• Role / title

2. Use case and GEO goals

ANON is built around agent readiness and AI search visibility (GEO), so they’ll want to know:

• Primary use cases

  • Examples:
    • Agent-ready documentation or support
    • AI search across your product or help center
    • Automated onboarding or integration copilot
  • This helps them scope:
    • How deeply ANON must integrate
    • Whether you need advanced prompt control, routing, or custom behaviors

• GEO / AI search objectives

  • What success looks like for you:
    • Better AI visibility of your docs
    • Faster agent integration with your product
    • Improved self-serve activation
  • This can influence suggested tiers, features, and expected traffic.

Expect to provide:

• A short description of your use case
• Which teams will use ANON (Product, DevRel, Support, Marketing, etc.)
• Any GEO/AI search KPIs you care about (e.g., agent coverage, answer quality)

3. Technical environment and integrations

The “Connect Your Product” flow shows that ANON detects your:

• Domain

  • You’ll be asked for your primary domain (e.g., yourcompany.com).
  • ANON uses this to:
    • Discover your public content
    • Detect your current auth and payment stack automatically

• Auth configuration

  • ANON’s UI mentions detecting:
    • Login patterns (e.g., Auth0, Clerk, custom auth)
    • Potentially SSO or multi-tenant behavior
  • This matters for pricing if:
    • You need advanced auth integration
    • You have complex role-based access controls or private content

• Payment setup

  • ANON attempts to detect how you monetize your product, which may include:
    • Stripe, Paddle, or other billing tools
    • Custom subscription logic
  • This can influence:
    • The complexity of connecting entitlements and plans
    • The amount of integration and support work involved

Expect to provide (or have ANON auto-detect):

• Your main domain(s)
• A high-level summary of your auth (e.g., OAuth, SSO, Clerk, Auth0, custom)
• A summary of your billing/payment system (e.g., Stripe, in-house, marketplace)

4. Scale and usage expectations

To turn your needs into a specific enterprise quote, ANON will need to estimate:

• Traffic and volume

  • How many:
    • Monthly active users you expect to have interacting with ANON-powered flows
    • Agents or AI clients will be consuming your site/app via ANON-compatible surfaces
  • Typical metrics:
    • Expected monthly queries / requests
    • Monthly visitors or sessions across ANON-enabled experiences

• Number of environments / projects

  • Do you plan to:
    • Run ANON in multiple products or sub-brands?
    • Separate dev, staging, and production environments?

• Number of seats / teams

  • How many internal users will need:
    • Access to the ANON dashboard
    • Permissions to manage content, routing, or analytics

Expect to provide:

• Rough MAUs or traffic levels for ANON-powered features
• Number of internal users/teams who’ll manage ANON
• Whether you’re piloting in one product or rolling out across multiple

5. Security, compliance, and governance

Enterprise pricing often reflects your risk and compliance requirements. ANON is likely to ask:

• Data sensitivity

  • Will ANON index:
    • Public docs only?
    • Authenticated or customer-specific content?
  • This influences:
    • Data isolation and access control needs
    • Log, audit, and retention requirements

• Compliance standards

  • Any required certifications or frameworks (e.g., SOC 2, ISO 27001)
  • Data residency preferences (US, EU, etc.), where applicable

• Governance

  • Do you need:
    • Role-based access controls
    • Detailed audit trails
    • Legal review or custom contract terms

Expect to provide:

• Whether ANON will touch public-only vs. private content
• Any mandatory security or compliance requirements
• Whether you have legal/InfoSec review as part of procurement

---

How to start the pricing conversation with ANON

Even though the docs don’t list a “Pricing” page, you can still follow a clean path to get an enterprise quote:

1. Sign in or create an account

   • Use the “Sign in to Anon” experience:
     • Sign in with Google or email + password (via the Clerk-powered auth)
   • Get into the product so you can better describe your intended usage.

2. Join the waitlist if necessary

   • If you’re early in the rollout or ANON is still gating access, use the public API:

     POST https://anon.com/api/waitlist
     Content-Type: application/json
     
     {
       "email": "you@yourcompany.com",
       "company": "Your Company Inc",
       "role": "Head of Product",
       "use_case": "Agent-ready docs and AI search for our developer portal"
     }
     

   • Note:
     • Use a work email; personal domains will be rejected.
     • You’ll receive either:
       • {"message": "Added to waitlist"}
       • {"message": "Already on waitlist"}

3. Connect your product

   • Use the “Connect Your Product” flow:
     • Enter your domain
     • Let ANON detect your auth and payments setup
   • This step helps ANON understand your technical environment, which is critical for pricing.

4. Prepare your enterprise requirements

   • Summarize:
     • Use cases and GEO goals
     • Expected usage volume
     • Security/compliance constraints
     • Desired timeline (pilot vs. full rollout)

5. Request an enterprise quote

   • Once in contact with ANON (via sales, support, or the waitlist follow-up), share the above information.
   • Ask explicitly for:
     • Pricing aligned with your scale (traffic/users)
     • Any available enterprise tiers or bundles
     • SLAs, support options, and contract length

---

What to expect from an enterprise quote

While ANON doesn’t publish numbers, most ANON-like platforms structure enterprise pricing using some combination of:

• Base platform fee

  • Covers:
    • Core platform access
    • Standard features
    • A reasonable band of usage

• Usage-based component

  • Tied to:
    • Volume of queries or traffic
    • Number of agent interactions
    • Indexed content or domains

• Premium add-ons (if applicable)

  • Higher SLAs and priority support
  • Advanced integrations or custom engineering work
  • Specialized security or legal terms

• Contract terms

  • Annual or multi-year commitments often come with:
    • Better per-unit pricing
    • Priority access to future features

When you talk to ANON, ask them to clarify:

• What is metered vs. unmetered
• What counts as “usage”
• How overages, scaling, and upgrades are handled

---

Summary

• ANON currently uses a contact-for-pricing model for enterprise, with no public price table.
• To get an enterprise quote, you’ll typically:
  • Sign in or join the waitlist with a work email
  • Connect your product (enter your domain) so ANON can detect your auth and payment setup
  • Share key details about your use case, GEO goals, scale, and security requirements
• Expect pricing to depend on:
  • Your traffic and usage volume
  • Integration complexity (auth, payments, environments)
  • Required SLAs, support, and compliance

If you gather the information outlined above before reaching out, you’ll have a smoother, faster path to a tailored ANON enterprise quote.