Identity and applications
- Manage organizations and identity
- Govern application versions and visibility
All products
NexusAI AtlasNexusAI
Give AI use a clear boundary.
The governance layer for managing identity, organizations, model access, application use, quotas and audit records.
NexusAI AtlasProduct responsibilities
Product responsibilities
Enterprise AI governance
01 / Product overview
The work this product is responsible for.
NexusAI Atlas brings organizational identity, application access, model use and cost records into a governance scope for enterprise IT, platform administrators and governance teams. Teams can define who may use which AI capabilities, under which policies and limits, then review application versions, requests, bills and audits to adjust their enterprise rules.
Who it is for
- Enterprise IT and platform teams
- Organization and application administrators
- AI governance teams
Inputs & context
Users, organizations, applications and model requests
Outputs & deliverables
Access decisions, usage limits and audit records
Its role in the ecosystem
Define enterprise AI access, rules and costs
NexusAI Atlas governs organizational identity, application access, model policies and cost records. Administrators manage access and cost budgets, then use application versions, requests, Token usage, bills and audit records to review AI use.
From organizational rules to traceable use
- 01
Establish identity and access
Maintain members, departments and roles; define application versions, visibility and model access to connect.
- 02
Apply model and governance rules
Configure model admission, routing, content policies and cost budgets for connected requests.
NexusAI Atlas - 03
Review records and adjust
Use requests, Token usage, bills, cost allocation and audit records to adjust access and cost rules.
Core capabilities
Models and runtime policies
- Configure model admission and routing
- Apply content and runtime policies
Costs and usage traceability
- Manage quotas and usage costs
- Trace requests and administrative activity
Product relationships
Atlas governs connected applications and model access, supplies identity and organization information to OS, and governs model requests from Runtime and from OpenFlux in Atlas-managed mode.
Governance serviceNexusAI Studio
Govern NexusAI application and model use
Atlas manages access, version visibility and model invocation rules for NexusAI applications within its governance scope. NexusAI continues to run the Agents and workflows.
Capabilities & deliverables involvedAccess decisions, model policies, quotas and audits
Governance serviceNexusAI OS
Provide identity and organization information to OS
OS uses Atlas users and organizational structure to place tasks, people and responsibilities in context. OS manages goals, business processes and project progress.
Capabilities & deliverables involvedUsers, departments and organizational scope
Governance serviceOpenFlux Runtime
Govern Runtime model requests
OpenFlux Runtime model requests pass through the enterprise gateway, where Atlas applies model access policies, cost budgets and audit rules for the organization its account belongs to. Runtime stores no model provider keys.
Capabilities & deliverables involvedModel requests, usage and audit records
Governance serviceOpenFlux
Govern Atlas-managed OpenFlux model requests
Only in Atlas-managed mode does OpenFlux send model requests through the enterprise gateway, where Atlas applies model access, policy, quota and audit rules.
Capabilities & deliverables involvedManaged model requests, usage and governance records
02 / Core capabilities
What you can do.
Manage organizations and identity
Maintain the organization tree, members and roles. Assign users to teams and departments, and manage application access and available capabilities within organizational permissions and scope.
- Organization trees, members and roles
- Organizational scope and access permissions
Govern application versions and visibility
Manage application registration, version review, publication and visibility. Administrators can see which applications are available to which teams and which versions they use.
- Application review and versions
- Team visibility and usage scope
Configure model admission and routing
Manage model providers, allowed models and request routes. Process model requests through a governed gateway so model selection follows enterprise rules.
- Model admission and routing
- A governed model gateway
Apply content and runtime policies
Configure model invocation and content safety policies. Apply the relevant rules to requests and inspect policy matches and handling records to review runtime behavior.
- Content safety and runtime rules
- Policy matches and handling records
Manage quotas and usage costs
Set cost budgets and review Token usage, bills and internal allocation. Manage AI resource budgets alongside actual consumption and spending.
- Cost budgets and Token usage
- Billing and cost allocation
Trace requests and administrative activity
Review model requests, application use, risk events and administrator actions. Combine usage and cost information to trace how enterprise AI is used and managed.
- Request and application usage audits
- Risk events and administrator actions
03 / Use cases
Start with these tasks.
Make AI applications available by team
Organize members and roles, review application versions and configure visibility by department and intended usage scope.
What you get
Defined application access, corresponding versions and management records.
Set common model usage rules
Configure allowed providers, models, request policies and limits. Process requests connected to the governance chain through a common gateway.
What you get
Model access governed by enterprise rules, with usage and policy records.
Review AI spending and responsibility
Use request audits, application activity and cost allocation to understand organizational consumption. Identify where limits, access or policies need adjustment.
What you get
Cost and audit records that can be associated with organizations, applications and model use.
04 / How it works
From inputs to results.
- 01
Establish organizations and access
Configure departments, members and roles. Identify the applications to govern and their intended usage scope.
- 02
Set model and governance rules
Define model admission, routes, content policies and resource limits, then connect the relevant usage to the governance chain.
- 03
Review records and adjust rules
Review applications, requests, usage and cost records. Adjust permissions, limits and policies based on actual use.
05 / Scope & combinations
A clear scope for use.
A defined governance connection
Atlas governs the applications and model usage connected to it. OpenFlux Runtime model requests pass through the enterprise gateway, as do OpenFlux requests in Atlas-managed mode.
Identity and organizations support collaboration
OS uses Atlas users and organization information when arranging work. OS coordinates assignments, human decisions and project progress.
Governance and execution have separate roles
Atlas manages application access, policies, quotas and audits. NexusAI, OpenFlux and the relevant applications execute the business tasks.
CONTINUE EXPLORING
Place this capability in your own work.
Review the wider architecture, or bring this product into a conversation about your team and systems.
Current productNexusAI AtlasEnterprise AI governance