Skip to content

Licensing & tiers

DioscHub is licensed in three tiers — Free, Pro, and Enterprise. A tier decides two things: how much you can create (resource limits) and which capabilities are unlocked (features). This page sets out what each tier includes and how you apply a license, so you know which entitlements your deployment has.

Resource limits are enforced when you create something — reach the cap for your tier and DioscHub declines the create, naming the tier that would allow it.

ResourceFreeProEnterprise
Assistants13Unlimited
MCP instances13Unlimited
Knowledge bases15Unlimited
Toolsets550Unlimited
Roles per assistant310Unlimited
Sitemap entries per assistant1050Unlimited
Admin users15Unlimited
Active models13Unlimited

Active models are the models you have switched on in the model catalog. An Assistant’s primary model, its routing candidates and its fallback models must all be active, so they all count against this limit. A fallback has no separate tier switch: the Free tier cannot keep a second model active, so it has no fallback, and Pro (up to three active models) can run a primary with fallbacks.

When a deployment moves to a lower tier, DioscHub does not delete anything over the new cap. It keeps the newest items within budget active and sets the excess aside; moving back up reactivates them. Your configuration is preserved across a tier change.

Higher tiers unlock capabilities the lower tiers gate off. The ones with direct effect on a deployment:

  • Pro unlocks file handling (users uploading files into a chat), custom branding (below), business intelligence reporting, problem reports with the Problems page and its webhook sinks (the problemReports capability), and per-Role capabilities such as session-history lookup and custom approval dialogs.
  • Enterprise adds the admin role hierarchy — custom administrator roles and the RBAC ladder — and multi-instance federation, the licensed capability behind horizontal scaling.

Data-protection duties are never gated. On every tier, Free included, an Owner or DPO can find a person’s data, give them a copy of it, erase it, and turn on the retention window that deletes old conversations and files. A move to a lower tier never takes these away. The one retention option tied to a tier is waiting for Business Intelligence, which appears only where BI is licensed.

”Powered by DioscHub” on the Free tier

Section titled “”Powered by DioscHub” on the Free tier”

On the Free tier, the chat widget shows a non-removable “Powered by DioscHub” attribution. It is enforced on both sides: the backend serves the default styling and the widget renders the attribution regardless of what branding is configured.

From Pro upward, custom branding is unlocked — you replace the attribution with your own, and the backend stops forcing the default styling. The attribution is a branding entitlement, not a notice about the assistant; for how AI interaction is disclosed to users, see AI disclosure.

A license is installed as an environment variable when you deploy DioscHub — there is no in-app upload. With no license, a deployment runs on the Free tier.

  • A Pro license activates against the DioscHub license service and is cached locally, so it keeps working through brief connectivity gaps.
  • An Enterprise license is a signed license you install directly, with no callout — suited to air-gapped deployments.

DioscHub reads the current tier at startup and re-checks it on a daily schedule; the resolved tier is what drives the entitlements above.


Next: AI disclosure.