PRIVATE BETA · FULL-SUITE CPMS

Run the charging business.
Not just the chargers.

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.

BUILT FOROCPP 1.6 / 2.0.1 / 2.1OCPI 2.2.1 CPOOICP 2.3Internal network roamingOSCP 2.0REVE / SGV

Product suite

Four products. One platform.

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.

The product

The control plane operators actually run from.

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.

app.sparqly.eu / operations
Sparqly operator dashboard showing live network operations, sessions, and revenue

Built for operational scale

Built like infrastructure, not a bolt-on.

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.

GATEWAY UPTIME
Live %
Measured per tenant and shown in the CPMS operator workspace
DB-isolatedOCPP gateway transport

The charger gateway runs on its own database. Slow charge events never lock billing or reporting.

InternalNetwork roaming

Authorize, price, clear, and settle across member CPOs without forcing the session through an external hub.

T+1Partner settlement close

Draft to paid on the same evidence chain your auditors reach for — variance, reversal, and dispute aware.

Why Sparqly

Connecting chargers is table stakes. Running the business is where complexity compounds.

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.

01

System stitching becomes the job

When operations, billing, field service, partners, and reporting live in different systems, every handoff creates work and risk.

02

Revenue problems surface too late

A failed payment, missing CDR, tariff mismatch, or settlement variance needs an owner and evidence before month-end.

03

Partner growth multiplies complexity

Distributors, site hosts, service companies, and roaming members need different access, commercial terms, and settlement views.

Why operators switch

Remove the operational gaps that keep becoming manual work.

Revenue assurance

The exception queue your finance team has been waiting for.

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 →
app.sparqly.eu / revenue / exceptions
Sparqly revenue assurance and finance dashboard

Partners and internal roaming

Grow the network without turning every new relationship into a project.

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 →
app.sparqly.eu / finance / settlements
Sparqly finance workspace with settlement and roaming controls

Field service

From fault to fix without leaving the platform.

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 →
app.sparqly.eu / service / work-orders
Sparqly work order detail with crew, parts, and evidence timeline

Switching CPMS

Rehearse the migration before the network depends on it.

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 →
app.sparqly.eu / operations / charger
Sparqly charger workspace with commissioning, commands, sessions, and evidence

Security & privacy

Security and evidence are product boundaries.

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.

Evidencechained
Tenantscoped
Privacyconsent-aware
Audit logrecorded

Where we are

“Your next CPMS should remove operational boundaries — not become another one.”

A Sparqly product principle

● Private betaFull product suite implementedEU-resident by default

For developers

Built for operators. Open for integrators.

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.

REST API per domainSigned webhooksOpenAPI contract
GET /api/v1/charging-sessions?status=active

{
  "data": [{
    "status": "charging",
    "energy_kwh": 14.27,
    "tariff_id": "tar_standard_es",
    "auth_method": "rfid"
  }]
}

Get started

Ready to run a better network?

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