For AI product teams

Ship the AI feature. Stop rebuilding its knowledge layer.

CorpusMesh maintains source-backed knowledge and returns retrievable context. Your models, prompts, agents, and application stay under your control.

Private beta
Access is reviewed manually for a named application. There is no public signup or public retrieval API.
Status
Private beta
Access
Manual review
Public API
None
Knowledge maintenanceeu-ai-act-reference
EU AI Act knowledge-maintenance boundary
Official sourceEUR-Lexmonitored source set
Corpus version2026-08-21.1source verified
Retrieval contractPOST /v1/retrieveprivate beta
Returned to your applicationpassagescitationsversiondecision

§01The recurring job

Your prototype is not the maintenance plan.

Finding a useful passage once is easy to demo. Keeping the source boundary current, reproducible, and safe to serve is the ongoing product work.

Recurring knowledge-maintenance work
WorkOutput
01Define the source boundaryName the authorities, documents, jurisdictions, languages, dates, and exclusions the feature is allowed to use.source inventory
02Preserve proof of originKeep the original artifact, reuse evidence, canonical URL, checksum, and transformation history attached to every version.provenance record
03Prepare retrievable knowledgeNormalize structure, add metadata, create deterministic chunks, and build a projection without making the vector store canonical.immutable version
04Measure retrieval before activationReplay a frozen fixture set, test citations and abstention, then activate only the version that passes its boundary.evaluation gate
05Operate the next source changeDetect upstream changes, rebuild deliberately, preserve the prior version, and keep rollback available.maintained service

§02A deliberate boundary

Knowledge on one side. Product intelligence on the other.

CorpusMesh does not take over the part of your application that makes decisions. It makes the knowledge input inspectable and consistent.

CorpusMesh maintains

  • source inventory and provenance
  • immutable corpus versions
  • retrieval profile and evaluation
  • citations, limits, and rollback

Contract

Requestquery + allowed filters

Responsecontext + citations + decision

Your team controls

  • model and provider
  • prompts and agent logic
  • customer experience
  • the final answer or action
Review the private-beta developer contract

§03Build versus buy

Build the part that differentiates your product.

CorpusMesh is useful only when the recurring knowledge work costs attention without creating product advantage. There are cases where keeping the whole pipeline internal is the right call.

Responsibilities when running the knowledge pipeline internally or using CorpusMesh
ResponsibilityRun internallyUse CorpusMesh
Source intakeYour team finds sources, documents rights, and defines completeness.A reviewed source inventory defines the bounded corpus.
Change handlingYour team monitors every authority and reconciles each material update.Source checks create a new candidate version only when content changes.
Retrieval qualityYour team owns chunking, embeddings, evaluation fixtures, thresholds, and regressions.A versioned retrieval profile must pass the corpus evaluation before activation.
ProvenanceYour team designs and preserves the path from each result back to the source.Source identity, version, metadata, checksums, and citations travel with results.
Serving boundaryYour team implements authorization, filters, quotas, metering, and rollback.The private-beta entitlement pins the permitted corpus, version, filters, and limits.
Source changes and recoveryYour team reviews changed text, reruns retrieval fixtures, schedules activation, and keeps the previous version recoverable.A verified candidate passes review and evaluation before activation, with the prior version retained for rollback.
Application and decisionsYour team owns the model, prompts, integration, product evaluation, and final decisions.Your team retains those responsibilities and checks that the returned evidence fits its workflow.
  1. N1Estimate the same workload

    For a 45-day trial, record hours spent on source monitoring, change review, indexing, retrieval evaluation, and recovery. Multiply the total by your loaded hourly cost, then add source licences, model-provider retrieval costs, storage, and hosting for those same 45 days. Separate initial setup from recurring maintenance so a quiet trial does not hide the cost of the next source change.

  2. N2Compare like for like

    The published EU AI Act beta is USD 1,500 excluding VAT for 45 days. Add your integration and application-evaluation time to that fee. Compare both options against the same sources, query volume, citation checks, update needs, and recovery requirements. Your model-generation and product costs remain yours in either case. Other knowledge bases need a separately reviewed scope and price.

  3. N3Keep it internal when

    The corpus is your proprietary advantage, the data cannot cross an external processing boundary, or the retrieval behavior needs control that a shared service should not promise.

§04Reviewed evidence

Inspect one retrieval all the way back to EUR-Lex.

The EU AI Act Source Trace is an internal engineering reference. It is fixed to a verified corpus version and a reviewed runtime result.

Corpus version
2026-08-21.1
Frozen fixtures
80
Boundary violations
0
Official source
EUR-Lex
Published evidence status
Verified internal retrieval
Limit
It is not customer proof and it does not make the service public.

§05Evaluate the fit

Follow the question to the right contract.

§06Questions from AI teams

Know the boundary before you integrate.

Does CorpusMesh run our model or generate the final answer?

No. Your team controls the model, prompts, agents, product behavior, and final output. CorpusMesh returns bounded passages, source metadata, citations, the corpus version, and a retrieval decision.

Why not build the knowledge pipeline ourselves?

You should when the corpus is a core proprietary advantage, must remain inside a boundary no provider can enter, or needs highly custom processing. CorpusMesh is intended for teams whose recurring source maintenance is necessary but does not differentiate their product.

Can we send production traffic today?

There is no public signup or generally available retrieval service. The prepared EU AI Act service is a manually reviewed private beta for a named application and entitlement.

Which knowledge is available?

The catalogue lists six knowledge bases in the private-beta programme. The English EU AI Act has a published limited-beta offer and reviewed retrieval evidence. Each other scope is qualified for its sources, rights, jurisdictions, and workflow before access; the catalogue records the evidence and next gate for each. Access is reviewed manually, with no public retrieval service.

How can we inspect the source behind a result?

The public EU AI Act Source Trace shows one fixed request, its enforced scope, ranked passages, official EUR-Lex citations, version, evaluation context, and lineage checksums.

Your knowledge problem

Tell us what your application has to keep current.

Name the sources, jurisdictions, update burden, intended workflow, and expected retrieval volume.

Request AI-team access