Skip to content

    Sherpa is now Navorda. Read the announcement

    Navorda
    Pricing

    Pricing built around the portfolio you govern

    Navorda pricing scales primarily with the portfolio under governance and the capabilities your organization needs — not simply with the number of people using the platform.

    How Navorda pricing works

    Every energy portfolio operates differently. Navorda deployments are therefore scoped around the projects you need to govern, the capabilities you require and the systems Navorda needs to connect with.

    • 01 — Portfolio

      Projects under governance

      Navorda Platform pricing scales primarily with the number of active projects managed through the platform. Archived projects stay consultable and are not counted.

    • 02 — Capabilities

      The operating model you need

      Extend the core platform with the optional capabilities your teams need, when they need them. Each one extends the same project, portfolio, versioning, counterparty and governance model — nothing is re-entered.

    • 03 — Connectivity

      Your enterprise architecture

      Power BI connectivity, the REST API and enterprise integrations through Navorda Connect are incorporated depending on the systems and data flows involved. The Navorda MCP Connector is included in Navorda Platform.

    • 04 — Deployment

      Implementation requirements

      The commercial scope can also reflect data migration, portfolio configuration, countries and organizational structure, integrations and implementation requirements. Navorda remains a SaaS platform: structured onboarding runs four to eight weeks from kickoff to supported go-live, scoped to the capabilities you start with.

    Active projects

    Active projects are the projects being managed in the system. They are what the commercial scope of Navorda Platform is counted against.

    Archived projects

    Archived projects are non-editable projects that stay in the system to be consulted when needed — terminated projects, projects sold to another corporation. They are not counted.

    Govern the portfolio, not the seats.

    Navorda is designed to connect execution, portfolio management and leadership across the organization. Its commercial model therefore focuses primarily on the portfolio being governed rather than charging for every person who needs access to its information.

    Give the people involved in your projects the visibility they need without designing the operating model around software seats.

    A clear proposal for your deployment

    1. 01

      Portfolio

      Tell us what you are managing.

    2. 02

      Scope

      Identify the Navorda capabilities and integrations your operating model needs.

    3. 03

      Proposal

      Receive a commercial proposal adapted to the deployment.

    See what Navorda Platform includes

    How you buy

    Navorda is an AWS-native platform listed on AWS Marketplace. Your proposal can be transacted there or contracted directly with CabSan.

    • Transact through AWS Marketplace

      Navorda is listed on AWS Marketplace. Procurement, contracting and billing can run through the AWS account you already have, and a private offer is how your tailored proposal is transacted there.

    • It can draw down AWS commitment you already hold

      Eligible AWS Marketplace purchases retire against an organization's committed AWS spend under an Enterprise Discount Program or Private Pricing Agreement. For organizations carrying commitment they are not fully consuming, that turns a new software line item into budget already committed. Eligibility and the share of a commitment that Marketplace spend may retire are set by your agreement with AWS and have changed over time — confirm with your AWS account team.

    • You can contract on standard terms

      The Standard Contract for AWS Marketplace is available if you would rather not negotiate a bespoke agreement, and procurement, contracting and billing run through the AWS account you already have.

    • Or contract with CabSan directly

      If Marketplace does not suit your procurement route, we quote and contract directly. The proposal is the same either way.

    Machine-readable version (pricing.md)

    Pricing questions

    Navorda pricing is based primarily on the portfolio under governance, together with the capabilities, integrations and deployment requirements involved. We define the scope with your team and provide a commercial proposal for your specific deployment. Navorda uses an enterprise commercial model based primarily on the portfolio under governance, required platform capabilities and deployment scope. Pricing is provided through a tailored commercial proposal rather than a public price list. Navorda is transacted on AWS Marketplace through private offers; no public price is published there either.

    Navorda's commercial model is designed around portfolio governance rather than traditional per-seat pricing. The main pricing driver is the scope of the portfolio and capabilities being governed, so the people involved in your projects can have the visibility they need without the operating model being designed around software seats.

    Yes. Navorda is designed to scale as portfolios, countries, technologies and organizational requirements evolve. Commercial scope can be adjusted as the portfolio under governance changes — a project that needs to exist in the system should exist in it, and Navorda does not block work or bill per-project overage as the portfolio grows. Talk to us before a large intake and we will scope the change together.

    Active projects are the projects being managed in the system. They are what the commercial scope of Navorda Platform is counted against. Archived projects are non-editable projects that stay in the system to be consulted when needed — terminated projects, projects sold to another corporation. They are not counted. A portfolio that has developed and sold a hundred projects over a decade is scoped on what it manages today, not on its history.

    Every Navorda deployment starts with Navorda Platform, and no core capability is held back for a larger deployment. Navorda Platform includes projects with configurable attributes and KPIs; milestones for development, permitting and land readiness with templates and dependencies; automatic stage from milestone logic; baselines and deviation control, including committed versus forecast MW per milestone and period; project-to-SPV ownership; relationships between projects and shared infrastructure; embedded reporting; the Navorda Decisions register; and the included read-only MCP Connector for compatible enterprise AI. Specialist depth is optional: Navorda Risks, Navorda Land, Navorda Finance, Navorda Transactions (SPAs and shareholder structures), Navorda Offtake, External Models Governance, Enterprise Integrations, Navorda Connect (Power BI Semantic Model Twin and REST API) and Navorda AI extend the same project model when the organization needs them. Optional capabilities are scoped with the deployment; the MCP Connector is not one of them — it is part of Navorda Platform.

    Yes. Optional add-ons and enterprise connectivity can be activated as the operating model expands across functions, countries and systems, and they extend the same underlying project model: existing projects, milestones and baselines stay in Navorda while the enabled workflows expand. You do not need to deploy every specialist workflow on day one — start with the projects and teams where governance matters most, and the commercial scope follows.

    Implementation is scoped with the deployment — it depends on how many projects and countries you are loading, what you are migrating from, and which integrations are in scope. Structured onboarding runs four to eight weeks from kickoff to supported go-live, and the implementation scope is part of the same commercial proposal.

    Through AWS Marketplace, where Navorda is listed, or directly with CabSan. On Marketplace, a private offer is how your tailored proposal is transacted: procurement, contracting and billing then run through your existing AWS account, and you can contract under the Standard Contract for AWS Marketplace instead of negotiating a bespoke agreement. If you would rather contract directly, contact info@cabsansolutions.com — the proposal is the same either way.

    Often, yes — this is one of the practical reasons to buy through the Marketplace. Eligible AWS Marketplace purchases retire against an organization's committed AWS spend (an Enterprise Discount Program or Private Pricing Agreement commitment), which means budget you have already committed to AWS can cover the software. Eligibility, the share of a commitment that Marketplace purchases may retire, and the rules about where a product runs are all set by your own agreement with AWS and have changed over time. Navorda runs on AWS in Frankfurt, which is the usual technical condition. Confirm the commercial side with your AWS account team before you plan around it.

    No. Proposals are quoted in EUR and exclude VAT and any local taxes that apply to your organization.

    Get a price for your portfolio

    Tell us what you manage and what you want to govern. We will help define the right Navorda deployment and provide a clear commercial proposal. If you are not yet sure how much governance distance you are carrying, start with the assessment — it takes about five minutes and it will tell you what a platform would actually have to fix.

    Take the 5-minute assessment

    Questions about scope or procurement? Read the FAQ