Private beta pricing

One maintained knowledge base. One fixed beta.

Test CorpusMesh in a real AI application without building the source, provenance, versioning, and retrieval pipeline yourself.

Limited availability. Every organization and application is reviewed manually.

Limited-beta service ledger45-day fixed term
EU AI Act referenceOne maintained entitlement
USD1,500excluding VAT
Maintained delivery pathCM-ENT-0001
01 · Source setApproved sourcesEUR-Lex · checked daily
02 · VersionSealed corpusprovenance · rollback
03 · PlanBounded retrievallimits enforced
04 · DeliveryNamed applicationpassages · citations
Knowledge bases
1
Monthly requests
5,000
Maximum top_k
5
Delivery
REST
One organizationOne named applicationNo automatic overage
No seat pricingNo token markupNo automatic overageNo checkout before review

The paid boundary

Pay for maintained knowledge, not a pile of vectors.

The beta covers the operating work between an official source and the bounded context your application retrieves. Your model, prompts, agents, and product remain yours.

See the maintained pipeline →
  1. 01

    Knowledge boundary

    One maintained EU AI Act knowledge base, in English, for one named application.

  2. 02

    Retrieval capacity

    5,000 requests per month, 250 per day, 10 per minute, and 2 concurrent requests.

  3. 03

    Response boundary

    Up to 5 passages, 4,000 characters per passage, and 50,000 bytes per response.

  4. 04

    Integration support

    One 60-minute technical kickoff and one 60-minute integration review.

  5. 05

    Source maintenance

    Daily checks of the approved official source set during the beta.

How pricing scales

The knowledge base is the product unit.

Request capacity scales the service inside that entitlement. We do not charge for customer seats or add a margin to the tokens used by your own model.

Primary unitKnowledge-base entitlementMaintained coverage, versions, provenance, and citations
Capacity unitRetrieval requestsBounded by rate, response size, and corpus exposure
Scoped separatelyRights and service needsAnother application, redistribution, higher limits, or an SLA

Before credentials are issued

The agreement makes every limit explicit.

There is no self-service checkout. We confirm the application, source boundary, permitted use, and payment before the beta starts.

Included

REST retrieval, citations, source metadata, immutable versioning, bounded updates, and email support.

Not included

Legal advice, compliance decisions, corpus exports, vectors, MCP, a customer dashboard, or self-service billing.

Usage above the plan

No automatic overage. Requests above the approved limits are rejected before retrieval work begins.

Service commitment

No public uptime SLA. The initial support-response target is two business days.

After the beta

USD 6,000 annual hypothesis.

The current annual hypothesis covers the same knowledge base and limits, billed annually and excluding VAT. If an annual agreement is signed within 30 days of the beta review, the USD 1,500 beta fee is credited against its first term.

Pricing questions

What the fixed beta does and does not buy.

Is USD 1,500 a subscription?

No. It is the fixed price for a 45-day limited beta. The beta starts after the application boundary and agreement are approved and credentials are delivered.

What happens after 45 days?

The beta ends with a commercial and technical review. The current annual hypothesis is USD 6,000 excluding VAT for the same knowledge base and service-plan limits. It is not an automatic renewal.

Can we use more than 5,000 requests?

Not through automatic overage billing. A higher limit requires a reviewed service-plan revision that preserves capacity and extraction controls.

Can we add another knowledge base?

Each knowledge base has separate source, rights, maintenance, evaluation, and support costs. CorpusMesh prices another entitlement after its product boundary is ready.

Do you charge per user or token?

No. The primary unit is access to one maintained knowledge base. Request capacity is the secondary limit. Your team keeps control of its own model and generation costs.

One application, one real test

See whether maintained retrieval removes work from your team.

Describe the application, required source boundary, filters, and expected request volume. We will confirm whether the limited beta fits.

Request beta access