MiGrid is an open-source, enterprise-grade operating system designed to transform electric vehicle fleets from simple transportation assets into active, revenue-generating participants in the energy grid.
Our unified 11-layer platform spans from the physics of energy transfer to the tokenization of grid-supportive actions, enabling fleets to participate in wholesale energy markets, demand response programs, and Vehicle-to-Grid (V2G) operations.
MiGrid is an open-source, vertically integrated operating system designed to bridge the gap between physical EV assets and digital energy markets. We enable fleets to turn parked vehicles into revenue-generating Virtual Power Plants (VPPs) through physics-verified, standards-compliant orchestration.
We do not trust the driver; we verify the physics.
- Verify the Physics: Every charging session is audited against a Physics Engine (L1) that compares energy dispensed vs. battery capacity with a strict
<15%variance threshold. - Unlock the Grid: We don't just consume energy; we manage it. Our stack is built for OpenADR 3.0 compliance, turning load shedding and price signals into automated fleet actions.
- Tokenize Value: Grid-supportive behaviors are measured, verified, and rewarded directly to the driver's wallet via our Token Bridge (L10).
MiGrid is built on a streamlined, high-precision architecture designed for the realities of critical infrastructure. Our engineering principles prioritize physics verification, low-latency data processing, and uncompromising security.
- Physics-First Verification (L1): We do not trust digital signals blindly. All energy transactions are validated against a proprietary Physics Engine that audits charging sessions using "Digital Twin" models to detect anomalies and enforce capacity limits.
- Real-Time, Low-Latency Data: The platform utilizes Redis for sub-millisecond state caching and Apache Kafka for event streaming, enabling real-time responsiveness for frequency regulation (<500ms) and high-frequency market bidding.
- Edge-to-Cloud Resilience: Our Edge Runtime ensures site-level orchestration and mesh networking continue seamlessly even without cloud connectivity ("The Fuse Rule"), supported by a Multi-Region Active-Active cloud deployment for global resilience.
We leverage a modern, cloud-native stack to ensure scalability and adherence to global energy standards:
- Infrastructure as Code: Fully containerized deployments via Docker and Kubernetes, managed with Terraform.
- Data Layer:TimescaleDB for high-fidelity time-series energy metrics and PostgreSQL for relational core data.
- Security & Compliance: Built on a Zero-Trust Architecture with mTLS everywhere. We strictly adhere to NERC CIP and IEC 62351 cybersecurity standards.
- Interoperability: Native support for OpenADR 3.0 (VEN), OCPP 2.1 (Native V2G/V2X), OCPP 2.0.1 (Legacy Smart Charging), and ISO 15118 (Plug & Charge).
The system is decoupled into eleven distinct functional planes to separate concerns between physics, markets, data science, and user experience.
| Layer | Service | Description | Standards |
|---|---|---|---|
| L1 | physics-engine | The "Green Audit" — verifies kWh dispensed vs received. | PL/pgSQL |
| L2 | grid-signal | Virtual End Node (VEN) for utility communication. | OpenADR 3.0 |
| L3 | vpp-aggregator | Aggregates EVs & BESS for wholesale markets. | IEEE 2030.5 |
| L4 | market-gateway | Arbitrage engine for CAISO, PJM, and Nord Pool. | FIX / OASIS |
| L5 | driver-dx | Smart routing, voice commands, and availability. | GraphQL |
| L6 | engagement | Achievement-based driver behavior shaping. | WebSocket |
| L7 | device-gateway | Hardware abstraction for chargers. | OCPP 2.1 / 2.0.1 / ISO 15118 |
| L8 | energy-manager | Edge-ready dynamic load management (DLM). | Modbus TCP |
| L9 | commerce-engine | Flexible billing, tariffs, and split-billing. | Stripe / OCPI |
| L10 | token-bridge | Rewards and staking via Open-Wallet. | ERC-20 / Polygon |
[I] Verify the Physics "Verify the physics. Unlock the grid." Every charging session is audited to ensure energy dispensed matches energy received (<15% variance threshold). | [II] Unlock the Grid "The Grid is a partner, not just a plug." Active site load management, utility signal response, and grid stability prioritization. | [III] Tokenize Everything "Every electron must be a tokenized asset." Grid-supportive actions are measured, valued, and rewarded through Web3 incentives. |
[▸] Full-Stack V2G/VPP Control
Built from the ground up to support FERC Order 2222, enabling fleets to:
- Aggregate EVs into 100kW+ Virtual Power Plants (VPPs)
- Bid into wholesale energy markets (CAISO, PJM, ERCOT)
- Participate in demand response programs
- Generate revenue from grid services
[▸] Fintech-Grade Ledger
Treats every kilowatt-hour and dollar as a high-precision asset:
- PostgreSQL with TimescaleDB for time-series data
- Decimal.js for zero rounding errors
- Complete financial audit trail
- Real-time settlement reconciliation
[▸] Tokenized Driver Incentives
Built-in Web3 rewards system via Open-Wallet Framework:
- ERC-20 tokens on Polygon
- Reward drivers for grid-friendly behavior
- Smart charging bonuses
- V2G participation rewards
- Gamification and leaderboards
[▸] Hardware Agnostic
Universal hardware abstraction layer:
- OCPP 2.1 (Flagship) & 2.0.1 support
- OCPP 1.6 legacy support
- OCPP 2.1 (Native V2X), 2.0.1 & 1.6 support
- ISO 15118 Plug & Charge (in progress)
- V2G bidirectional control
- No vendor lock-in
graph TB
subgraph "Application Layer"
L5[L5: Driver Experience]
L6[L6: Engagement Engine]
end
subgraph "Intelligence Layer"
L11[L11: ML Engine]
L3[L3: VPP Aggregator]
end
subgraph "Market Layer"
L4[L4: Market Gateway]
L2[L2: Grid Signal]
end
subgraph "Infrastructure Layer"
L1[L1: Physics Engine]
L7[L7: Device Gateway]
L8[L8: Energy Manager]
end
subgraph "Business Layer"
L9[L9: Commerce Engine]
L10[L10: Token Engine]
end
[≡] View Full Service Matrix
| Layer | Service | Description | Port | Status |
|---|---|---|---|---|
| L1 | Physics Engine | Energy variance validation (<15% threshold) | 3001 | v10.1.6 |
| L2 | Grid Signal | OpenADR 3.0 VEN for demand response | 3002 | v2.5.6 |
| L3 | VPP Aggregator | Fleet capacity aggregation for markets | 3003 | v3.3.2 |
| L4 | Market Gateway | CAISO/PJM/ERCOT wholesale integration | 3004 | v3.8.8 |
| L5 | Driver Experience API | Mobile backend, auth, smart routing | 3005 | v4.1.0 |
| L6 | Engagement Engine | Gamification, leaderboards, achievements | 3006 | v5.17.0 |
| L7 | Device Gateway | OCPP 2.1, ISO 15118, V2X control | 3007 | v5.12.0 |
| L8 | Energy Manager | Dynamic Load Management (DLM) | 3008 | v2.1.0 |
| L9 | Commerce Engine | Billing, tariffs, split-billing | 3009 | v5.1.0 |
| L10 | Token Engine | Web3 rewards via Open-Wallet | 3010 | v4.3.8 |
| L11 | ML Engine | AI forecasting, predictive maintenance | 3011 | v0.5.0 |
Backend & Infrastructure
| Frontend & Mobile
|
AI & Machine Learning
| Standards & Protocols
|
Scenario: Charge 50 vehicles by 6 AM at lowest cost Solution:
| Scenario: Grid operator needs demand response Solution:
|
Scenario: Incentivize off-peak charging behavior Solution:
| Scenario: Driver charges fleet vehicle at home Solution:
|
# Required
[✓] Docker & Docker Compose
[✓] Node.js 18+
[✓] Git
# Optional (for development)
[*] PostgreSQL 15+ client
[*] Kubernetes (for production)# Clone and start
git clone https://github.com/dcplatforms/Migrid.git &&cd migrid
docker-compose up --build[▸] Step-by-Step Installation
# Main MiGrid platform
git clone https://github.com/dcplatforms/Migrid.git
# Open-Wallet service (for token rewards)
git clone https://github.com/ThomasC3/open-wallet.git
# Directory structure:# ./# ├── migrid/# └── open-wallet/cd migrid
# Start infrastructure
docker-compose up -d postgres redis kafka zookeeper
# Run migrations
docker exec -i migrid-postgres-1 psql -U migrid -d migrid_core < scripts/migrations/001_init_schema.sql
# Seed demo data
npm install
node scripts/seed-data.js# Start entire platform
docker-compose up --build
# Or start specific services
docker-compose up physics-engine vpp-aggregator market-gateway# Health check all servicesforportin 3001 3002 3003 3004 3005 3006 3007 3008 3009 3010;do
curl -s http://localhost:$port/health | jq
done| Service | URL | Description |
|---|---|---|
| Admin Portal | http://localhost:5173 | Fleet management dashboard |
| Driver API | http://localhost:3005 | Mobile app backend |
| VPP Aggregator | http://localhost:3003 | Capacity management |
| Market Gateway | http://localhost:3004 | Trading operations |
| Energy Manager | http://localhost:3008 | Load monitoring |
Email: alice@demo.com
Password: demo123
Full deployment guide: See DEPLOYMENT.md for production setup
Version 10.1.6 • May 2026 • 84% Complete
Phase 1: Foundation ████████████████████ 100% [✓] Q1 2025
Phase 2: Grid Integration ████████████████████ 100% [✓] Q2 2025
Phase 3: Market Access ████████████████████ 100% [✓] Q3 2025
Phase 4: Driver Experience ████████████████████ 100% [✓] Q4 2025
Phase 5: Enterprise Scale ████████████████████ 100% [✓] Q1 2026
Phase 6: AI & Optimization ████████████░░░░░░░░ 60% [ ] Q2 2026
Phase 7: Global Expansion ░░░░░░░░░░░░░░░░░░░░ 0% [ ] Q3 2026
Phase 8: Advanced Grid ░░░░░░░░░░░░░░░░░░░░ 0% [ ] Q4 2026
[≡] View Detailed Roadmap
| Phase | Quarter | Focus | Status |
|---|---|---|---|
| 1 | Q1 2025 | Physics verification, Energy Manager MVP | Complete |
| 2 | Q2 2025 | OpenADR 3.0, Telematics bridges | Complete |
| 3 | Q3 2025 | VPP aggregation, Wholesale markets | Complete |
| 4 | Q4 2025 | Mobile app, Token ecosystem | Complete |
| 5 | Q1 2026 | Commerce engine, ISO 15118, Global markets | Complete |
| 6 | Q2 2026 | ML forecasting, Predictive analytics | In Progress |
| 7 | Q3 2026 | Multi-tenant, International markets | Planned |
| 8 | Q4 2026 | Frequency regulation, Resilience | Planned |
Interactive Roadmap:View roadmap.html • Detailed Status
| Document | Description |
|---|---|
| README.md | This file - platform overview and quick start |
| DEPLOYMENT.md | Complete deployment guide with examples |
| PLATFORM_STATUS.md | Detailed progress tracking and metrics |
| docs/roadmap.md | Full roadmap with technical specifications |
| docs/roadmap.html | Interactive visual roadmap |
| Service READMEs | Individual service documentation |
MiGrid is governed by a Technical Steering Committee (TSC). Major architectural changes require an RFC (Request for Comments).
- Read the Architecture Documentation
- Review the Roadmap
- Include physics constraint unit tests
- Follow safety invariants (e.g., "Never discharge BESS below 20%")
- Submit PR with detailed testing plan
Apache 2.0 License • Copyright © 2025-2026 MiGrid Contributors
See LICENSE for full details.
- Repository:https://github.com/dcplatforms/Migrid
- Issues:https://github.com/dcplatforms/Migrid/issues
- Roadmap:Interactive HTML Version
- Discussions:GitHub Discussions
MiGrid: Powering the Future of Sustainable Fleet Electrification
Built by the open-source community
