Skip to main content
The sandbox is free and needs no card. Everything past it is a plan.
This is early pricing 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 the rows mean

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. 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 journey never needs Automate. Against the sandbox it is free; against your own endpoint it is the partner-endpoint row above. Direct Payment covers the Payments modules, which are a separately published EVRoaming Foundation extension rather than part of the core specification. Against the sandbox those suites are open to everyone, so you can see what they do before you buy. Scheduled runs repeat the same sweep against a registered endpoint on a cadence you set, daily or weekly, so an integration proved once keeps being checked instead of being left alone. The connection shows what the last scheduled run found. They need a real endpoint: the sandbox target is our own peer, so it cannot regress. 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.

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 Certified is, and is not

Certified 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. The name is older than the rest of this page and it promises less than it sounds. ChargerDojo is not an accreditation body and issues no certificate, and formal OCPI conformance certification is issued by the EVRoaming Foundation through its own process. The verdict logic is the same on Certified 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:

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 Certified 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 two days. 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.
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 two days 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.