Features

Everything an incident needs, in one navigator

Nami combines search and reasoning with your team, so you go from alert to answer without switching tools or losing context.

Investigation Chat

Ask Nami questions in natural language. She searches your connected runbooks, repos, and logs — then reasons through the problem like an experienced specialist on that team.

Tool Catalog

Upload custom Python tools your team already uses. Nami surfaces the right one during an investigation and runs it when you click Run — never on her own.

Admin Dashboard

See every investigation across your org. Track usage, resolution rates, and identify knowledge gaps that need runbooks.

Knowledge Improvement

When Nami finds a knowledge gap, she drafts the missing runbook or tool for you to review and publish. Your team's investigations make the system smarter over time.

Capabilities

Go deeper on how Nami works

Every feature is built to keep context in one place and move investigations forward — from the first question to the final runbook.

Unified search across your stack

Nami indexes your connected runbooks, source code, and logs so a single question searches everything at once — no more tab-switching during an incident.

Team-based communication styles

Create teams with the communication style each needs. For example, ops can get plain language while engineering gets deeper technical detail — and you can define as many teams and styles as your org needs. Each team sees only their tools.

Escalation ticket drafting

When an incident needs to move up, Nami drafts a complete ticket with context, timeline, and suggested next steps from custom templates you define.

Tool runs you approve

Custom Python tools run inside the investigation, but only when a person clicks Run. Nami surfaces the right tool for the moment, you review the inputs, and the output lands in the conversation.

Knowledge base indexing

Connect your sources once and Nami keeps them fresh. New docs, commits, and log streams are indexed automatically as your systems evolve.

Role-based access & admin controls

Admins manage members, teams, and connected sources from a single dashboard with full visibility into every investigation.

Spend & usage analytics

Track investigation volume, resolution rates, and per-team activity from the admin dashboard so you know how the team is using Nami.

Auto-generated SOPs

Every resolved incident becomes institutional knowledge. Nami drafts runbooks from real investigations so the next person moves faster.

Cross-team investigation handoff

For example: ops starts an investigation, Nami escalates with a ticket containing the investigation ID, and another team picks it up by pasting the ID — Nami resumes with full context. No knowledge lost between teams.

Answers in their language

One investigation, tuned for every team

Create as many teams as you like — each with its own communication style. These are examples; yours can be named and tuned however you need.

OpsPlain English

The checkout service is slow because a recent deploy shrank the database connection pool. Rolling it back should restore normal speed.

DevCode & SQL

pool_size dropped 40 → 8 in a1f9c2e. Revert the config or set DB_POOL_SIZE=40. Query below confirms connection wait spikes.

SupportBalanced guidance

Checkout may feel slow for some customers. Engineering has identified the cause and is deploying a fix — no action needed from customers.

Included

Built for real production environments

Natural-language investigation chat
Confluence, Google Drive, GitHub, CloudWatch, Datadog & Jira connectors
Custom Python tool catalog
Tool runs you approve
Role-based team access
Escalation ticket templates + Jira writeback
Admin dashboard & usage analytics
Drafted SOPs from real investigations
Knowledge-gap detection

Ready to resolve incidents faster?

Start a 14-day free trial with your team and see Nami investigate on your real production stack.