All users

Monitoring open

Live status of all Pipelet services — publicly visible, no login required.

Fully open, no login. Status, metrics and incident history always live-visible.

Screenshot coming soon

Monitoring is the public status page of the Pipelet suite. Every service with current status, response time trace and open incidents. No login barrier — customers, partners and integrators can check in any time.

Data comes from internal health checks that ping every service every minute. Incidents are automatically pushed to the page, post-mortems documented after resolution.

For your SLA reporting there's a machine-readable feed (JSON) with all historical metrics. Webhook subscription for your own dashboards or paging integration.

What to expect

Live per-service status

Broker, CPMS, Fleet, Driver, Simulator, Studio — every service with an uptime indicator, current response time, ongoing incidents.

Incident history

Complete timeline of past incidents, including duration, affected services and post-mortem.

JSON feed

All data also as machine-readable JSON endpoint — directly into your Grafana, SLA dashboard or paging tool.

Webhook subscribe

Subscribe to status changes via webhook. No polling needed, no rate-limit risk. Retry logic on our side.

Common scenarios

1

Customer asks: is your system down?

Link to monitor.pipelet.com in your signature. The customer sees for themselves whether the problem is Pipelet or their own integration — ticket volume drops noticeably.

2

SLA report for enterprise customers

Monthly JSON export into your BI tool, automatically formatted as PDF for the enterprise customer report — including uptime numbers and incident timeline.

How Monitoring fits into the suite

Frequently asked questions

Is Pipelet available as source code?
Yes. Every module is available as a source-access package — complete with Docker Compose, documentation and an SLA support channel. You can audit, customize and self-host.
Which OCPP versions are supported?
Full OCPP 1.6 and 2.0.1 including Security Profiles, Smart Charging, and ISO 15118 Plug & Charge.
Can I use individual modules only?
Yes. Every module is standalone — you can deploy e.g. just the OCPP Broker as infrastructure and build your own CPMS on top.
What does onboarding look like?
We start with a 30-minute call to scope requirements. After that you get a concrete proposal with modules, timeline and price. Pilot typically live in 4–8 weeks.

Sounds like a fit?

Fully open, no login. Status, metrics and incident history always live-visible.

You might also like

All products