For OCPP Developers

Build Your CSMS Without
Buying Physical Chargers

Test your OCPP backend with thousands of simulated charging stations.
No hardware, no waiting, no $500k procurement process.

The Problem with Traditional OCPP Development

You know this pain if you've tried building a CSMS

Hardware Dependency

Can't test your CSMS until you buy physical chargers ($10k+ each). Procurement takes weeks. Setting them up takes more weeks.

Scale Testing is Impossible

Need to test 10,000 concurrent connections? Good luck buying 10,000 chargers. Your CFO will love that $100M purchase order.

Edge Cases Never Happen

How do you test a network timeout mid-transaction? A corrupted meter value? Firmware update failure? You can't reliably reproduce these with real hardware.

Slow Development Cycles

Change one line of code? Walk to the test lab, physically interact with a charger, check logs. Repeat 50 times a day. Your velocity dies.

How Gridmock Solves This

Start Testing in 5 Minutes

No hardware. No procurement. No waiting. Spin up 10 virtual chargers with a single API call and start developing immediately.

curl -X POST api.gridmock.com/chargers
-d '{"count": 10, "protocol": "1.6"}'

Test at Massive Scale

Simulate 10,000 concurrent chargers for the cost of a coffee. Find bottlenecks before your production launch, not after.

50,000+ chargers supported
<50ms response time

Inject Any Scenario

Trigger edge cases on demand: network failures, corrupted messages, timeout sequences. Test what's impossible with real chargers.

Network interruptions
Malformed payloads
Race conditions

Your Development Workflow

How OCPP developers use Gridmock every day

1

Local Development

Point virtual chargers at your localhost CSMS. Write code, save, test immediately. No hardware in the loop.

# Start your CSMS locally
npm run dev:csms

# Spin up test chargers pointing at localhost
gridmock create --count 5 --url ws://localhost:8080
2

Automated Testing

Run OCPP compliance tests in your CI pipeline. Every PR gets validated against the full spec.

# .github/workflows/test.yml
- name: OCPP Compliance Tests
  run: gridmock test --scenario ocpp-1.6-compliance
3

Load Testing

Before launch, stress-test your staging environment with 10,000 concurrent chargers. Find bottlenecks early.

# Ramp up to 10k chargers over 5 minutes
gridmock load-test --target 10000 --ramp 5m
4

Debugging Production Issues

Customer reports a weird edge case? Recreate it instantly with a scenario script. Fix and verify in minutes.

# Reproduce specific customer issue
gridmock scenario --file customer-bug-123.json

What You Can Test

Message Flow Validation

  • BootNotification → Authorize → StartTransaction flow
  • MeterValues frequency and accuracy
  • StopTransaction and session cleanup
  • Heartbeat intervals and timeout handling

Error Handling

  • Network disconnections mid-transaction
  • Invalid JSON payloads and schema violations
  • Timeouts and retry logic
  • Concurrent request handling

Smart Charging

  • SetChargingProfile command handling
  • Load balancing across multiple chargers
  • Dynamic power limits and scheduling
  • Time-of-use optimization

OCPP 2.0.1 Features

  • Device model and variable attributes
  • ISO 15118 Plug & Charge simulation
  • Security extensions and certificate management
  • Transaction events and composite schedules

Built for the Way OCPP Teams Work

Gridmock is designed around the real pain points of CSMS development

Ship releases without waiting on hardware

Run full OCPP compliance checks in CI on every commit instead of blocking releases for weeks on physical charger availability.

Catch edge cases before production

Fault-injection scenarios let you reproduce race conditions, network drops, and malformed payloads that are near-impossible to trigger reliably on real hardware.

Load-test at scale for the cost of a coffee

Simulate thousands of concurrent chargers in software instead of buying a warehouse of EVSE units to stress-test your backend.

Start Building Today

Gridmock is in early access. Request access and start testing your CSMS without hardware.

Questions? Request a demo or talk to our team.