Licensing
The schnell.digital AI Kit is licensed per installation. This page explains the licensing model in plain terms so that you know what to expect when the trial ends or when your team grows.
For the daily management of license files and quotas, see Administration → Licensing.
What a license controls
A license file defines the limits — also called quotas — under which your installation operates. Typical quotas are:
| Quota | What it limits |
|---|---|
| Workspaces | How many separate team areas you can run on one installation. |
| Users | How many distinct accounts can exist across all workspaces. |
| Workflows | How many automations you can create per workspace. |
| Models | How many AI-model connections you can configure per workspace. |
| Knowledge | How many knowledge bases you can configure per workspace. |
Your specific quotas depend on the edition and term you purchased. When you upload your license file, the platform shows exactly what it grants.
License modes
| Mode | Description |
|---|---|
| Trial | Activated from the setup assistant with one click. Full functionality, time-limited. Designed so that you can evaluate the platform on real data without committing. |
| Standard | Production license tied to your organization. Renewable annually. |
| Enterprise | For larger deployments, multiple workspaces, and custom quotas. |
You can switch from Trial to Standard or Enterprise at any time by uploading the new license file — no reinstall, no downtime.
What happens when a quota is reached
The platform never silently overrides a quota. Instead, it stops the action that would exceed it and explains why.
- Creating a new workflow / model / knowledge / user above the quota returns an error message ("license insufficient") right in the user interface. The existing items continue to run.
- The trial expiring puts the workspace into a read-only state: existing automations stop on their next trigger, existing users can still log in, but no new content can be created. Uploading a valid license unfreezes the workspace within seconds.
This means there is no risk of being suddenly locked out — but it also means you should plan license renewals ahead of time.
What is not part of the license
The AI Kit license covers the platform. It does not include:
- AI provider costs. When you connect OpenAI, Anthropic, or Mistral, you bring your own API key and pay them directly per token. See Models → BYOK.
- Server infrastructure. For on-premise installations, hardware and operating costs are yours.
- Third-party integrations. Connecting to Google Workspace, MinIO, or a private database server may require credentials and permissions that you arrange yourself.
Recommendations
- ✅ Upload the license file before the trial expires. The administrator who initiated the installation receives a reminder email a few days in advance — make sure that address is monitored.
- ✅ Review quotas at least quarterly. Growth in users or automations often happens silently.
- ✅ When growing across departments, consider one workspace per department instead of cramming everything into a single workspace. Quotas in most plans are per installation, not per workspace.
- ⚠️ Treat the license file as confidential. It identifies your organization and is signed; do not share it outside the team that needs it.
- ⚠️ When you upload a new license, the existing one is replaced. Keep a copy of the file outside the AI Kit.
- ❌ Do not edit the license file. Edits invalidate the signature and the platform will reject it.
What to do next
- Day-to-day management: Administration → Licensing.
- Adding your first model: Models → Create a New Model.