Skip to main content
The sandbox is free and needs no card. Everything past it is a plan.
This is a launch price and it will rise. It is not locked or frozen, and nothing here is a commitment to a future price. What you are quoted at signup is what you pay.

The plans

Yearly is ten months for twelve.

What is free

Running against ChargerDojo’s sandbox is free. Running against your own or a partner’s endpoint is paid. That holds at every tier, including a signed-out browser. Load runs and parallel charging sessions need Automate even against the sandbox. The API quickstart drives a free sandbox run through the API, but the API needs a cdojo_ key, and keys need a paid plan. Without a key, run the same test in the browser.

Free without an account

  • The simulator and Learn. Open chargerdojo.com to watch OCPI messages move between CPOs, eMSPs and chargers. Learn explains the protocol, and guided scenarios walk through failures such as a charge billed twice.
  • The MCP server. The MCP server has nine tools that need no key or signup. They list OCPI versions, compare two versions, show how each encodes the credentials token, list suites, checks and journeys, validate a JSON object against its schema, describe what each plan adds and send the team feedback. See Connect a coding agent.
  • Sandbox runs. While signed out you can run against the sandbox, list your reports and share them. Your browser keeps its anonymous session until the session expires or you clear its stored data, within report retention. Signing in attaches those reports to your organisation, so you can reach them from other devices.

What a sandbox run proves

The sandbox is a real OCPI peer: a run discovers its versions and makes real HTTP calls to its modules, and the report has the same per-check evidence as a paid run. It tests ChargerDojo’s own peer, so a green result shows how the tool works, not how your implementation behaves. Coverage and sandbox limits explains what the sandbox stores and where it differs from a real endpoint.

Where the free line falls

The line follows whose infrastructure a run touches, not the quality of the report. A run against your endpoint uses a runner and a real HTTP conversation with a third party; a sandbox run stays inside ChargerDojo. The MCP server’s account tools work with a paid API key; account tools for signed-in free accounts are launching soon.

What the rows mean

Conformance suites cover the versions the app offers: 2.1.1, 2.2.1 and 2.3.0. OCPI 2.2 was superseded by 2.2.1 within months and is retired from the pickers, so it has no row of its own. Partner endpoints are the targets you test against. A free account tests against the sandbox, which is free at every tier and never counts toward a plan’s partner endpoints. A local connector reaches an endpoint behind your firewall over an outbound connection, so your service is never reachable from the internet. Each organisation can pair up to ten. See Test a private endpoint. Colleagues are free, and they draw on the same endpoints. Nothing here is priced per person and no plan carries a seat count, so invite the whole team. What a colleague does not bring is capacity: the partner endpoint allowance above belongs to the organisation, so two people on Integrate hold three endpoints between them rather than three each. See Work with a colleague. API keys are the whole reason the rest of this documentation exists. Without one there is no API, so nothing runs from a script or a pipeline. See Create an API key. Load runs drive one journey at volume to see how your implementation behaves under concurrency. They need Automate even against the sandbox, because the cost is ours either way. So do parallel charging sessions, the 2 to 6 overlapping tracks you can set on a single journey: same concurrency, same plan, whichever target you point them at. A single-track core journey uses the partner-endpoint row above. Hub relay, Bookings and Direct Payment have the separate capability rows shown in the table. Core journeys against the sandbox are free. Gireve and Plugsurfing Roam profiles grade a journey against the rules in that partner’s published guide, pinned to its revision, rather than against OCPI alone. Against your own endpoint they need Automate; against the sandbox they are open to everyone, like Direct Payment and Bookings. The hub-routed charge runs a graded charge through a hub ChargerDojo plays, as Gireve or Plugsurfing Roam, so against your own endpoint it needs Automate too. The primary sources are Gireve OCPI implementation guides and Plugsurfing Roam OCPI CDR guidance. Those are partner expectations, not extra OCPI requirements or partner approval. Direct Payment covers Payments: a separately published EVRoaming Foundation extension for OCPI 2.2.1 and a core chapter in OCPI 2.3.0. OCPI 2.1.1 has neither. Against the sandbox those suites are open to everyone, so you can see what they do before you buy. The 2.2.1 extension’s cover says:
“This is a separate module which can be used by CPOs and is an addition on the OCPI 2.2.1 protocol.”
EVRoaming Foundation Direct Payment 2.2.1, page 1. The 2.3.0 core chapter identifies itself as:
Module Identifier: payments Data owner: PTP
OCPI 2.3.0 Payments. Roaming hub identity uses one CPO test registration on Integrate. Roaming hub relay uses two linked counterparties on Automate and can run on a schedule. Sandbox includes the catalogue and a static reference-hub report. Custom includes both modes across hubs on quoted fair use. Both test your own hub; the hub-routed charge tests your eMSP through a hub we play, and needs Automate. Scheduled runs repeat a conformance sweep or a selected paired hub relay journey on a daily or weekly cadence. The connection shows what the last scheduled run found. They need your own endpoint. Sandbox endpoints run ChargerDojo’s own code, so scheduled runs cannot detect changes to your integration. Report retention is how long a graded report and its share link stay readable. It splits free from paid and does not differ between paid plans. Upgrading gives the reports you already have paid retention, counted from when each was made.

What every plan gets, including the free one

The verdict logic is the same at every tier, and that is deliberate. A free sandbox run produces the same report, with the same per-check evidence and the same refusal to fail you for declining a recommendation, that a paid run against your partner produces. Read your report is worth reading before you spend anything: it says what a green result does and does not license, and where our own coverage stops.

What Custom is, and is not

Custom is everything in Automate, priced on the endpoints and runs you need rather than from the table above. It is a quote, so it is the one plan you cannot start from inside the app, and it is why the endpoint row above says fair use rather than a number: how many partners you test against is part of the conversation, not a rung you are sold. Tell us what you need and we will scope it with you. ChargerDojo issues no certificate. Formal OCPI certification happens on the EVRoaming Foundation’s test tool, EVRTT. The verdict logic is the same on Custom as on the free sandbox. If a partner or a regulator wants a record of what you ran, tell us what it has to show and we will scope that work with you.

Ceilings, and why they are not on this page

Runs per minute and runs in flight are set per deployment, so a number printed here would be one environment’s rather than yours. Read your own: Operation reference: GET /usage.

Free trial

Integrate comes with a seven-day free trial. Start it from the Integrate card on the pricing page, or from any place in the app that offers Integrate.
  • You enter a card at checkout and pay nothing for seven days. The first charge is taken when the trial ends, at the monthly or yearly price you chose.
  • Cancel before then in Settings, Billing, Manage billing, and you are not charged. The trial keeps running to its end, then your organisation moves to the free plan.
  • Each organisation gets one trial, and so does each company email domain: once someone at acme.com has started one, colleagues on acme.com start Integrate as a paid plan.
  • The trial is for organisations new to paid access. One that has bought a plan or been given one by our team starts Integrate as a paid plan.
  • The trial needs a verified work address. Personal addresses such as Gmail or Outlook can buy Integrate but cannot start a trial.
The dashboard shows the days left while the trial runs. Everything Integrate unlocks works during the trial, with the same three partner endpoints.

Changing plan

Upgrading is offered in the app wherever a paid feature is, and on the pricing page, and takes effect immediately. If you are testing more endpoints than Automate holds, that is what Custom is for: sales@chargerdojo.com.

When a plan ends

A plan ends when you cancel it, when the paid period runs out, or when a renewal payment fails for one day. Your organisation then moves to the free plan. What stops:
  • Runs against your own endpoints, and the charging journeys that need a paid plan.
  • Every call made with an API key. It answers 402 with a message naming the plan, so a pipeline fails saying why rather than with an authentication error.
  • Scheduled runs, which pause until the plan is back.
  • Share links to reports about your own endpoint, which stop resolving.
What is kept:
  • The endpoints you registered, and their schedules.
  • Your reports, for as long as their retention lasts.
  • Your API keys, which work again as soon as the plan does.
A trial that ends without a payment ends the same way, and Start Integrate brings it all back. An organisation that has had its trial does not get a second one. Resubscribing brings all of it back: the dashboard, Billing in Settings and every paid feature offer the plan you had, in one step. Paused schedules start on their next occurrence. If a renewal payment fails, your plan keeps working for one day while the card is retried, then pauses. The card is retried for 15 days in all. Update it in Settings, Billing, Update payment method, and the plan comes back without a new subscription.