01
Establish governance
Identify owners for product, infrastructure, security, data, sites, hardware, integrations, and support.
Private deployment and operational control
Enterprise and government EV charging software
Sock8 supports large organisations planning EV charging across private sites, business units, fleets, workplaces, or public programmes with controlled access and clear operating ownership.
The platform can run as managed cloud or in customer-controlled private-cloud or on-premise infrastructure. Architecture, identity, networking, data location, integrations, resilience, handover, and support are agreed before deployment.
What this buyer needs
Outcomes the solution is designed around.
- Operate multiple sites within an approved governance model
- Keep infrastructure and data inside the required boundary
- Integrate charging with enterprise systems
- Transfer knowledge and operating responsibility clearly
What gets in the way
Operational and commercial friction to remove.
- Procurement and security requirements spanning many teams
- Private networking and data-residency constraints
- Complex roles across sites and business units
- Long-term upgrade, recovery, and support ownership
How it works
A buyer-specific path from scope to live operation.
02
Design the architecture
Agree deployment boundary, identity, networking, environments, capacity, observability, backup, and recovery.
03
Prove the operating model
Pilot representative sites, chargers, users, integrations, reports, failures, and support procedures.
04
Roll out with handover
Expand in approved waves, deliver documentation and training, and begin the agreed release and support cycle.
Inside the platform
The operating detail behind the solution.
Enterprise operators can centralise network visibility while keeping deployment, access, data, and support responsibilities within an agreed control model.
Representative Sock8 product interface
Relevant products
Use the modules this buyer actually needs.
Customer-hosted software
Private-cloud or on-premise installation with documented responsibilities.
Central operations
Sites, chargers, sessions, access, tariffs, roles, and reports in one CSMS.
Enterprise integration
Approved APIs and webhooks for internal systems and reporting.
Controlled migration
Move an existing estate through parity assessment, pilot, waves, and reconciliation.
OCPP 1.6JOCPP 2.0.1OCPI 2.2.1REST APIsWebhooks
Implementation
Make ownership and acceptance clear before rollout.
- 1
Requirements and ownership
Capture functional, security, infrastructure, data, integration, procurement, support, and acceptance requirements.
- 2
Architecture readiness
Prepare environments, network paths, DNS, certificates, identity, monitoring, backup, recovery, and access.
- 3
Pilot and acceptance
Validate representative end-to-end journeys, controls, integrations, operational procedures, and recovery cases.
- 4
Phased deployment
Onboard sites and users through governed releases with evidence, training, reconciliation, and handover.
Relevant evidence
Private cloud or on-premise
Customer-hosted option
Sock8 offers a perpetual customer-hosted licence with installation, documentation, handover, and annual support scoped to the approved architecture.
Deployment
Choose the right operating boundary.
Choose managed cloud, dedicated infrastructure, private cloud, or on-premise deployment according to the approved control boundary and operating model.
Pricing
Match cost to the buyer model.
Enterprise and government deployments use a custom quote based on software scope, connectors, environments, architecture, integrations, migration, availability, documentation, and support.
View platform pricingBuyer FAQs
Questions large and private deployments ask.
Can Sock8 run in customer-controlled infrastructure?+
Yes. Customer-hosted licensing supports approved private-cloud or on-premise environments with defined installation, operations, upgrade, and support responsibilities.
Can access be separated by site or business unit?+
Roles, permissions, sites, users, and reporting boundaries can be designed around the agreed organisational structure.
Does Sock8 support data-residency requirements?+
The hosting region and data boundary can be addressed in the deployment architecture, subject to the selected infrastructure and required integrations.
Can the platform integrate with enterprise systems?+
Yes. Required identity, fleet, ERP, finance, support, reporting, or data-platform flows are scoped through approved APIs, webhooks, or custom integration work.
How are upgrades and support handled?+
Release ownership, maintenance windows, testing, rollback, major-version work, escalation, and support coverage are documented in the licence and support scope.
Next step