Security and deployment

Security and deployment for OCPP and OCPI testing

This page does not replace a security review. It gives buyers one place to align deployment model, data-handling, and support before a deeper conversation.

The fastest way to lose a technical buyer is to hide deployment and procurement questions behind a generic demo CTA. This page exists so teams can qualify whether they need cloud evaluation, an Enterprise deployment conversation, or a more detailed architecture review.

Deployment models

Cloud evaluation

The fastest path for early protocol validation, product walkthroughs, and initial regression coverage when a team wants to move without infrastructure work first.

On-premises deployment

Relevant when procurement or internal policy requires tighter network control, internal hosting, or a deeper architecture review before rollout.

Hybrid deployment

Useful when teams want cloud speed for evaluation but need a controlled production setup for larger QA, partner onboarding, or procurement readiness.

Questions buyers usually ask

Data handling

What test traffic is retained and for how long during evaluation.
How teams can request deletion or narrower scope for sensitive test data.
Which environments or endpoints are used during protocol validation and partner testing.

Access and support

Who gets access during the trial or pilot and how support is handled.
What response expectations apply when a team is evaluating Pro or Enterprise.
When a buyer should move from self-serve testing into a scoped technical conversation.

Procurement readiness

What architecture, deployment, and support questions should be answered before security review starts.
When on-premises or hybrid deployment needs to be part of the buying conversation.
How protocol scope, vendor coverage, and load expectations influence the right plan.

What the site already helps verify

Deployment discussion before procurement

The site already separates early cloud evaluation from Enterprise conversations around on-premises or hybrid deployment.

Protocol scope is visible before the call

OCPP 1.6, OCPP 2.0.1, OCPI 2.1.1, and OCPI 2.2.1 pages make it easier for buyers to align security questions with actual usage.

Support expectations are explicit

Pricing and contact flows now explain when a team can self-serve and when dedicated support or procurement help should be discussed.

Inspect a sample report

See the kind of evidence buyers can review before moving deeper into evaluation.

Match deployment to plan

Use pricing to decide when cloud evaluation is enough and when Enterprise is the better fit.

Start a deployment discussion

Use contact when procurement, architecture review, or support requirements are already part of the conversation.

If your team needs a deeper review, use contact to scope protocol versions, deployment model, and support expectations before procurement work starts.