Skip to content
Contact us

Get a Free Demo

Tell us about your OCPP or OCPI testing needs. We’ll help scope the right workflow, show the product in context, and typically reply within 2 business hours.

Contact information

Average response time: <2 hours during business hours

Book time with our team

Choose a slot if you already know you want to discuss plan sizing, protocol coverage, roaming validation, or Enterprise requirements.

Typical reasons teams reach out

Most conversations start with one of these: choosing the right plan, validating a protocol or roaming workflow, or understanding Enterprise deployment options.

  • How many virtual chargers or roaming counterparts do we actually need?
  • Can you help us validate OCPP 1.6, OCPP 2.0.1, OCPI 2.1.1, or OCPI 2.2.1?
  • Do we need Professional, Enterprise, or an on-premises deployment?

When teams usually contact us

Most conversations fall into one of these three buckets. If one matches your situation, you are in the right place.

Sales sizing

You need help choosing between Pro and Enterprise for your charger volume, protocol mix, or QA workflow.

Protocol and roaming validation

You want to discuss OCPP 1.6, OCPP 2.0.1, OCPI 2.1.1, OCPI 2.2.1, GIREVE, or Hubject testing needs.

Enterprise and deployment questions

You need on-premises deployment, dedicated support, procurement answers, or high-scale load-testing guidance.

What happens after you reach out

  1. 1. We review your request

    Form submissions are typically reviewed within 2 business hours so your message does not disappear into a generic queue.

  2. 2. We scope the right workflow

    We align on protocol versions, vendor or partner coverage, and whether you need CPMS testing, roaming validation, or scale testing.

  3. 3. We show the next practical step

    That may be a demo, a trial recommendation, plan sizing, or a deeper technical discussion for Enterprise requirements.

What we can show in a first demo

A real protocol walkthrough

We can show OCPP or OCPI flows that match your version, charger type, or roaming workflow instead of staying at a marketing level.

Actual product views

Expect to see logs, workflow editing, charger profiles, and the parts of the product your engineers would use during evaluation.

A concrete next step

The goal is to leave the call with the right plan, evaluation path, and deployment conversation instead of a vague follow-up.