From connected to resolved

NamiFlow is an AI investigation navigator. Nami investigates with your team across connected runbooks, code, and logs, reasons over the evidence, and always leaves a concrete next move — resolution steps you can take now, or one targeted question that unblocks the investigation.

No. NamiFlow is deliberately collaborative, not autonomous. You remain the actor on production changes. Deterministic rules act as guardrails (access boundaries, team communication style, safety). The investigation itself is AI reasoning over your evidence — not silent remediation.

Checkpoint questions are reasoned from the current investigation state — for example an incident time window to scope logs, or a failed request_id to trace a workflow. They are not keyword-matched templates. Each question should be explainable: why that input, and what Nami will do with the answer.

Live connectors today: Confluence (runbooks/docs), Google Drive (shared folders), GitHub (code), CloudWatch (logs), Datadog (log search), and Jira (escalation create + optional comment writeback). You choose which to connect. Other providers shown as coming soon in Connections are not claimed as available yet.

Read access by default. Confluence, Google Drive, GitHub, and Jira connect over OAuth (Drive folder access is a Viewer share to NamiFlow’s reader service account); CloudWatch through a cross-account IAM role you create and can revoke; Datadog via API/app keys you paste. You choose which sources to connect and can disconnect any of them whenever you want. Nami does not deploy code, commit code, edit runbooks, modify logs, or make production changes. Writes exist only for Jira escalation: creating an issue and posting updates/comments to a linked issue — each requires a person to click, never automatic silent writes.

Starter is $20 per user per month. Pro is $49 per user per month. Team plans are Team 15 ($599/mo), Team 40 ($1,499/mo), and Team Unlimited ($2,999/mo) — contact us; there is no self-serve Team checkout. Enterprise is custom — contact us. Investigation packs are 50 for $150. Included investigations are pooled across your team, not siloed per person. New organizations get a 14-day free trial on Starter or Pro (card required). See the live pricing page for volumes and plan details.

An investigation is a thread where Nami actually worked the problem — you describe an incident, she searches your sources and investigates with you. Threads you cancel before Nami begins investigating (for example, while she's still asking clarifying questions) don't count. Once underway it counts whether or not you mark it resolved — and if her clarifying questions alone helped you resolve it, that counts too. Investigation counts are approximate: exceptionally large investigations — a small minority with unusually heavy research volume — may count as more than one. Your plan's included investigations are a shared pool across your whole team, not a per-person allowance.

New investigations pause until you add capacity. An org admin can buy investigation packs — 50 additional investigations for $150 — from Settings → Billing. Optionally enable auto-refill there so a pack is charged to your saved card when the pool runs out; auto-refill is off by default and never charges without that opt-in.

Out of the box today: Confluence, Google Drive, GitHub, CloudWatch, Datadog, and Jira. She indexes connected knowledge, code, and logs so a single question can search across them. Google Drive is shared-folder access (Viewer to NamiFlow’s reader). Jira is used for escalation create and optional comment writeback on linked issues. Connectors marked coming soon in the product (for example Notion or GitLab) are not available yet.

Read access by default. Confluence, Google Drive, GitHub, and Jira connect over OAuth (Drive folders via Viewer share to NamiFlow’s reader); CloudWatch through a cross-account IAM role you create and can revoke; Datadog via API/app keys. You pick which sources to connect and can disconnect any of them at any time. Nami does not deploy code, commit code, edit runbooks, modify logs, or change production. The only writes are Jira escalation actions — create an issue or post an update/comment on a linked issue — and each happens only when a person clicks.

Access is role-based and scoped per team, so members only see the tools and sources they're assigned. Connector credentials are encrypted, and all data is encrypted at rest and in transit. Admins control members, teams, and connected sources from a single dashboard.

Yes. New organizations get a 14-day free trial on Starter or Pro. A credit card is required at signup; you won't be charged until the trial ends. Cancel anytime during the trial and you won't be billed. Existing organizations that already subscribed are not eligible for another trial.

When an investigation escalates, Nami can draft a ticket from your templates. With Jira connected, a person can create the issue in Jira in one click and later post investigation updates as comments on that linked issue. When lifecycle comments are enabled for your org, Nami can also post a brief comment when an escalated investigation is resolved or cancelled. Nami does not change production systems through Jira beyond these ticket writes.

Admins create as many teams as they need and assign members, tools, and a communication style to each. Each team sees only the tools they're given, and Nami answers in that team's style. Investigations can hand off across teams via investigation ID so context isn't lost.

A paid 8-week engagement — $5,000, or $2,500 for small teams — where you run Nami against real production incidents with weekly support from the NamiFlow team. Invoiced upfront, and 100% of the fee is credited toward a 12-month contract if you convert. You pay the annual price and get fourteen months instead of twelve. Limited to three teams at a time and reviewed personally — apply via the contact page. A demo, a workflow discussion, and a historical/sanitized test case are always free; only the 8-week engagement against real environments is paid.