On-premise limitations

The private installation focuses on agents using your documents, approved APIs and chosen model. It does not include every feature of the online app.

Included in the free installation

Community mode includes one signed-in user and one live agent, document knowledge and API connectors within your installation’s access rules. You supply a local model or your own provider connection. No product key is needed.

Omnimatch does not impose a monthly token cap on your own model or provider key. Your hardware capacity and your provider’s limits still apply.

Features you can request

A product key can increase the user and agent limits and enable selected features such as company sign-in, anonymous chat, role-based access and audit history. Omnimatch models and selected hosted data are separate optional services. See Features & licensing for what each option provides.

Hosted features not included

• Scheduled tasks and background routines.
• Agent email inboxes and messaging channels such as Telegram, Discord, Teams, Google Chat and WhatsApp.
• The hosted marketplace, agent subscriptions and platform billing.
• Public conversation sharing, published dashboards and the hosted custom-domain service.
• Hosted browser automation, media tools and the generated agent wiki.

A product key does not enable these missing services in the current on-premise image. If one is essential to your workflow, discuss your deployment requirements before choosing an edition.

What air-gapped means

Disconnected operation requires a local model and local sources. External model providers, Omnimatch models, hosted data and online identity providers need network access to their services. Selecting a remote provider can send prompts and source material outside your network; zero data retention depends on that provider’s agreement and configuration.

Follow the air-gapped installation guide to prepare the image and local services.

Your operational responsibilities

The supplied deployment runs on one server. It does not provide automatic failover, managed replication or multi-node scaling. Do not run two application containers against the same data volume.

Your team manages HTTPS, network access, storage, model capacity, backups and updates. A server outage stops the application. Document processing interrupted by a hard stop resumes after restart and a subsequent request; it is not an independent distributed background service.

Keep a tested backup and recovery process. An update that changes the database can require restoring the matching backup to roll back.

Shared user guides

Use the same user guides for conversations, documents and agent management. Hosted-only guides are labelled, and the controls shown in your installation depend on its edition, product key and your role.