Pricing follows the company, not a public grid
There is no self-serve price list. Scope depends on users, modules, integrations, migration, customisation, deployment, infrastructure and support. The modes below help us start the conversation.
Figures are not published here because they would be invented. Talk to us and we will scope the first slice of work.
Core Workspace
Teams that need one place for customers, projects, tasks and documents.
Drive with versioning, sharing and optional in-browser Office editing
Work: dashboard, tasks, calendar, presence, projects and diary
Roles, tenants, section ACL and audit
Web client and native iOS/Android with the same section tree
Needs configurationIdentity (email, Google and/or Microsoft)
Storage location
Who may see which tenants and modules
Connected Operations
Companies that need quotes, costs, workforce, quality processes and connections to what they already run.
Everything in Core Workspace, scoped to what you actually use
Quotes, costing, calendar, presence and absences
Operational CRM (queue, pipeline, account 360) where you need it
QMS quality registers and/or AI Act registers where they belong
Finance registers, Excel import, calendar sync and API-led connections
Needs configurationWhich operational modules are on
Migration from Excel and incumbent tools
Workflow automation if the engine should run
Private AI & On-Premise
Organisations that need Knowledge Engine, internal copilots, local models or dedicated infrastructure.
Knowledge ingestion and permission-aware retrieval
Domain copilots (work, diary, CRM, QMS, AI Act, Drive, analytics) with optional human confirmation
Ollama or Vertex, chosen with you
On-premise or private-cloud topology when required
Needs configurationModel hosting and data residency
Which corpora may be ingested
Support and maintenance for the AI hosts
What changes the investment
Your company does not need more disconnected tools.
Let’s identify the first process NexusOS can simplify.