# GridOS Pricing > Transparent pricing for OCPP 1.6, OCPP 2.0.1, and OCPP 2.1 gateway routing, OCPI 2.1.1, OCPI 2.2.1, and OCPI 2.3.0 roaming, multi-backend control, and ChargerPilot AI operations. Last updated: 2026-08-05 Canonical: https://gridos.co/pricing Markdown: https://gridos.co/pricing.md Contact: contact@gridos.co ## How to read this page GridOS pricing is scoped to charger estate size, routing complexity, and migration shape—not a generic SaaS seat count. Starter is for pilots; Growth is for live multi-system operations; Enterprise is for large estates and custom integrations. ## Plan tiers ### Starter — $0/month - CTA: Start Free ### Growth — $500/month - CTA: Start Growth ### Enterprise — custom pricing - CTA: Contact Us ## Feature matrix ### Connectivity | Feature | Starter | Growth | Enterprise | | --- | --- | --- | --- | | OCPP 1.6 support | Included | Included | Included | | OCPP 2.0.1 support | Not included | Included | Included | | Max chargers | 50 | 500 | Unlimited | | Concurrent connections | 100 | 2,000 | Unlimited | ### Routing & Migration | Feature | Starter | Growth | Enterprise | | --- | --- | --- | --- | | Single backend routing | Included | Included | Included | | Multi-backend parallel routing | Not included | Included | Included | | Automatic failover | Not included | Included | Included | | Protocol translation (HTTPS/MQTT) | Not included | Not included | Included | | Live migration with rollback | Not included | Included | Included | ### Roaming & Interoperability | Feature | Starter | Growth | Enterprise | | --- | --- | --- | --- | | OCPI 2.1.1 | Not included | Included | Included | | OCPI 2.2.1 | Not included | Included | Included | | Hub connections | 1 | Multi (Hubject, Gireve) | Unlimited | | Partner credential management | Not included | Included | Included | ### Operations & Monitoring | Feature | Starter | Growth | Enterprise | | --- | --- | --- | --- | | Real-time dashboard | Basic | Included | Included | | Session & CDR export | Included | Included | Included | | Alerting & anomaly detection | Not included | Included | Included | | Audit logging | Not included | Included | Included | ### Security & Compliance | Feature | Starter | Growth | Enterprise | | --- | --- | --- | --- | | TLS encryption | Included | Included | Included | | Role-based access control | Not included | Included | Included | | SSO / SAML | Not included | Not included | Included | | Custom security review | Not included | Not included | Included | ### Support | Feature | Starter | Growth | Enterprise | | --- | --- | --- | --- | | Community support | Included | Included | Included | | Priority email support | Not included | Included | Included | | Dedicated support manager | Not included | Not included | Included | | SLA guarantee | Not included | Not included | Included | ## What is included in the product - OCPP 1.6, OCPP 2.0.1, and OCPP 2.1 charger-facing gateway - OCPI 2.1.1, OCPI 2.2.1, and OCPI 2.3.0 roaming / partner exchange - Multi-backend routing and parallel sync patterns - ChargerPilot AI agents for OCPP and OCPI operations - Migration without a big-bang cutover ## Commercial notes - Starter ($0/month): evaluation and smaller estates (feature limits apply). - Growth ($500/month): production rollout, multi-hub routing, priority support. - Enterprise (custom): unlimited chargers, advanced failover, protocol translation, SLA. - Sales / architecture review: https://gridos.co/contact ## FAQ ### What is GridOS? GridOS is the infrastructure layer between chargers and downstream systems. It provides an OCPP gateway for the field, an OCPI gateway for roaming and partner exchange, multi-backend routing, and ChargerPilot AI agents that help operators manage sessions, exceptions, and protocol workflows without binding the fleet to a single CPMS. ### What is the OCPP gateway vs the OCPI gateway? The OCPP gateway is the charger-facing entry point: mixed fleets connect once, and GridOS normalizes traffic toward one or more backends. The OCPI gateway is the partner-facing layer for locations, tokens, sessions, tariffs, and CDRs with hubs or bilateral peers. Together they separate field control from roaming and commercial integrations. ### What is ChargerPilot? ChargerPilot is GridOS’s AI agent layer for OCPP and OCPI operations. Agents assist with load balancing, anomaly detection, tariff actions, roaming exception triage, and routine protocol tasks so ops teams can manage large fleets without living in raw message logs. ### Does GridOS replace our current CPMS or CSMS? Not necessarily. The OCPP and OCPI gateways can sit alongside an existing CPMS or CSMS so you can add routing, roaming, monitoring, and ChargerPilot agents before deciding whether a full replacement is necessary. ### Which OCPP and OCPI versions do you support? Production connectivity is built for OCPP 1.6, OCPP 2.0.1, and OCPP 2.1 on the charger side and OCPI 2.1.1, OCPI 2.2.1, and OCPI 2.3.0 for roaming and partner interoperability. Version choice still depends on your charger firmware and which partners you connect to live. ### When is this most useful? It is most useful when you have mixed charger fleets, roaming requirements, backend migration risk, or a need for AI-assisted OCPP/OCPI operations while preserving your own operational visibility and data. ### Can we run multiple systems in parallel? Yes. That is one of the main reasons to use the gateway layer. Operators can keep a live operational view and ChargerPilot agents while validating a new backend, partner, or routing model instead of forcing a single cutover event. ### Does this help with migration risk? Yes. You stabilize the OCPP field layer first, then move OCPI partners and backends in controlled phases. ChargerPilot helps surface anomalies during each wave instead of turning migration into a fleet-wide field change. ### Who is the buyer? Usually CPOs, eMSPs, platform teams, or operators responsible for charger connectivity, OCPI roaming, backend modernization, and the operational consequences of protocol or partner changes. ### Do we need to replace charger hardware? The goal is usually the opposite: reduce hardware-side changes by moving control into a stable OCPP gateway. Exact steps still depend on charger estate, firmware quality, and how the current backend and OCPI partners are wired. ### Does GridOS support regional standards and global markets (US NEVI, EU AFIR, UK, APAC)? Yes. GridOS is architected for global CPOs and eMSPs operating across North America, Europe, the UK, and APAC. It supports regional compliance requirements including EU AFIR ad-hoc payment roaming, US NEVI uptime reporting, and UK regulations through normalized OCPI 2.2.1/2.3.0 modules and automated ChargerPilot audit logs. ## Related links - [Pricing page (HTML)](https://gridos.co/pricing) - [llms.txt](https://gridos.co/llms.txt) - [llms-full.txt](https://gridos.co/llms-full.txt) - [OCPP guide](https://gridos.co/ocpp) - [OCPI guide](https://gridos.co/ocpi)