Overview
Nave is a kanban analytics platform for agile teams. The company has launched AI-powered insights. Nave states that its analytics are used by more than 7,000 agile teams worldwide and names Syngenta, Ramsey Solutions, The Economist, Holcim, Doodle, Nubank and ArcTouch among its customers. Pricing is $100 per board per month or $1,000 per board per year with unlimited users and a 14-day free trial. The platform is SOC 2 compliant as of May 2024 and GDPR compliant. The Kanban Analytics app on the Atlassian Marketplace has more than 1,000 installs and a 4.4 out of 5 rating from 33 reviews. Nave was named Atlassian Marketplace Rising Star Partner of the Year 2026, announced at Team '26 in Anaheim. Its newsletter has more than 60,000 subscribers. The company describes itself as a small team. Founder and CEO Sonya Siderova is based in the Antwerp area; the company's Atlassian Marketplace vendor address is in Sofia, Bulgaria, and its contact phone number is Belgian.
Stated facts & numbers
- Headquarters: Antwerp (founder location); vendor address in Sofia, Bulgaria
- Founder & CEO: Sonya Siderova
- Product: Kanban analytics for Jira, Azure DevOps, Trello, Asana
- Customers: 7,000+ agile teams; Syngenta, Ramsey Solutions, The Economist, Holcim, Doodle, Nubank, ArcTouch
- Pricing: $100 per board per month, unlimited users
- Award: Atlassian Marketplace Rising Star Partner of the Year 2026
- Compliance: SOC 2 (May 2024), GDPR
Leadership & org chart
In the news
- Finishing 26 items in one day can look like exceptional performance. But consider the full dataset: One item finished on 36 days. Two items finished on 22 days. Three items finished on 7 days. Across all days with completions except one, seven or fewer items finished. On the remaining day, 26 items finished. That outlier does not prove the team suddenly had more capacity. It tells you that many items crossed the finish line together. Throughput shows how many items finished during a chosen period. It does not show where those items
- Leadership knows where it wants the organization to go. The people doing the work still face years of accumulated processes, existing commitments and urgent demands. By October, the strategy and the day-to-day system may be pulling in different directions. Matthew Croker sees this conflict often: the organization is active, but business as usual keeps taking over. If your strategy keeps losing to the system meant to deliver it, read the full conversation → https://getnave.co/4ikkNvy #NavigateYourFlow #Kanban #FlowMetrics
- Your team is delivering too slowly. But is the problem really development speed? Take a look at this chart from the Nave flow analytics tool. Only 18% of the total cycle time is spent in Development, while 67% is spent in Ready for Testing and Ready for Deployment. So where would YOU look first? Join The Job Hackers on October 27 as Sonya Siderova, founder and CEO of Nave, walks us through a real-world delivery example and shows how flow metrics can help uncover bottlenecks. 🎁 Bonus for attendees: You'll receive FREE access to
- A metric can remain perfectly stable while delivery gets worse. Resource allocation is a good example. Once a team reaches 100% allocation, the percentage cannot increase any further. It can remain at its ceiling while: - Work in progress grows - Items wait between process states - Current work continues to age - Delivery dates start slipping The report isn’t wrong. It’s simply measuring whether people have work assigned. It isn’t measuring whether that work is moving. Arrival rate, throughput, waiting time and the age of work in
- The dotted vertical lines stretching across the Cycle Time Histogram are called percentile lines. We use percentiles to establish service level agreements and define the probability of meeting our commitments. Using the percentiles on your Cycle Time Histogram, you can perform a probabilistic forecast. Essentially you define a range of cycle times and the probability that comes with each of them. Now, what happens if a customer asks “When will this be done”? Looking into the histogram here, the answer will be “there is a 50/50
- Our leadership can now see the bigger picture that the Asana reports and Azure DevOps dashboards don’t show.” That’s Leonardo Luzzatto at Stoque, where an eleven-person product team needed more than a monthly report to understand delivery. They started looking at aging work every day, reviewing delivered work regularly, and using flow data to make more accurate release-date commitments. What changed when those metrics became part of the team’s decisions? Read the Stoque story → https://getnave.co/3U9ZZ1s #NavigateYourFlow #Kanban
- Your process might look like it’s flowing, but what if hidden debt is quietly dragging it down? In Kanban, flow debt occurs when we prioritize certain tasks by borrowing time from others in progress—often unintentionally. Just like financial debt, flow debt can be useful—but only when managed intentionally. Otherwise, it quietly accumulates and weakens your system’s ability to deliver reliably. Use your Cumulative Flow Diagram and Cycle Time Scatterplot to measure the gap between approximate and actual cycle times. What's the
- There is a little-known practice that can completely transform how your team operates. When you implement this approach, get ready for open dialogue, active listening, and collaboration like you've never experienced before. Just imagine this: you and your team will have the opportunity to give feedback on each other's work, highlighting strengths and areas for improvement. No judgment or blame involved. This practice is all about personal and professional growth, making feedback a natural part of your everyday work. So, my friend,
Something wrong or missing? Send an update. Fixed within 24 hours.