Licensed engineering docs
Premora is delivered under a license. Active license holders get access to an in-depth engineering reference covering how Premora is distributed, licensed, enforced, and operated — the level of detail an enterprise platform team needs to deploy and run it with confidence.
That reference is kept private to license holders. This public page is the front door to it.
What's in the licensed reference
- Distribution & licensing architecture — the vendor / tooling / customer boundary, and how releases reach your environment (connected or air-gapped).
- License model — how entitlement, channels, and expiry work, and how to issue and manage keys.
- Runtime enforcement — what happens as a license approaches expiry, and what "read-only on expiry" means in practice.
- Distribution server & break-glass — the release pipeline, channels, and the heavily-restricted recovery path for regaining admin access.
How to get in
- Go to the licensed customer docs (
dist.premora.dev). - Paste your Premora license key.
- It verifies your license and unlocks the full documentation — a normal docs site (search, navigation, the lot), served only to active license holders.
Your license key is the same one used to install and update Premora. If you don't have one yet, contact your Premora representative.
How licensing works, at a glance
- Premora installs and runs under a license that has an expiry.
- As expiry approaches, admins (and then all users) see a renewal reminder in the web client.
- If a license lapses, Premora becomes read-only — your knowledge stays searchable and readable, but ingestion and chat pause until it's renewed. Nothing is deleted.
The deeper mechanics — and everything an operator needs — live in the licensed reference above.