Navorda, in plain English

Navorda is the operating platform for energy project development and portfolio governance. It keeps execution and management connected as energy developers scale, through one governed project reality. It is development governance for energy developers, EPCs, infrastructure funds and IPPs. As portfolios grow, the distance between the people executing projects and the people governing the portfolio grows with them: information climbs from field to management late and summarized, and decisions and accountability dilute on the way back down. Navorda closes that distance by keeping permits, land, milestones, risks, shareholder structures, offtake agreements, project finance and portfolio performance connected in one governed system — so schedule deviations surface before they hit COD, not after. The spreadsheets, GIS exports and email threads it absorbs are the symptom; the governance gap is the problem it solves. The day-to-day value is operational relief from week one.

Navorda reduces the growing distance between project execution and management as energy portfolios scale. The problem is governance, not spreadsheets. Growth increases the distance between the people executing projects and the people making portfolio decisions: information climbs an ever-longer chain — field, department, project, portfolio, country, management — and gets delayed, summarized or lost, while decisions and accountability dilute traveling back down. More meetings and reporting templates store information; they do not govern the business. Navorda creates a governed information flow in both directions: when reality changes at project level it becomes visible upstream without waiting for the monthly report, and when management sets a baseline or assigns responsibility, that commitment stays connected downstream to the projects, milestones and people expected to execute it. Excel fragmentation is the symptom Navorda removes along the way — the full argument is at navorda.com/blog/what-got-you-here-wont-get-you-there.

By maintaining one governed project reality that connects the critical facts, relationships, ownership, dependencies and commitments of energy development — projects, land, permits, milestones, dependencies, risks, SPVs and ownership, transactions, offtake, finance, external models, baselines and reporting. Reality travels upstream: when a permit, milestone, risk or commitment changes in execution, the change is visible to management without a reporting chain rebuilding it. Decisions and accountability travel downstream: priorities, targets, baselines and mitigation actions stay connected to the people responsible for executing them. Not every activity has to happen inside Navorda; Navorda governs the relationships, provenance, ownership and corporate context that matter.

Not primarily. Navorda is the operating and governance layer connecting project execution with portfolio and management decisions. A project-management tool tracks tasks and dates inside a project; Navorda governs the project reality the organization shares — permits, milestones, dependencies, risks, ownership, commitments and their history — so that the same record serves the Project Manager, the Head of Development, the COO and the enterprise systems and AI that read it. It does not replace every existing tool: it governs what matters, integrates what works and replaces only what needs replacing.

Not necessarily. Excel is often a symptom rather than the root problem: spreadsheets, presentations and manual reporting are the mechanisms organizations build to compensate for the distance between execution and management. Navorda replaces spreadsheet-based governance where appropriate, preserves what execution users value about Excel — structured imports and exports, spreadsheet-style grids, bulk operations and reusable templates — and governs specialist external models through External Models Governance when a workbook remains the right calculation engine. The question is not whether Excel should disappear; it is what the operating model needs to govern.

The governance layer is the operating context connecting specialist execution tools with portfolio and management decisions. It governs the relationships that matter across them — which permit gates which milestone, which risk threatens it, who owns the project SPV, which commitment depends on delivery, which model version produced a governed figure — without requiring every specialist activity to move into one application. Land software, GIS, ERPs, financial models and BI keep doing what they do; Navorda keeps their project reality connected and governed.

Energy developers managing land and permitting workflows; EPC contractors coordinating multi-project construction programmes; infrastructure investment funds and IPPs that need portfolio-wide visibility; and data-center operators and their energy teams developing the private power generation and grid infrastructure that supplies their campuses. Inside those organizations, Navorda is built around five roles — Project Managers, Heads of Development and Construction, COOs and C-level, CFOs and Finance leaders, and CTOs — each of which gets a different value from the same governed project reality; see the five role questions below.

Enter it once, use it yourself, trust what gets reported. Navorda helps Project Managers maintain project information once, use that same information for their own daily management and trust that management reporting is built from the same governed project reality. Country- and technology-specific templates, structured Excel imports and exports, spreadsheet-style interfaces and bulk operations reduce the effort required to keep information current. Ownership, history and provenance remain attached to changes, so project reality does not need to be manually reconstructed as it moves upstream. Full page: navorda.com/roles/project-managers.

Keep commitments explicit across teams — ownership, deadlines, dependencies and change. Navorda keeps who owns what, and by when, on the same governed record for every project, so commitments do not disappear between teams, countries and functions. Ownership, risks, dependencies, mitigation actions, changes and commitments remain connected to the projects they affect, which also makes the work of development and construction teams visible beyond final milestone status: functional leaders can show how their teams are actively governing outcomes and where management intervention is required. Full page: navorda.com/roles/development-construction-heads.

Manage from governed project reality instead of reconstructed reporting. Navorda helps C-level stay closer to project reality as the organization scales: instead of relying exclusively on periodically reconstructed portfolio reports, management works from governed context connecting projects, milestones, permits, risks, dependencies, ownership, finance and commitments — the same record execution teams maintain. The objective is earlier awareness of deviations, the context behind every change, less reconstruction of reality and faster, better-informed decision-making. Full page: navorda.com/roles/coo.

Bring governed project information into financial forecasts and capital decisions. Navorda connects governed project information with financial context, helping CFOs understand the operational events behind forecasts, procurement commitments, funding requirements and investment decisions. Your financial systems keep the numbers; Navorda keeps the operational reality behind them connected to the project, the milestone and the version that explain them — so Finance exercises its judgment on better information, not on a reconstructed status. Full page: navorda.com/roles/cfo.

Stop rebuilding the business in software. Navorda gives technology leaders a governed operating model for energy development, so the organization does not need another cycle of custom applications, data pipelines and reporting infrastructure built to reconstruct what is happening across the portfolio. Business change is absorbed through per-tenant configuration rather than a new build; Navorda Connect carries the governed project reality into Power BI, the data platform and enterprise systems; the Navorda MCP Connector gives the organization's own enterprise AI the same context read-only. ERP, treasury and specialist systems stay authoritative for their domains. The technology team spends less effort maintaining commodity project-development infrastructure and more on architecture, security, integration and the capabilities that genuinely differentiate the company. Full page: navorda.com/roles/cto.

Solar, wind, BESS (battery energy storage), hydrogen, data center power, and other large-scale energy infrastructure across multiple geographies.

No — Navorda manages the energy project development layer behind them. For data-center campuses that depend on dedicated or behind-the-meter power, Navorda governs the development of the generation, storage, grid infrastructure, land and permits those campuses rely on — the power projects, not the compute, cooling or data-center construction itself. See navorda.com/data-center-power-development-software for the full picture.

Navorda is built for European multi-country portfolios — 300+ projects managed across 14+ European countries. Permitting processes are modelled per country and technology, so each jurisdiction's chain — Spain's DIA and AAI with grid access and connection permits, Italy's Autorizzazione Unica, and so on — is tracked against its own approved baselines instead of being forced into one generic pipeline. Spanish cadastral data gets first-class treatment: Catastro GML files are parsed natively on import, no GIS analyst required. Navorda is not limited to Europe, but European land and permitting workflows are where it is deepest today.

Navorda is purpose-built for energy project development. It speaks the grammar your team already speaks — plots, permits, baselines, counterparts, SPVs — with cadastral mapping, schedule control against approved baselines, measurable risk exposure, and structured SPA management built in. Generic PM tools force you to bend their data model around a domain they weren't designed for; Navorda was designed for it.

The category splits in two: land systems (Quorum On Demand Land, Pandell, IFS Land for Renewables, Gridlync) treat the agreement as the primary object, while execution platforms (Sitetracker, Matidor) treat the site as the primary object. Navorda is a development platform — the project is the primary object, covering land, permitting baselines, quantified risk and ownership together, built for European multi-country portfolios. We maintain honest side-by-side comparisons, including when each alternative is the better choice, at navorda.com/compare.

Yes. Navorda AI — the optional intelligence add-on that runs inside Navorda — are seven agents that continuously read the governed data your teams already manage in Navorda: projects, milestones, permits, land agreements, risks and ownership structures. They surface missing or stale data, contradictory records, schedule slippage, risks threatening milestones, and financial exposure, and propose mitigation steps. There is no extra reporting layer and no chatbot to babysit — the agents work because the operating model feeds them real context: the relationships between milestones, permits, land, risks and ownership, not just rows of data.

Yes. The Navorda MCP Connector — powered by Navorda's native MCP (Model Context Protocol) server for renewable energy project development — lets Claude, ChatGPT, Cursor, or any MCP-compatible enterprise AI query your workspace directly: development funnel, projects, milestones, land contracts, SPAs, risks and exposure (never Finance or offtake data), live from your single source of truth. It is permanently read-only (no write tools exist and a server-side lock rejects any mutation), disabled per organization until an admin enables it, secured with standard OAuth 2.1 per user, and landowner contact data is structurally excluded from every response. It is how external AI systems get your organization's real operating context. Navorda AI runs separately, inside Navorda on AWS Bedrock in-region (EU), so your data is never sent to a third-party AI service over the public internet. See the Navorda MCP Connector product page for details.

No. Navorda AI is Navorda's own intelligence, running inside Navorda: continuous monitoring and embedded insight in the Navorda UI, operated by Navorda. The Navorda MCP Connector, included in Navorda Platform, is enterprise AI access: your organization's own MCP-compatible AI — ChatGPT, Claude or another client — consuming Navorda's governed data, relationships and operating context. Same operational truth, two ways to use AI.

No. The REST API is part of Navorda Connect, an optional product, and is for application and system integration: programmatic access to supported resources behind governed authentication. The Navorda MCP Connector, included in Navorda Platform, is AI-oriented access to curated Navorda context and purpose-built analytical capabilities. Systems consume Navorda data through Connect; AI consumes Navorda context through MCP.

No. Navorda Platform governs the operational source and ships its own embedded reporting. Navorda Connect can make the same governed model available to your Power BI environment through its Semantic Model Twin, so corporate dashboards use the same operational truth as Navorda.

AI models are becoming extraordinarily capable, but inside organizations, intelligence without context has limited value. To understand whether a project is genuinely at risk, an AI needs more than documents or database access — it needs the relationships between milestones, baselines, permits, dependencies, responsibilities, risks, ownership and historical decisions. That is what an operating model provides: it becomes the context layer for AI. Navorda combines governed operational data, configurable AI agents and MCP connectivity so both internal and external AI systems can work with the organization's real operating context. Models will evolve and interfaces will change; the durable asset is the organization's context.

For most day-to-day plot and contract work, yes. Navorda includes a native geospatial stack with PostGIS, MapLibre, and Catastro/GML parsing, with contract-linked map layers built in. Specialised GIS analysis can still happen in dedicated tools when needed.

Both live in Navorda Transactions, an optional add-on: shareholder structures — SPVs up to holding companies, equity shares, voting rights, entry/exit dates, multi-level relationships — and the Sales and Purchase Agreements, acquisitions and disposals that change them, from screening through signing and closing. Navorda Platform itself links each project to the SPV that owns it. When a transaction closes, the ownership change is written into the structure the add-on governs.

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. Every add-on extends the same project record: existing projects, milestones and baselines stay where they are when a module is activated, and there is no separate edition — Navorda Platform is the one core product.

Navorda has one common platform with optional specialist add-ons. It is not a collection of disconnected applications: every add-on extends the same project, portfolio, versioning, counterparty and governance model.

Project milestone, dependency and baseline information is included, so a slipped milestone is visible without any add-on. Dedicated risk registers, scoring, mitigation tracking and quantified time-at-risk and cost-at-risk are available through Navorda Risks, an optional add-on that extends the same project record.

Navorda Platform treats permits like any other milestone: each permit milestone carries its date — in the past or in the future — a comment, and who created or last changed it and when, with templates and dependencies around it, and the project stage is derived from them. There is no separate permit register; the milestones are the register. Specialist land parcel, contract, landowner and geospatial processes require Navorda Land.

Yes. Navorda Platform captures metrics as direct input on each project — MW is one; your organization can add its own, such as square metres per MW — and calculates KPIs from Platform data, such as the latest permit date. A KPI whose raw material lives in an add-on needs that add-on: the secured-area percentage, computed from parcels and contracts, comes with Navorda Land.

Yes, and it is one of the platform's strengths. For a milestone and a period, Navorda Platform shows the MW committed in the locked baseline against the MW now forecast, the difference, and the projects and milestones behind it — who owns each one and which decision, if any, was recorded about it. The reason is whatever the team wrote down; Navorda keeps the context, it does not invent it.

The land-readiness milestone is. Navorda Platform tracks land readiness as a milestone with status, owner, expected and actual dates, like any other development milestone. Which parcels are secured, by which instrument, with which landowner and under which contract, the secured-area KPI and where those parcels are on the map belong to Navorda Land. Platform knows whether land is secured. Navorda Land manages how it gets secured.

Navorda Platform associates each project with its owning SPV. Shareholder structures — HoldCo relationships, shareholders, ownership percentages, cap tables and the ownership hierarchy — are part of Navorda Transactions, the optional add-on that also manages the SPAs that change them. Activating it later extends the record you already maintain.

Yes. The Navorda MCP Connector is part of Navorda Platform for authorized, read-only access to supported Platform information from compatible enterprise AI clients. Permissions, supported tools and organizational configuration determine what each user can access: the connector is off until an admin enables it, every user authorizes their own client, and tools over add-on data return results only where that add-on is licensed.

No. MCP lets your own compatible AI access authorized Navorda context. Navorda AI — Navorda's embedded agents, running inside Navorda — is an optional intelligence add-on. A Platform customer can use their own AI through the MCP Connector without buying Navorda AI.

No. Native reporting is included in Navorda Platform, and so is the read-only MCP Connector. The Power BI Semantic Model Twin, the REST API and Enterprise Integrations are optional enterprise-connectivity capabilities under Navorda Connect.

Yes. Navorda Platform is designed to start with the projects and milestones the organization needs to govern and to expand as requirements grow — bring your existing project list, set your milestone templates, lock a first baseline. Actual onboarding, contract scope and active-project limits depend on the agreed subscription.

Yes. Add-ons extend the same underlying project model. Existing projects, milestones and baselines remain in Navorda while the enabled workflows expand, subject to deployment details — nothing is re-entered or migrated to a second system.

Yes. Navorda records every offtake agreement against the project that generates the power — physical and corporate PPAs, virtual PPAs and CfDs, private wire, behind-the-meter, tolling, route-to-market and green-attribute sales, with the list configurable per customer. Commercial terms (contracted capacity, annual volume, strike and floor price, tenor, pricing structure, indexation, currency), delivery terms (delivery point, green attributes, balancing responsibility) and credit and legal terms (credit support, conditions precedent, longstop date, change-in-law protection, termination rights) are structured fields rather than prose in a contract folder, and the agreement stage is calculated from the milestone dates recorded rather than typed by a user.

No. Asset management software monitors operating plants — SCADA data, availability, O&M, production and revenue. Navorda governs the project, ownership and commitment layer of the portfolio: development and construction baselines, quantified risk, SPVs and transactions, and offtake commitments against the supplying projects. A project does not leave Navorda at COD — its ownership, contracts and history stay governed — but operating the plant belongs to your SCADA, O&M and asset-performance tools, and Navorda deliberately coexists with them.

No, and deliberately so. Navorda governs offtake agreements as commitments against the projects that supply them — what has been sold, to whom, from when, and what the supplying project has to achieve. It does not do settlement, meter data, imbalance, dispatch optimisation, forward curves, mark-to-market or trading; specialist energy trading and risk management products cover that well, and Navorda coexists with them. The question Navorda owns is whether the development portfolio can deliver what has been commercially committed.

Navorda Finance is the project financial layer of Navorda. It records project costs, revenues, forecasts and financial commitments against the same projects, versions, counterparties and permissions used for development governance. Financial records can also be connected to milestones and permits, so project schedule and financial timing can remain linked. Development happens in days and euros; Navorda governs both.

No. Navorda Finance governs project-level financial context. ERP and specialist finance systems continue to manage accounting, invoicing, payments, tax, treasury, P&L, balance sheet, cash flow and financial consolidation. The ERP records the accounting truth; Navorda connects financial reality to the project reality that explains it.

Yes. A financial record can be linked to a milestone or permit. For example, a forecast EPC payment can be defined relative to NtP. If NtP moves, the related financial date can move with it when the user chooses to maintain that link.

Navorda supports configurable business fields on financial records. A Funding Status can, for example, follow an amount through Forecast, Capital Call, Purchase Order, Goods Receipt and Payment, while the actual accounting and payment execution remain in the ERP and finance stack.

Yes. Navorda supports a configurable seven-level ledger-account hierarchy with source-system identifiers and reporting tags, alongside a three-level finance-figure hierarchy with budget codes.

Yes. Finance records belong to the same versioning model used by Navorda's project data. Locked reporting versions are read-only, preserving financial context alongside the project state at that reporting point.

Yes. External Models Governance, an optional add-on to Navorda Platform, governs assumptions, provenance and critical outputs from external models without replacing them. Attach the project's workbook (.xlsx or .xlsm), link the output cells you care about — CapEx, IRR, NPV — to governed project fields, and each value carries its file, sheet, cell, who linked it and when, read-only while linked. Pair the model's assumption cells (NtP, MW, CapEx, tariff) with the live project fields they should mirror: when the project moves and the model does not, the project shows a model-outdated warning and the outputs from that workbook are flagged as stale. Checks only read and compare; nothing is written into the model or into Navorda. Links and checks target project-level fields today, and linked values are not exposed through the MCP Connector, Navorda Connect or Navorda AI. Details: navorda.com/products/external-models

Yes. Navorda Decisions, part of Navorda Platform, is the governance register: each investment committee, board or steering committee decision is recorded on the project it concerns with its forum, date, reference in the minutes, rationale and alternatives, approved amount and capacity, and the counterpart it was taken on behalf of — the COO, the Investment Committee, a shareholder, an SPV, a lender. Conditions carry a status and a due date, commitments become owned, dated Activities, evidence is attached, and closing a decision stamps the date and the user. Records are versioned and role-based like the rest of the platform, and the Navorda MCP Connector exposes them read-only. It is a register of record, not an approval workflow: it does not route approvals, collect votes or sign documents. Details: navorda.com/products/decisions

A Fit Review is how an evaluation of Navorda starts. You bring one representative project; we review how your organization handles milestones, permits, dependencies, risks, ownership, reporting and decision-making on it, and say where Navorda does and does not add value. It is not a generic product demo. Request one from any page, or take the Corporate Distance Assessment first if you would rather start on your own.

A structured onboarding programme runs four to eight weeks: discovery and workflow alignment, tailored configuration, guided data migration, land/map activation, user training, and supported go-live.

Navorda is fully cloud-native on AWS, hosted in Frankfurt, Germany (eu-central-1), with hard multi-tenant isolation enforced at the data-access layer on every query. Data is encrypted at rest — RDS PostgreSQL for structured data, S3 for documents — and in transit with TLS. The platform runs on ECS Fargate and ALB, monitored with GuardDuty, VPC Flow Logs and network anomaly alarms with real-time alerting. Access control is SSO with Microsoft Entra ID and Google (standard OIDC) with permission-based RBAC on every endpoint and full audit trails. ISO 27001 and SOC 2 are in progress; the security page at navorda.com/security states the full posture plainly.

Yes. Navorda runs in AWS Frankfurt, Germany (eu-central-1). Data is encrypted at rest — RDS PostgreSQL for structured data, S3 for documents — and in transit with TLS. Even Navorda's AI stays in-region: Navorda AI runs on AWS Bedrock inside the EU, so portfolio data is never sent to a third-party AI service over the public internet. CabSan Solutions is an EU vendor based in Spain, and a Data Processing Agreement is available on request.

No. Navorda AI runs inside Navorda on AWS Bedrock in-region (EU), accessed with AWS IAM roles rather than stored API keys. Per AWS Bedrock's standard commitment, prompts and outputs are not used to train foundation models and are not shared with model providers. Navorda also keeps AI in an explaining role, not a deciding one: risk and deviation detection is a deterministic rule engine, and the AI layer only turns findings into readable explanations and suggested mitigations — no black-box decisions. For external AI assistants, the Navorda MCP Connector is permanently read-only, with landowner PII structurally excluded from every response.

Deletions are soft by default: records go to a Recycle Bin and can be restored, and permanent deletion is restricted to system administrators — a mistaken click never silently destroys portfolio history. Every record carries a full audit trail of who created and modified it. User offboarding follows your identity provider: Navorda uses SSO with Microsoft Entra ID and Google over standard OIDC, so deactivating an account in your IdP offboards it from Navorda, and MCP access is automatically revoked when organization membership ends. If you stop using Navorda entirely, your data is exportable in full — structured Excel and JSON — and tenant data is deleted on request.

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 Platform is the core every deployment starts with and includes the MCP Connector; Navorda Risks, Land, Finance, Transactions, Offtake, External Models Governance, Enterprise Integrations, Navorda Connect and Navorda AI are optional and scoped with the deployment. The proposal is transacted through AWS Marketplace — where a private offer carries the tailored terms and eligible purchases retire against committed AWS spend — or contracted directly with CabSan. See navorda.com/pricing for how pricing works, or contact info@cabsansolutions.com.

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; Navorda does not bill per-project overage or block work as the portfolio grows.

The return comes from three places, and each can be estimated before you buy. As illustrative assumptions drawn from real commercial proposals: a 2% negative CapEx deviation on a €40M asset is an €800,000 overrun — catching drift early against a preserved baseline protects exactly that. A three-month permit or land delay on a 36 MWp asset producing 70 GWh a year loses roughly 17.5 GWh, about €700,000 of revenue at €40/MWh. And if the platform releases around 10% of the time of 100 FTEs managing permits, land and construction at a €50,000 average salary, that is roughly €500,000 a year redeployed to value-added work. Substitute your own portfolio numbers — the structure of the case stays the same.

Nothing appears on an invoice, which is why the do-nothing scenario usually survives budget reviews. The cost is the distance between execution and decisions: leadership answers "how many MW are in permitting?" with three people and two days of reconciliation; a deviation someone in the field spotted in March reaches the portfolio review in June, after it is baked into COD; the same KPI is calculated differently by different teams; and after every surprise the most expensive sentence in the company gets said — "we knew that." Someone knew. The organization didn't. A single three-month slip that surfaces late on one mid-size asset can cost more than a year of software — that is the comparison an investment committee should see.

Navorda is built by CabSan Solutions, founded in March 2019 in Spain. The founder, Luis Cabello, has more than 10 years of IT consulting experience in the energy sector since October 2013, with a strategy and IT background from Accenture.

Custom applications can be valid, but successful custom software needs two scarce things: business experts with enough time to explain and specify the real business need, and a software team capable of translating that complexity into robust technical and product architecture. Even when both are available, the business keeps changing — new countries, technologies, permits, financing models, partnerships and reporting needs — and the risk is that every legitimate change becomes another requirement, another development cycle, another release. Navorda provides the governed operating foundation from which those requirements can be served through per-tenant configuration, integrations, Power BI, APIs, MCP and AI, so technology moves from solving each requirement independently to providing the foundation the business can evolve on. See navorda.com/roles/cto.

Navorda supports SSO with Microsoft Entra ID and Google (standard OIDC), role-based access control with custom roles per organization, Excel bulk import, audit trails, and per-tenant configurable data models. Navorda Connect, optional, brings the governed model to your enterprise stack — a Power BI Semantic Model Twin for corporate reporting, a REST API over supported resources, and Enterprise Integrations that connect ERP, CRM and treasury systems through governed imports and the API, scoped per deployment — and the Navorda MCP Connector, included in Navorda Platform, brings governed context to your enterprise AI. Navorda Finance complements your ERP: project-level financial context lives in Navorda, accounting truth stays in the ERP, and source-system identifiers plus Excel export support reconciliation between the two.

CabSan is a member of the AWS Partner Network and the NVIDIA Inception Program. Navorda is listed on the AWS Marketplace.

Yes. Navorda is the new name of the product marketed until September 2026 as Sherpa by CabSan; it is unrelated to other products called Sherpa. Every page on the former domain, sherpa-platform.com, redirects to the same page on navorda.com, and the product, the team, contracts and pricing are unchanged. The full announcement is at navorda.com/sherpa-is-now-navorda.

No. Navorda (formerly Sherpa by CabSan) is renewable energy project development software, built by CabSan Solutions in Spain. Its former name is shared with unrelated things — including SHERPA, the EU-funded hydropower research project at sherpahydro.eu (grant agreement 101172849); the other SHERPA research projects funded by the European Union; Sherpa Capital, the Madrid-based private equity firm at sherpacapital.es; Sherpa.ai, the Spanish artificial-intelligence company; Sherpa Agent: Talk to Your AWS Cloud, a separate product listed on AWS Marketplace; customer-support helpdesk, wealth-management, travel, insurance, recruitment and consumer applications using the name Sherpa. When checking reviews or documentation, confirm the vendor is CabSan Solutions and the domain is navorda.com (formerly sherpa-platform.com).