Platform

The architecture behind ihomer.

Four products, one platform. See how they fit together, from the charge point all the way to the roaming hub. Live data, animated.

Charge ManagementSmart ChargingRoamingGateway
01
Charge Management

The foundation, control & management

ihomer Charge Management is the core: a vendor-neutral CPMS that speaks to every OCPP-compliant charge point. Multi-tenant with strict data isolation. Operator portal, REST API, white-label customer app, billing module that connects directly to ERP systems.

Deep dive on this product
CPMS LAYERThe foundationOPERATOR · NORTH-BOUNDOPOperator portaldashboard · alertsAPIREST APIOpenAPI · webhooksUICustomer appwhite-label$$BillingCDR → ERPihomer CPMSControl & Management · Multi-tenantSSessionsremote start/stopCConfigurationtariffs · accessMMonitoringhealth · OTATMulti-tenantRBAC · ABACOCPPCHARGE POINT FLEET · SOUTH-BOUNDACAC chargersAlfen · EVBoxDCDC fastABB · KempowerHBHubsMulti-vendorHMHomeresidential
ihomer · CPMS · Control & Management
02
Smart Charging

The intelligence layer, SCSP

The Smart Charging Service Platform runs on top of ihomer Charge Management or any CSMS via open API. Ingests OpenADR, EPEX, MSP, PV/storage and vehicle SoC. A MILP/MPC optimizer computes OCPP charging profiles; load balancing happens real-time.

Deep dive on this product
INTELLIGENCESCSP · on top of CPMSCPMS LAYERThe foundationEXTERNAL SIGNALSDROpenADRDSO · grid limitsEPEXday-aheadMSMSPe-driver intentPVPV / Storagesolar · batteryEVVehicle SoCpriority · deadlineSCSP, Smart ChargingCore + Ingestion · Spring/ECSINIngestionREST · normaliseFCForecastload · price · weatherOPOptimizerMILP · MPCV2V2Gflex · batteryDIDriver intentAPI resolverOCPP Charging Profilesasync via SQS · live OCPP passthroughLBLoad bal.real-timeSTORE / UIDBPostgreSQLSCSP DB · CRUDSTOREUISCSP ManagerApp: Vue.jsAUKindeauth · SSOCRUDOCPP profiles · SQSihomer CPMS / CSMSor any CSMS via open APIOCPP gateway1.6 / 2.0.1Multi-tenantcontrol & managementOpen API3rd-party CSMSHub A · 2.0.1Depot B · 2.0.1Hub C · 1.6
ihomer · Smart Charging · SCSP
03
Roaming

The roaming layer, Broker

One OCPI integration, many hubs and eMSPs. Version translation 2.1.1 ↔ 2.2.1 ↔ 2.3, token handling, CDR routing and tariff management, all from one integrated stack. Hubject + Gireve + EVRoaming Foundation certified.

Deep dive on this product
ROAMINGBetween CPOs and eMSPsHJHubjectOICP 2.3 · CB-ILHUBOICPCPOACPO Back-Office AOCPI 2.2.1BCPO Back-Office BOCPI 2.1.1CCPO Back-Office COCPI 2.3Own auth & billingForwardRealtimeAuthihomer BrokerRoaming layerOCOCPI2.1.1 → 2.3OIOICP 2.3HubjectTCTokenscross-networkCDCDR routingbilling-gradePriority queues + webhookshi/med/lo · 30+ per-sub settingseMSP / HUBAeMSP Provider AOCPI 2.2.1BeMSP Provider BOCPI 2.2GVGireve NAProaming hub · FRToken & billing hubcharge passes · CDRs11K+ sessions/day · <10ms p99 · Hubject + Gireve certified
ihomer · Broker · Roaming layer
04
Gateway

The translation layer, Gateway

Between your charge points and your CPMS backend(s). Hot-standby uptime, OCPP translation between 1.5/1.6/2.0.1, smart routing for multi-backend scenarios, and zero-downtime migration without rip-and-replace.

Deep dive on this product
TRANSLATION LAYERBetween chargers and CPMSCHARGE POINTSLGCharge Point AOCPP 1.5 SOAPLEGACYJSCharge Point BOCPP 1.6 JSON / WS20Charge Point COCPP 2.0.1NEWMXMixed fleetvendor-mixAGAggregatormultiple CPOsLive OCPP streampassthroughihomer GatewayProtocol translation · Smart routingPTTranslate1.5 ↔ 1.6 ↔ 2.0.1SRSmart routemulti-backendMAMasterbidirectionalWRITERORead-onlymirror/auditREADAuth · Audit · Message lognormalised + replayMigration modemirror to candidate CSMSMASTERmirrorBACKENDSIHihomer CPMSmulti-tenantMASTERLGLegacy CPMS3rd-partyREADANFleet analyticsBI · dashboardsREADBIBilling engineCDR → ERPREADGRGrid operatorDSO interfaceREADCandidate CSMSmigration target
ihomer · Gateway · Translation layer

See it run?

30 minutes with a solution architect, concrete answers, no pitch.

Book a call