Licence
- Covers
- The right to run Omni Core, Content and Apps for a year, with the edition, user band and support terms.
- Sold as
- Annual licence. Quoted by edition and user band.
Licensing
A licence, a deployment, and the work to fit it.
Annual licence. Installation and customization in man-days. Scoped in weeks, not quarters.
01 · Layers
Three layers, one quote.
The licence is annual. The work is counted in man-days. Keeping the two separate is what makes the quote readable.
Deployment
- Covers
- Installation, hardening, connectors, identity, backup and handover on your infrastructure.
- Sold as
- Man-days. Scoped after a short assessment.
Tailoring
- Covers
- Custom connectors, taxonomy, workflows, templates and training for how your business works.
- Sold as
- Man-days. Fixed in the quote.
02 · Editions
Starter, Workstation, Enterprise.
Three editions, each with a support model and a set of indicative limits. The quote confirms the fit.
A single team
Starter
- Typical fit
- A first production deployment for one team.
- Deployment
- Single box or one private cloud account.
- Support
- Business-hours support and an annual upgrade window.
Indicative limits
- Up to 25 users
- 3 standard connectors
- 5,000 Concierge messages per month
A department
Workstation
- Typical fit
- A department or a multi-team site.
- Deployment
- Single node with a local model, or a private cloud account.
- Support
- Business-hours support with a named contact.
Indicative limits
- Up to 100 users
- 10 standard connectors
- 25,000 Concierge messages per month
The organisation
Enterprise
- Typical fit
- A regulated organisation or a multi-site rollout.
- Deployment
- On-prem, private cloud, hybrid or air-gapped, with HA data stores.
- Support
- Support retainer, a named owner and upgrade planning.
Indicative limits
- Unlimited users
- All standard connectors
- Volume by agreement
Indicative. Confirmed in the quote.
03 · Included
What the licence covers, and what is work.
The platform is in the licence. The fit is the engagement. This is where the line sits for each pillar.
Connect
Included in licence
Standard connectors and the connection layer.
Tailored in man-days
Custom connectors, field mapping and legacy interfaces.
Knowledge
Included in licence
Wiki, document ingestion, citations and permissions.
Tailored in man-days
Taxonomy, migration, cleanup and retention rules.
Conversations
Included in licence
Home, Concierge and Companion channels.
Tailored in man-days
Channel setup, tone, routing and handoff rules.
Workflows
Included in licence
The builder, approvals and run history.
Tailored in man-days
Workflow build, integrations and approval design.
04 · Engagement
The work, in man-days.
An indicative ladder, not a fixed menu. The quote fixes the sequence, the scope and the rate.
- ScopingCredited against the deployment.1–2 days
- Deployment and hardening3–5 days cloud · 5–10 days on-prem
- Connector setup0.5–2 days standard · 3–10 days custom
- Knowledge migration and taxonomy2–5 days
- Channel setup0.5–1 day each
- Workflow build1–3 days each
- Training and handover1–2 days
- Support retainerOptional
Assumptions
- One legal entity and one production environment.
- Standard infrastructure that meets the deployment checklist.
- Customer provides access, a business owner and a technical contact.
- Up to the agreed connector count; extra connectors are scoped separately.
Days are indicative; the quote fixes scope and rate.
05 · FAQ
Questions the quote answers.
Six that come up before the order. Anything else belongs in the scoping call.
How does a quote work, and is scoping credited?
A short scoping call sets the entity, edition, connectors and first workflows. We return a written scope, a day estimate and a licence quote. The 1–2 scoping days are credited against the deployment.
What is not included?
Commercial rates are set in the quote, not on this page. Hardware, model usage, third-party licences and travel sit outside the licence unless the quote says otherwise.
Where does the data live?
Wherever you deploy it. On-prem, private cloud, hybrid or air-gapped. The licence does not move the data; the deployment decides where it sits.
How do upgrades work?
Signed updates with a rollback path. The edition sets the support window; Enterprise adds upgrade planning and a retainer.
Can you build a custom connector?
Yes. Standard connectors are included by edition; a custom connector is scoped in man-days and fixed in the quote.
What happens when we exit?
The licence ends; the deployment does not disappear. You keep the data, the configuration and the audit records, and we hand over the runbooks. Portability is part of the exit plan.
Continue
The rest of the suite.
Quote
Scope the licence in weeks.
Tell us the entity, the edition and the connectors. We return a written scope, a day estimate and a licence quote — no rate card on a web page.