One login. Every Comley Nexus product.
Comley Nexus is the shared layer under Nexus Field and Nexus CMS: one sign-in, one permission model, one design system. Your teams stop switching tools; your admins stop reconciling them.
The plumbing every app was rebuilding, built once
Each product used to carry its own login, its own roles, its own branding and its own admin screens. Comley Nexus consolidates the parts that should never have been duplicated. Each product stays free to be good at its own job.
One identity, everywhere
People sign in once and land in whichever app they have access to. Joiners and leavers are handled in one place, not three.
Status pages backed by real checks
Every app reports real dependency checks and usage metrics on a schedule, so status pages reflect what is actually happening.
Features you can turn on
Capabilities are switched per workspace from the console: no release, no ticket, no code change to give one customer early access.
Your brand, per workspace
Colors, logo and tone are stored as design tokens and applied at runtime, so the same components render wearing your customer's identity.
Field and CMS, on one platform
Buy what you need today. Everything here shares identity, design and administration, so adding the next product is a switch rather than a project.
Nexus Field
Job scheduling, mobile-first task capture and audit trails for teams whose work happens away from a desk.
Nexus CMS
Content, pages and publishing for marketing sites: versioned, scheduled and safe to hand to non-developers.
Coming soon
Nexus Connect
CRM connecting all of Comley Nexus apps. Contacts, work sites, and message tracking that streamlines communication across the whole team.
Enforced in code, checked on every request
The rules below run in code across every app on the platform. They are why a new product can be added without re-litigating security from scratch.
- Access control
- Deny by default
- Tenancy
- Server-set
- Accountability
- Full audit trail
- Availability
- Real checks
Unknown page or capability is refused, never silently allowed. The server decides; the interface only reflects it.
A workspace is resolved from the verified session, never from anything the browser sends. Cross-tenant reads are structurally impossible.
Every change routes through one logging path, so "who changed this, and when" is always answerable.
Health endpoints test a live dependency rather than returning a hopeful 200, and the console polls them continuously.
See it running on your own operation
A 30-minute walkthrough with the people who built it. We will show the console live, against real data, and tell you plainly what is production-ready today and what is not.