The NexiAct platform

Intelligent operations. Contextual decisions. Governed actions.

NexiAct connects operational signals, enterprise context, AI reasoning and governed execution in one architecture. Every product is built on the same foundation.

Architecture

Five layers, with governance across all of them.

Signals enter through the integration layer, gain meaning in the context layer, are reasoned over by agents, and surface in the products and experiences your teams use. Governance and security apply at every layer.

ExperienceHow people work
Unified portalOperational dashboardsInvestigationsChatOpsApprovals
Domain productsWhat teams use
NexiOpsNexiGraphnexiGaurdNexiCVM
Agentic intelligenceHow decisions are made
ReasoningEvidence retrievalToolsWorkflow enginePolicy decisionsHuman in the loop
Context and knowledgeWhat the agents know
GraphCMDBTopologyHistorical incidentsChangesRunbooksCVEs
IntegrationWhere signals come from
ObservabilityITSMCloudCI/CDCode repositoriesSchedulersSecurityIdentity
Governance & security
How data and actions flow

Open ingestion. Grounded reasoning. Controlled execution.

APIs and webhooks

Signals, incidents and changes arrive through REST APIs and webhooks from the tools you run.

Connectors

Connectors for common observability, ITSM, cloud, scheduler and source code repository platforms, confirmed with each design partner.

OpenTelemetry

Native ingestion of OpenTelemetry metrics, logs and traces.

MCP tool access

Agents call approved tools through the Model Context Protocol, limited to an allowlist per role.

Retrieval grounding

Agents retrieve facts from NexiGraph and your knowledge sources and cite them in every recommendation.

Policy-based execution

Every action is checked against policy before it runs, and routed for approval when required.

Integration status

We distinguish supported, pilot and planned integrations. Vendor names are not shown, and no endorsement is implied.

CategoryStatus
ObservabilitySupported via OpenTelemetry, APIs and webhooks
ITSMPilot connectors with design partners
CMDBPilot connectors with design partners
Cloud providersPilot connectors with design partners
Job schedulersPilot connectors with design partners
ChatOpsPilot connectors with design partners
Source code repositoriesPlanned
CI/CDPlanned
Security and identityPlanned
Governance model

You set how far agents may go.

Autonomy is a policy, set per action type and environment. Pick a level to see what the agent and your team each do in the same scenario.

Scenario
pg-cluster-03 is filling up at 2.1% per hour.
Agent
Opens CHG-20418, asks the on-call DBA in Slack, and runs the fix once approved.
Your team
Approves with one click.
Security foundations

Security is foundational, not a feature.

These controls describe how the platform is designed. Formal certifications are not claimed; ask us about the current state of any control.

Least privilege

People and agents get the minimum access their role needs.

Tool allowlists

Agents can call only the tools explicitly allowed for their task.

Approval gates

Human approval for any action class you choose.

Secrets handling

Credentials stay in a vault and are never exposed to model prompts.

Tenant isolation

Customer data is designed to be isolated per tenant.

Data minimization

Only the data an agent needs is retrieved for each task.

Logging

Recommendations, approvals and actions are logged with their evidence.

Rollback

Actions carry a rollback plan and post-action verification.

Review the architecture with our team.

We'll walk your architects and security team through the platform and how it would connect to your environment.