Core
MIT-licensed library, CLI and single-service API. You own scheduling, storage and retries. Free.
Xberg Pro and Xberg Enterprise
Core, Pro and Enterprise run the same extraction engine. Pro and Enterprise add what runs around it: durable jobs, storage, search, access control, audit and scale. Self-hosted, with no phone-home.
One engine, three packages
None of the three is a cut-down build. Choose by how much you want to run and maintain yourself. Audio and video transcription is Core only.
MIT-licensed library, CLI and single-service API. You own scheduling, storage and retries. Free.
One container plus PostgreSQL on a single node. Durable jobs, web console, crawling, search, Auto-Tune, connectors and an audit log.
Everything in Pro on your Kubernetes cluster, plus teams, SAML and SCIM, managed webhooks, document versions, data rooms and horizontal scale.
What runs around the engine
A durable job queue that survives restarts, retries and dead letters, with S3, GCS, Azure Blob or filesystem storage and presigned uploads.
Collections, ingest pipelines, hybrid retrieval on PostgreSQL with pgvector, and reranking. Local MCP clients can reach collections through an opt-in, private MCP listener.
API keys with read and write scopes, projects isolated by row-level security, OIDC sign-in, and monthly job and page quotas.
An append-only, hash-chained log of state-changing operations, with a verification routine.
Pro scales vertically on one node. Enterprise autoscales workers on queue depth and returns them when the queue drains.
Self-hosted by design
Docker Compose or Helm, on infrastructure you operate.
Pro license tokens are signed, valid for 180 days plus 30 days of grace, and verified locally. Enterprise licensing is by agreement.
Features that call an external model are off until you supply a provider and key.
Get started