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.

Availability
Limited availability. Every organization and application is reviewed manually.

Limited-beta service ledger

45-day fixed term
Price

USD1,500

excluding VAT · fixed price for one 45-day limited beta

Entitlement
CM-ENT-0001
Knowledge base
EU AI Act reference, English
Organizations
1
Applications
1 named application
Term
45 days, fixed
Monthly requests
5,000
Delivery
REST
Overage
None. Rejected before retrieval
Access
Manual approval, signed agreement
  • No seat pricing
  • No token markup
  • No automatic overage
  • No checkout before review

Delivery path

From approved source to one named application.

  1. 01 Source setApproved sourcesEUR-Lex · checked daily
  2. 02 VersionSealed corpusprovenance · rollback
  3. 03 PlanBounded retrievallimits enforced
  4. 04 DeliveryNamed applicationpassages · citations

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

What the limited beta includes
LineItemBoundary
L01Knowledge boundaryOne maintained EU AI Act knowledge base, in English, for one named application.
L02Retrieval capacity5,000 requests per month, 250 per day, 10 per minute, and 2 concurrent requests.
L03Response boundaryUp to 5 passages, 4,000 characters per passage, and 50,000 bytes per response.
L04Integration supportOne 60-minute technical kickoff and one 60-minute integration review.
L05Source maintenanceDaily checks of the approved official source set during the beta.

Service-plan limits

Limits apply before expensive retrieval work.

Maximum top_k
5
Passage length
4,000 characters
Response size
50,000 bytes
Request rate
10 per minute
Concurrency
2 requests
Daily allowance
250 requests
Monthly allowance
5,000 requests
Request body
16,384 bytes
Plan authority
The values describe the prepared EU AI Act beta plan. The immutable plan attached to an issued entitlement remains authoritative.

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.

  1. Primary unitKnowledge-base entitlementMaintained coverage, versions, provenance, and citations
  2. Capacity unitRetrieval requestsBounded by rate, response size, and corpus exposure
  3. 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.

INIncluded
REST retrieval, citations, source metadata, immutable versioning, bounded updates, and email support.
OUTNot included
Legal advice, compliance decisions, corpus exports, vectors, MCP, a customer dashboard, or self-service billing.
REJECTUsage above the plan
No automatic overage. Requests above the approved limits are rejected before retrieval work begins.
NO SLAService commitment
No public uptime SLA. The initial support-response target is two business days.

After the beta

From request to USD 6,000 annual hypothesis.

  1. T0RequestDescribe the application, source boundary, filters, and expected volume.
  2. T1Manual reviewWe confirm the application, source boundary, permitted use, and fit.
  3. T2AgreementLimits, permitted use, and payment are made explicit before access.
  4. T3 · day 0CredentialsDelivered after approval. The 45-day term starts here.
  5. Day 45Beta reviewTechnical and commercial review at the end of the term.
  6. Review + 30 daysAnnual hypothesis · USD 6,000The 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.

Not an automatic renewal. The beta ends with a technical and commercial review. The annual boundary becomes a contract only when both sides approve it.

Equivalent to USD 500 per month when billed annually

Pricing questions

What the fixed beta does and does not buy.

Q1

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.

Q2

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.

Q3

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.

Q4

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.

Q5

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

Reviewed manually · no checkout