Nucleus
Nucleus is the connect product. It brings the third-party software you already run onto the OneOps Gateway: import and harmonize records, keep them synchronized, provision and deprovision business assets, define your businesses, departments, and attributes, and feed a continuous stream of operational data into the OneOps Datalake. The result is one live mesh that the rest of the platform, and your own agents, can work over.
Identity and access
Every user signs in with their own account. Access is role-based: a role decides which parts of the platform a person can reach and which actions they can take.
- Sign-in. Email and password with optional multi-factor authentication, and single sign-on for organizations that use an identity provider.
- Roles. A named bundle of permissions assigned to each member. Roles map to least privilege, so a person gets what their job needs and nothing more. See Roles and access.
- Tenant scope. Your active organization is resolved on the server for every request, never chosen by the browser, so you only ever see your own tenant's data.
Multi-tenant isolation
Each organization is its own tenant: an isolated workspace with its own data, members, and settings.
The platform is designed to keep tenants apart even in joint arrangements, so two operators partnering on a contract can each keep their own data isolated.
The OneOps Datalake
Connected systems do not only answer live queries. Nucleus keeps a continuous stream of the operational records it brings in, landed in the OneOps Datalake, so reporting and analysis run over a consistent history rather than over whatever each source happens to return today. The datalake is read-only to the products that consume it.
The connector catalog
The connector catalog is how Nucleus connects a system. You add a connector the way you add a service: browse the catalog, enable the ones you need, configure each once, and go live.
- A connector wraps an external system's API as a set of typed operations, so the same actions look identical no matter which underlying system fulfills them.
- Live connectors disclose the read-only tools they expose to AI Studio; write actions are withheld from agent surfaces.
- Connectors are organized by category (dispatch and scheduling, billing and payments, fleet and vehicle management, identity providers) and tiered as live, coming soon, or future.
The full setup and operations flow lives in Integrations.
The workspace shell
The workspace shell is the shared surface the products appear inside. Each part has its own guide.
- Projects. Group related chats under shared instructions and reference files. See Projects.
- Agents. The roster of agents the assistant can put to work, each with a role, a model, tools, and pinned connectors. Tenant admins can edit, duplicate, add, or disable agents. See Using chat.
- Skills. The catalog of reusable capabilities agents can run, browsable by department and pinnable to a project. See Skills.
- Editor. A rich-text drafting surface with AI assistance. See The editor.
- Audit log. An append-only record of who did what and when, scoped to your workspace. See Audit and usage.
- Usage. Turns, tokens, and estimated cost for your workspace, by day. See Audit and usage.
See also
- AI Studio, where you create and test skills and agents over the data Nucleus brings in.
- AI Operations, where those skills and agents run full time.
- Integrations for the connector catalog in depth.
- Security for the public compliance posture.