Billing should not be an add-on
Tariff components, VAT rules, partner settlements, and revenue assurance exceptions need to be native to the platform — not bolt-on integrations that create reconciliation gaps at month end.
Company
Software for the operational reality of charging networks.
Sparqly is built around the parts of charging operations that usually sit outside the first-generation CPMS: finance, field service, partner settlement, compliance, migration, and grid participation.
Why we built Sparqly
The CPMS market solved connectivity first. Everything else became someone else's problem.
First-generation CPMS platforms were designed to connect chargers and report session data. That was enough when networks were small. As networks scaled, operators needed billing, partner settlement, field service dispatch, fleet management, revenue assurance, and regulatory compliance — and found themselves stitching vendors together to get there.
Sparqly is built to close that gap. Not by adding features to a monitoring tool, but by designing a platform where operations, revenue, service, and governance share one data model from the start.
Field work is part of the network
A charger fault, a technician dispatch, a parts reservation, and a completion record are one workflow. Exporting data to field service tools and back creates structural risk to uptime and evidence.
Compliance needs an evidence chain
Every financial adjustment, regulatory submission, and support action needs to be explainable. Evidence chains are not an audit feature — they are how a network stays trustworthy at scale.
What we believe
Principles behind the platform.
One data model, all domains
Operations, revenue, service, fleet, and compliance share tenant, zone, asset, and evidence boundaries. Cross-domain data should never require an integration to stay consistent.
Migration is a first-class feature
Switching CPMS platforms is the biggest risk in the market. Migration tooling — with dry-run preview, conflict detection, and rollback — is built into the platform, not bolted on at the end of a contract.
Operators own their data
Your session history, driver data, tariff configurations, and partner agreements belong to you. Full export, full audit trail, full portability — from day one, not after a support ticket.
Where we are
Private beta — evaluating real operator workflows.
Sparqly is in active private beta. The full product suite — operations, revenue, field service, fleet, grid, partner and distributor management, internal and external roaming, white-label, and compliance — is implemented. Product walkthroughs are being used to validate the platform against the operating models of European CPOs.
If you are evaluating CPMS platforms or planning a migration from an existing system, we would like to understand your operating model before we open access more broadly.