FAQ
Questions about Nave, answered.
Find answers about how Nave works, data and integrations, pricing, security, forecasting, AI, and getting started.
Getting Started
What is Nave?
Nave is a flow analytics platform for software delivery teams. It connects to the tools where your work already lives and turns delivery history into flow metrics, process insights and probabilistic forecasts.
Who is Nave for?
Nave is for teams managing delivery in Jira, Azure DevOps, Trello or Asana. It also gives delivery leaders visibility across multiple teams and helps transformation leaders understand performance across services and portfolios.
Do we need to change how our teams work to use Nave?
No. Nave analyzes the workflow and delivery data your teams already have, so you do not move work into Nave or adopt a new project management tool.
Do we need to use Kanban?
No. Scrum teams can use flow metrics and Kanban practices because Scrum and Kanban are not necessarily mutually exclusive.
How do we get started?
Start a 14-day free trial, connect your existing delivery tool, and choose the board you want to analyze. Nave uses the workflow and historical delivery data already in your tool, so you don't need to migrate your work or change how your team works.
Can I try Nave with my own data before buying?
Yes. The 14-day trial connects to your real tool and loads the delivery history from one of your own boards, so you can evaluate Nave using your team's actual data before buying. Every feature is included and no credit card is required.
Is there a free trial?
Yes. The free trial lasts 14 days, includes every feature and does not require a credit card. When it ends, you cannot access Nave until you subscribe, and your data is kept for three months.
Data & Integrations
What tools does Nave integrate with?
Nave integrates directly with Jira Cloud, Jira Server and Data Center, Azure DevOps, Trello and Asana. For another system, you can upload CSV or JSON files or automate uploads with the Nave API.
Do we have to move our data into Nave?
No. You connect the tool you already use, sign in with that tool's login and authorize access, so Nave never has access to your password. Nave syncs the details its charts need, such as IDs, titles, dates and status history. It never creates, changes or deletes your work items, comments, boards or projects.
Can we use Nave if our tool isn't directly integrated?
Yes. If your tool isn't directly integrated with Nave, you can import delivery data using CSV or JSON. Uploads can also be automated through the Nave API.
Can we anonymize the data?
Yes, Nave provides several ways to limit or anonymize the data it receives.
- Nave can work with only item IDs and timestamps. In a CSV, you can leave the Name values empty.
- On Jira and File dashboards, you can choose not to store task names when creating the dashboard. Once enabled, no user in the account can change this setting.
- On Jira and File dashboards, all person-related fields, including assignees, reporters, and custom user fields, can be hidden. Contact Nave to enable this option.
- An open-source uploader built by a Nave customer anonymizes Jira data before uploading it.
Can one Service contain teams from different tools?
Yes. One Nave account can hold teams using Jira, Azure DevOps, Trello and Asana. A Service brings together the teams delivering a product or service, including teams working in different tools.
How much historical data does Nave need?
Nave works with the history your tool already has. A new dashboard loads recent history by default, which is the last three months of completed work for most integrations, and fetches older work when you select an earlier date range. The Process Improvement dashboard needs at least four data points and uses the last three months, while forecasts use the history window you select.
How often does Nave sync?
Jira Cloud, Trello and Asana dashboards update as work changes through a webhook. Jira Server and Data Center also use a webhook when Jira admin rights are available; otherwise, Nave syncs every 30 minutes. Azure DevOps syncs every 30 minutes.
Metrics
What metrics does Nave calculate?
Nave calculates four core flow metrics: work in progress, cycle time, throughput and work item age. It also measures flow efficiency, blocked time and cycle time per process step.
How does Nave calculate cycle time?
Cycle time is the time between the defined start and end points of your workflow. It runs from when work enters the stages mapped as in progress until it is done.
Does Nave use averages?
Nave shows the full distribution of how long work took, with percentile lines such as 50%, 85% and 95%. An 85th percentile of 22 days means 85 of every 100 completed items finished within 22 days. Averages hide this variation because work does not all take the same amount of time.
What is an SLE?
An SLE is a service level expectation that states how long work usually takes based on historical cycle-time percentiles. For example, it might show that 85% of work finishes within 22 days rather than assuming every item takes the average.
Does Nave support story points?
Nave does not need story points. Its flow metrics and forecasts use completed work and its dates rather than estimates.
Do we need estimates to use Nave?
No. Flow analytics and probabilistic forecasting use historical delivery data rather than item-level estimates.
Can Nave compare teams?
Yes. Nave can show teams together in Services, Portfolios and Executive Dashboards, and compare each team's current period with its earlier periods. Performance should be read against each team's own delivery history, not used as a ranking, because teams handle different kinds of work.
Forecasting
What does Nave forecast?
Nave forecasts how much work you can finish by a given date or when you are likely to finish a given amount of work. Each answer includes confidence levels.
How does Monte Carlo forecasting work?
Nave counts the work items completed each day in the selected history window, including days with no completions. By default, it runs 10,000 trials that draw random days from that history to simulate possible outcomes. The results form a probability distribution of dates or amounts of work.
Does forecasting require story points or estimates?
No. Forecasts come from what the team has actually completed, not from story points or estimates of how long the remaining work might take.
What do 50%, 70%, 85% and 95% confidence levels mean?
An 85% forecast means the work finished by that date in 85% of the simulated cases. For the same work, an earlier date has lower confidence and a later date has higher confidence. Higher confidence requires more time or a smaller commitment, so you choose how much risk to accept.
Does Nave give me one guaranteed delivery date?
No. A single date would hide the uncertainty in delivery. Nave shows dates by confidence level so you can choose a commitment that matches the risk you can accept.
How often are forecasts updated?
The Continuous Forecasting dashboard recalculates forecasts daily as items finish. It keeps the original target date fixed and shows whether that target remains likely while there is still time to act.
How much historical data do I need for forecasting?
Forecasts use the throughput history window you select. A period when the delivery system behaved predictably provides a stronger basis, and the Process Improvement dashboard shows whether it did.
AI
What does AI do in Nave?
Nave's AI Investigator reads your computed flow metrics, identifies the stage and work items behind a problem, and shows you the evidence so you can decide where to intervene. It works on one team dashboard at a time.
Does AI calculate my delivery metrics?
No. Nave computes the flow metrics before the AI receives anything, and the AI only reads those results. Swapping the model does not change the numbers.
Does AI decide whether something is a delivery problem?
No. Delivery signals come from deterministic calculations on your data using natural process limits. The AI investigates the evidence Nave has already computed.
Can the AI return no finding?
Yes. If the computed data does not support a finding, the Investigator returns none and the panel says "No insights available."
What data is sent to the AI model?
The AI model receives computed metrics, stage statistics and the items in each stage. Item IDs are pseudonymized by one-way hashing, and item names, URLs and descriptions are never sent to the AI provider.
Is our data used to train AI models?
No. Nave does not train or fine-tune AI models on customer data. AI providers are used through their APIs for inference only.
Which AI model does Nave use?
Nave uses Anthropic and OpenAI through their APIs. It does not name a specific model or version because the underlying model can change without changing the numbers.
Enterprise & Security
Where is Nave hosted, and where is our data stored?
Nave runs on Google Cloud Platform in the EU. Data is stored in the europe-west region.
Is Nave SOC 2 compliant?
Yes. Nave has completed a SOC 2 Type II examination and supports GDPR compliance. Security documentation is available on request.
Does Nave support SSO?
Nave has no separate login or SAML setup to configure. Users sign in through the connected tool, using their Atlassian account for Jira or Microsoft Entra for Azure DevOps, so your existing SSO and MFA policies apply to Nave.
What permissions does Nave need?
Nave works with the connecting user's own access, so it only sees what that account can see. For Jira Server and Data Center, a Jira administrator links Nave once. Updates as work changes require Jira admin rights; without them, Nave syncs every 30 minutes.
Does Nave write anything back to Jira or Azure DevOps?
Nave never creates, changes, or deletes your work items, comments, boards, or projects. In Jira, it registers a webhook that tells Nave when work changes, so your charts stay current. It also registers a webhook in Trello and Asana, but adds nothing in Azure DevOps.
What data does Nave access?
For Jira, Nave keeps the connected board's ID, name and columns, along with issue keys, summaries, priorities, created dates, due dates and links. It also keeps status changes and their dates, blocked or flagged periods, selected custom fields, and assignee display names and avatars unless person-related fields are hidden. Nave uses your display name and email address to sign you in, and other tools follow the same pattern.
Does Nave support Jira Data Center?
Yes. Nave works with Jira Cloud, Jira Server and Data Center. The instance must be reachable from the internet; otherwise, you can upload your data and automate uploads with the Nave API. Nave is also available on the Atlassian Marketplace.
Can Nave support security and vendor assessments?
Yes. Nave's team supports security reviews, vendor onboarding and procurement documentation. Security documentation is available on request.
Do you have a DPA?
Yes. Nave publishes its Data Processing Agreement.
Who are Nave's sub-processors?
Nave's current sub-processors are listed in section 4.6 of the Data Processing Agreement. Nave notifies users of intended changes.
Pricing
How is Nave priced?
Nave is priced per board, not per user. A board can be a Jira board, an Azure DevOps board, a Trello board or an Asana project. Every feature is included.
Are users unlimited?
Yes. Every subscription includes unlimited users with no per-seat fees.
How much does Nave cost?
Nave costs USD 100 per board per month or USD 1,000 per board per year. Paying monthly for a year would cost USD 1,200 per board.
Do you offer volume discounts?
Yes, for subscriptions of 250 boards or more. Standard pricing applies below 250 boards.
Can we pay by invoice or bank transfer?
Yes, annual subscriptions can be paid by invoice or bank transfer with a 30-day payment term. Invoices are sent to your billing email and are also available on your Billing page.
Can we pay monthly?
Yes. Monthly subscriptions can be paid by Visa, Mastercard or American Express. All prices are in USD.
Can we get a quote?
Yes. Contact Nave with the number of boards you need.
Teams & Scale
Can Nave support hundreds of teams?
Yes. Nubank's Global Productivity Team uses Nave across more than 200 teams.
How do we organize many teams?
Team dashboards roll up into Services, which bring together the teams delivering a product or service, even across tools. Services then roll up into Portfolios.
Can leadership see performance without opening every team dashboard?
Yes. Executive Dashboards show cycle time, throughput, work in progress, flow efficiency and predictability across teams and services. They also compare performance over time.
Can different teams keep different workflow configurations?
Yes. Each team dashboard maps its own board and workflow stages. Services bring those teams together without reorganizing the tools underneath them.
No questions match your search. Try another word or browse the sections.