CPO startup
„How do we go live fast with OCPP 2.0.1 and billing?"
Modular CPMS + OCPI 2.3 out of the box. Broker and Headless API as the foundation, whitelabel Driver and Fleet portal on top.
CPMS CoreOCPP BrokerDriver PortalBilling
What other CPMS platforms are promising three years from now is already running in production with Pipelet today — built AI-native, shipped with full source code, hosted as SaaS or on-premise in your own data center. Over 100 companies across DACH and Europe already run Pipelet.
Pipelet treats Plug & Charge as a full CPMS capability: Hubject integration for public charging, ISO 15118-20 in the CPMS, and home-charging vehicle recognition in the Driver Portal.
Per station, per tenant, per module. The OCPP broker switches individual charge points from your legacy platform to Pipelet — drivers don't notice a thing.
Drivers, operators, integrators — every role gets its own UI. Below: the shared CPMS core and an API-first service layer that plugs into any landscape.
OCPP 1.6 & 2.0.1 simulator — virtual charge points so you can test your CPMS, tariffs, or OCPP integration against real protocol flows.
Full API reference, OpenAPI specs, Postman and Insomnia collections, code snippets for curl, Python, JavaScript and Go.
OCPI 2.2 client simulator. Tests the roaming interface of any CPMS within minutes — credentials, tokens, sessions, CDRs, tariffs. Launchable without login.
Live status of every Pipelet service. Fully transparent for customers and integration partners — no login, always up to date.
WebSocket proxy between charge points and your backend(s): multi-backend routing, digital twin, replay and live traffic — watch it in the portal instead of guessing from logs.
Every module in Git — self-host, customize, audit. No vendor lock-in, no black box, no surprises on the upgrade path.
Migrate per site, per module, per tenant — never big bang. Run in parallel with your current solution; the OCPP broker switches stations one at a time.
Your own brand, your own domain, your own colors — in every portal. No "Powered by" in the Driver or Fleet UI; your end customers only see your brand.
MCP server, cleanly documented APIs, isolated modules — the perfect foundation for Claude, Copilot and Cursor workflows. New features in days instead of months.
Multiple CPOs, multiple EMPs, multiple fleet customers — all isolated, all multi-tenant, all auditable.
12,000+ live charge points, 24/7 monitored, deployed across DACH. Critical charging infrastructure is our daily business — no MVP, no beta excuses.
Five typical starting points, five concrete answers. Pick the role that's closest to you — and see which modules fit.
„How do we go live fast with OCPP 2.0.1 and billing?"
Modular CPMS + OCPI 2.3 out of the box. Broker and Headless API as the foundation, whitelabel Driver and Fleet portal on top.
„Eichrecht, XRechnung and home charging — all from one provider?"
In the platform, not as an add-on. Multi-tenant per municipality, SEPA and VAT/OSS at the core, HR export for employee home charging.
„Multi-backend architecture for parallel operating models?"
The OCPP broker routes per station — factory sales, dealer network and leasing in parallel without conflict. Plug & Charge + ISO 15118-20 native.
„Company-car home charging with HR export?"
Driver Portal + CarData integration. Automatic session capture at the home wallbox, monthly PDF/CSV/XRechnung export straight to the HR system.
„Test OCPI 2.2 and 2.3 against Hubject?"
EMP Backend in production, EMP Simulator for testing — both from the same codebase. CDRs, tariff publishing and token authorization ready in minutes.
Pipelet is built for operators that need to work productively in Germany, Austria, Switzerland and across the EU: with local payment rails, controllable billing processes, data protection, works council requirements and multi-tenant portals.
That is why we do not think only in generic session billing, but in European operating realities: SEPA, XRechnung/ZUGFeRD, VAT/OSS, Eichrecht evidence, ISO 15118, Hubject, company-car home charging, multilingual interfaces and clear tenant boundaries are part of the product architecture.
Tariffs, receipts, mandates and invoice data are modeled as core processes, not as a late export from a session list.
Plug & Charge, roaming, CDRs and OCPP commands live in the same suite. This reduces gaps between the operator UI, EMP portal and backend.
Home charging zones, vehicles, RFID, private and business charging sessions as well as reimbursements can be modeled tenant by tenant.
Audit logs, role models, data minimization, clear tenant boundaries and multilingual interfaces are part of the product, not just project work.
Home charging, charging history, CarData integration — the EV driver UI of the Pipelet suite.
Fleet management, driver management, RFID and billing for commercial EV fleets.
The new operator UI: sites, charger commands, vouchers, OCPI, billing.
Vehicle recognition, contract certificates and ISO 15118-20 flows — publicly through Hubject, at home with capable wallboxes.
Charge points, tariffs, OCPI, billing — the established operator console.
OTA firmware campaigns, ChangeConfiguration, maintenance windows.
Virtual OCPP 1.6 & 2.0.1 charge points for testing and demo — no login required.
API docs, OpenAPI specs, Postman/Insomnia collections.
Visual workflow editor for event automation across the entire suite.
WebSocket broker with digital twin, smart proxy and messaging for OCPP.
Model Context Protocol server — the Pipelet suite directly inside Claude, Cursor, Copilot.
Live status of all Pipelet services — publicly visible, no login required.
E-Mobility Provider portal: roaming partners, driver tokens, CDRs, tariff publishing.
OCPI testing against any CPMS: simulate roaming flows, provoke errors, validate payloads.
Meters, load management, smart charging on site — decides locally, monitored centrally.
Dynamic site-cap distribution: splits the available power across all connected EVSEs in real time.
If yours is here — great. If not, a 30-minute call will answer it honestly.
Yes. Every module ships as source code in Git, with a Dockerfile and systemd units in the repo. Hosted by us, in your own data center, or in your VPC — same code, same upgrade path. Moving between models is a deploy, not a project.
Per site, per tenant, per module — never big-bang. The OCPP broker sits as a transparent layer between your stations and backends and switches traffic station by station. Drivers don't notice a thing, and you can route back any time.
Hubject (Intercharge) natively via OCPI 2.2.1 and 2.3. Direct peering with other CPOs via OCPI credentials handshake, bidirectional (push + pull) for tokens, locations, tariffs and CDRs. EMP Simulator for testing against third-party CPMSs — launchable without login.
Three models: SaaS from EUR 5.90/CP/month, on-prem annual license from EUR 18,000, Appliance with industrial PC from EUR 2,490 + EUR 249/month. Full per-module price list on /pricing/. All models include the complete feature set — no feature gating.
Kick-off to proof-of-concept in 1–2 weeks, to production cut-over typically 4–8 weeks — depending on the number of stations and legacy integrations. Parallel operation with the existing platform the entire time; no hard deadline, no big-bang cut-over risk.
Eichrecht conformity lives with the hardware manufacturer — the signed meter value comes from the metering device itself. Pipelet processes and archives the signed values in an audit-safe way, with customer-specific transparency-software export on request.
From the first kick-off call to production cut-over, typically 6–10 weeks. Parallel operation the whole time — no hard deadline, no rollback stress.
You describe the current landscape and pain points. We'll show you exactly which Pipelet modules fit — or tell you honestly if we're not the right choice.
OCPP Broker, CPMS Core and Driver Portal run live against your test stations. You see real traffic, real billing, real diagnostics — no slide deck.
Per site, per module, per tenant. The OCPP broker switches stations one at a time — always with a rollback path. Drivers don't notice a thing; you go at your own pace.
Software service provider focused on electric mobility, energy and Microsoft Azure. NeLeSo consults, builds and tests custom solutions — including OCPP gateways, charging-infrastructure backends and fleet-management tools.
Full-service provider for charging infrastructure — from consulting, planning and installation through operations and maintenance. With the WALL-E Charging Portal, photovoltaic integration and Charging-as-a-Service models.
Europe's marketplace for depot charging: Depotcharge connects site operators with fleet operators and enables automated charging at verified depots across Europe.
Automotive retail group running Pipelet as central CPMS for dealer sites and fleet operations — whitelabeled under their own brand, with Stripe and SEPA billing.
Tell us in a 30-minute call what you run today and where the pain points are. We'll show you exactly which Pipelet modules fit — or tell you honestly if Pipelet isn't the right choice.