System stitching becomes the job
When operations, billing, field service, partners, and reporting live in different systems, every handoff creates work and risk.

Sparqly brings operations, revenue, field service, partner networks, internal and external roaming, fleet, grid, and compliance into one CPMS — so your team can replace handoffs with one operating model.
Product suite
Each product owns a critical layer of the charging business. They share tenant, identity, partner, and evidence boundaries — so a fault in Ops can become a work order in Service and a governed adjustment in Revenue without a manual handoff.
OCPP gateway, live sessions, alerts, remote commands, and diagnostics across every site.
↳ Learn moreTariffs, invoicing, exception queues, partner settlement, and traceable evidence chains.
↳ Learn moreWork orders, crews, parts, vendors, preventive maintenance, and completion evidence.
↳ Learn moreCommissioning, audit logs, migration runs, and tenant governance with full evidence.
↳ Learn moreThe product
One workspace for sessions, sites, revenue, partners, faults, and service work. Different roles see the context they need, while identity and audit evidence remain consistent.

Built for operational scale
EU-resident by default, with regional deployment available where legal requirements demand it. The charger gateway is isolated from business data, tenant boundaries are structural, and material financial actions carry linked evidence.
The charger gateway runs on its own database. Slow charge events never lock billing or reporting.
Authorize, price, clear, and settle across member CPOs without forcing the session through an external hub.
Draft to paid on the same evidence chain your auditors reach for — variance, reversal, and dispute aware.
Why Sparqly
The strongest platforms in this market already cover operations, billing, roaming, and white-label. Sparqly goes further by keeping the workflows between those domains — faults, revenue exceptions, partner access, internal roaming, and settlement — inside one governed system.
When operations, billing, field service, partners, and reporting live in different systems, every handoff creates work and risk.
A failed payment, missing CDR, tariff mismatch, or settlement variance needs an owner and evidence before month-end.
Distributors, site hosts, service companies, and roaming members need different access, commercial terms, and settlement views.
Why operators switch
Revenue assurance
Sessions that fail reconciliation — meter deltas, tariff conflicts, unsettled PSP, partner gaps — surface for review instead of disappearing into a month-end spreadsheet.
Explore Sparqly Revenue →
Partners and internal roaming
Provision distributor-backed sub-CPOs, give site hosts and service partners scoped portals, and let approved member CPOs roam across the network. Commercial terms, visited tariffs, wallet movements, VAT, disputes, and payouts stay linked to the sessions that created them.
Explore Sparqly Network →
Field service
A charger fault becomes a work order with crew assignment, parts reservation, vendor SLA, and completion evidence — linked back to the session it affected.
Explore Sparqly Service →
Switching CPMS
Preview source data, resolve conflicts, score readiness, and verify the relationships between chargers, credentials, tariffs, partners, and history. Cutover gates and rollback planning turn migration into a controlled programme, not a leap of faith.
Plan a controlled migration →
Security & privacy
EU-resident by default, with regional deployment where law requires it. Tenant and zone isolation, scoped partner access, audited privileged actions, consent records, data-rights workflows, and linked financial evidence are built into the operating model.
Where we are
“Your next CPMS should remove operational boundaries — not become another one.”
A Sparqly product principle
For developers
A scoped REST API, HMAC-signed webhooks, OCPI and OICP roaming, reporting connectors, gateway events, and an OpenAPI contract — so integration teams build against governed interfaces instead of database access.
GET /api/v1/charging-sessions?status=active
{
"data": [{
"status": "charging",
"energy_kwh": 14.27,
"tariff_id": "tar_standard_es",
"auth_method": "rfid"
}]
}Get started
Show us your current platform, charger mix, partner structure, and operational bottlenecks. We will map the demo to the workflows your team wants to replace.
Book your walkthrough