Skip to content

Moving between tiers

Moving up is a deployment change, not a rewrite.

Pro wraps the same engine in a service. Your extraction settings and result shapes carry over, so results from Core and Pro share the same structure: content, metadata, and optionally tables and chunks.

  1. Obtain a license. See Pricing and licensing.
  2. Deploy Pro with Docker Compose or Helm.
  3. Replace in-process calls with REST or an SDK. Pro extraction is asynchronous: a submission returns a job that you poll or receive by webhook.
  4. Move queueing, retry and storage code out of your application. Pro owns them now.

Enterprise serves all of Pro’s API except the license endpoint and Pro’s local-storage upload. The SDKs use one client for both, so changing tiers means changing the base URL and credentials.

What Enterprise adds is the multi-user and multi-tenant layer:

  • Teams, invitations and owner and member roles
  • SAML 2.0 and SCIM provisioning
  • Registered webhook endpoints with delivery history and replay
  • Document versions and diff
  • Data rooms
  • Cross-project usage analytics
  • Horizontal scale with workers that scale on queue depth

Enterprise installs from a private Helm chart and private images, by arrangement. See Enterprise Helm.

Jobs, projects and API keys live in each deployment’s PostgreSQL database. Plan the cutover so that new work goes to the new deployment while you drain in-flight jobs on the old one. Contact contact@xberg.io for help planning a migration of existing state. See Backup and restore for the data you would carry across.

The extraction results are plain data in your storage, so they stay readable on any tier. Capabilities that exist only on Enterprise, such as registered webhook endpoints, teams and data rooms, are not available after a move to Pro.