Contact
Talk to the AmpNexus team
Book a demo, ask a question, or get help — we typically reply within one business day.
Book a demo
See the platform live with a walkthrough tailored to your fleet, hardware mix and integration plans.
info@ampnexus.co.ukGeneral enquiries
Questions about the platform, partnerships, or anything else — we'd love to hear from you.
info@ampnexus.co.ukPlatform support
Already running on AmpNexus? Our support team is ready to help with any operational issue.
support@ampnexus.co.ukCall us
Speak directly with the AmpNexus team about the platform, partnerships, or support.
+44 300 180 0413Common questions
What evaluators usually ask us
Which OCPP versions do you support?
OCPP 1.6 through 2.1, running side-by-side on one backend. Mixed fleets are the normal case for us, not the exception — you can modernise hardware on your own schedule.
Can we integrate the platform with our own systems?
Yes. AmpNexus uses scoped service APIs, webhooks and Server-Sent Events to connect charging operations to other systems. The public OpenAPI reference documents the external entry points currently available, and we map additional integration requirements during technical discovery.
How do firmware updates avoid taking chargers offline?
NexusDeploy rolls out changes in cohorts (canary → phased → full fleet) with approval gates, idle-only maintenance windows, per-device status tracking, and automatic rollback when failure thresholds trip.
Do you support multi-tenant operation and white-labelling?
Yes. The platform is multi-tenant with tenant isolation and role-based access control. The Portal, Driver App, Installer App and Smart Charging Mode can be presented under each customer's brand.
What visibility do we get for audits and compliance?
Every sensitive action is captured in audit logs, full OCPP message history is retained for troubleshooting and root-cause analysis, and reports can be exported on demand or on a schedule.
How do we get started?
Book a demo and we'll walk through the platform against your fleet, hardware mix and integration plans, then agree an onboarding path from there.
Looking for documentation?
The API reference, guides and the ideas hub are all self-serve.