The vehicle-first orchestration layer for electric fleets.
TOGL is being built to connect supported vehicle data, charging context, operational rules, tariffs, and future flexibility signals into one software layer.
Discuss platformOn vehicle-to-grid.
TOGL delivers value today through smart charging, depot load management, and demand shifting. That is where the addressable value is now, and it requires no additional hardware.
The platform is architected for bidirectional flow, and we will support V2G when vehicle availability, charger certification, and market access make it commercially viable at fleet scale.
We do not sell V2G revenue that does not yet exist.
Platform overview
Inputs
Vehicles & telematics
Chargers & CPMS
Fleet rules & departure times
TOGL
Orchestration & Optimisation
Readiness-first.
Cost-aware.
Grid-ready.
Outputs
Optimised charge schedule
Flexibility signal
Readiness protected
One layer between vehicles, charging, and energy.
TOGL is being built to sit between electric vehicles, charging operations, fleet requirements, and energy market signals. The aim is to optimise charging decisions while protecting operational readiness.
Data inputs
What the platform can use.
Vehicle state of charge
Charging status
Location context
Fleet readiness rules
Tariff signals
Site and substation capacity
Flexibility signals where available
Charger or platform data where integrations exist
Availability depends on supported integrations, permissions, and asset type.
Integrations
How TOGL connects to what a depot already runs.
Integration is partner-led rather than vendor by vendor, and coverage is confirmed against a specific site rather than published as a compatibility list. Checking it takes one enquiry.
Partner-led by design
TOGL integrates through partners rather than building a direct connector to every vendor. Supported passenger vehicle integrations are live, and the current brand list is available on request.
Coverage confirmed per site
What is reachable at a depot depends on the vehicles, chargers and charge point management system it actually runs, so TOGL checks coverage against the site rather than inferring it from a vendor name.
No new hardware
Smart charging, depot load management and demand shifting require no additional hardware. Charger or platform data is used where an integration exists.
Send the vehicles, chargers and charge point management system a depot runs, and TOGL will confirm what is supported today and what would need an integration partner.
Request a coverage checkGrid connection intelligence
How many vehicles will this depot actually take?
Most operators cannot answer that question for their own sites, and the connection is what holds electrification up. Not vehicle availability, and not charger cost.
Actual headroom at the serving substation
Not the figure on the connection agreement, and not a regional average. The capacity available at the specific substation feeding the depot.
Vehicles supported before an upgrade
How many vehicles the site can charge on today's connection, given the duty cycles and departure times it actually runs.
How much upgrade can be deferred
The share of a connection upgrade that load management removes the need for, and how long that defers the capital spend.
What it is built from
Substation capacity data
Available headroom at the substation actually serving the site, rather than a nominal figure from the site's own connection agreement.
HGV operator licence data
Where heavy fleets are authorised to operate from, and at what vehicle count, which is what determines the load a depot will eventually need.
Spatial analysis
Depot locations matched to the network serving them, so the answer is specific to a site rather than to a region.
Orchestration logic
How TOGL thinks.
Understand vehicle readiness
Check operational constraints
Identify charging flexibility
Avoid unnecessary peak demand
Optimise charging windows
Prepare assets for future flexibility participation
Current & roadmap
What we have, what we’re building.
Every capability below carries one of three statuses, and nothing is described as shipped unless it is.
Capability
Status
Notes
Supported passenger vehicle integrations
Supported OEM brands via integration partners. Current list available on request.
Fleet charging intelligence
Built around operational guardrails and charging context
Depot optimisation
Depends on site data, vehicle data, and charging data
Grid connection intelligence
Substation headroom, vehicles supported before upgrade, and how much of that upgrade load management can defer
eHGV support
In active development for depot orchestration. Vehicle data access depends on OEM API availability
Bus support
Depends on OEM API availability and heavy vehicle integration maturity
Flexibility market participation
Depends on market access, asset eligibility, and aggregator relationships
Vehicle-to-grid (bidirectional) flow
Architected for, not sold. Gated on vehicle availability, charger certification, and market access
What the status labels mean
- Live
- In production with customers or pilot users today.
- In development
- Actively being built, with a target window.
- Planned
- On the roadmap, dependency-gated, no committed date.
Architecture
How the layer sits.
Vehicle data
SoC, location, charging status
TOGL orchestration layer
Rules engine, optimisation logic
Fleet rules
Readiness, constraints, site limits
Charging decisions
Optimised schedule output
Reporting & partner workflows
Data, signals, flexibility
Vehicle data
SoC, location, charging status
TOGL orchestration layer
Rules engine, optimisation logic
Fleet rules
Readiness, constraints, site limits
Charging decisions
Optimised schedule output
Reporting & partner workflows
Data, signals, flexibility
Security & permissions
Built around permissioned data access.
Access to vehicle and site data is permissioned per organisation, and the failure mode is charging, not stranding: if TOGL cannot reach a vehicle or charger, the site falls back to charging in line with the duty cycle it has to meet. Optimisation is what degrades, never readiness, and never your uptime depending on ours. The exception cases and the override path are set out on the drivers page.
What is true today about hosting, sub-processors, certifications and vulnerability reporting is stated plainly on the security page.
Permissioned access
Data access is granted by users and operators with explicit permission scopes.
Governance by design
Security and governance are design requirements, not add-ons.
User control
Fleet operators retain control over what data is shared, with whom, and for what purpose.
Commercial model
How TOGL is bought.
TOGL publishes no rate card. Terms depend on fleet size, vehicle type, integration scope and which flexibility services a site can access, so pricing is agreed per deployment and discussed directly. A depot fleet operator typically engages under a revenue share, and early access pilots carry no licence fee.
Revenue share
TOGL participates in the value created from flexibility activity alongside asset owners and energy partners.
API licensing
An integration layer for partners, aggregators and energy market participants.
Enterprise partnerships
OEM, fleet, infrastructure and energy partner arrangements across the commercial ecosystem.
Flexibility market participation is a planned capability, so any share of flexibility value carries the same dependencies as the capability table above: market access, asset eligibility, and aggregator relationships.
Explore technical integration.
Send the vehicles, chargers and charge point management system your depot runs, and TOGL will tell you what is supported today and what needs an integration partner.
Discuss platformFAQ
How the platform works
How does TOGL decide when a vehicle charges?
TOGL treats departure readiness as a constraint on the optimiser rather than as one of its outputs. The platform takes vehicle state of charge, charging status, the depot's readiness rules and departure times, site and substation capacity, and tariff signals, then schedules charging inside those limits so the cheapest plan that still meets every departure is the one that runs.
What data does TOGL need from a fleet?
TOGL uses vehicle state of charge, charging status and location context, the fleet's own readiness rules and departure times, site and grid connection capacity, and tariff signals. Charger or charge point management system data is used where an integration exists. Vehicle data access depends on the manufacturer offering an API for that model.
Does TOGL support vehicle-to-grid (V2G)?
Not today. TOGL is architected for bidirectional flow but does not offer vehicle-to-grid, because it depends on vehicle availability, charger certification and flexibility market access that are not yet in place at fleet scale. TOGL will support V2G when those conditions make it commercially viable, and describes it as planned until then.
Which vehicles does TOGL support?
TOGL supports a range of passenger vehicle brands through integration partners, and the current list is available on request. Electric HGV support is in active development, and bus support is planned. Coverage for heavy vehicles is gated on manufacturers making vehicle data available through an API.
Will TOGL ever override a depot operator?
No. Depot operators set the readiness rules and keep the manual override, and TOGL optimises inside those constraints. A charging strategy that saves money and strands a vehicle has cost the operator more than it saved, which is why readiness rules take precedence over any price signal or dispatch instruction.
Where is fleet data stored, and who can see it?
Fleet data in TOGL is permissioned per organisation: a fleet's data is its own, and the fleet operator controls what is shared, with whom, and for what purpose. Enquiries submitted through the TOGL website are held in Brevo, which is the system of record for them, and the website itself operates no database. Hosting, sub-processors, certification status and vulnerability reporting are stated on the TOGL security page, and platform-specific data flows are available to prospective partners under NDA.
Which chargers and fleet systems does TOGL work with?
TOGL integrates through partners rather than building a direct connector to every vendor, so coverage is confirmed against a specific site rather than published as a compatibility list. Supported passenger vehicle integrations are live and the current brand list is available on request. Charger or charge point management system data is used where an integration exists, and no additional hardware is required for smart charging, depot load management or demand shifting. Contact TOGL for a coverage check against the vehicles, chargers and charge point management system a depot actually runs.
What commercial models does TOGL offer?
TOGL is bought under one of three commercial shapes: revenue share, where TOGL participates in the value created from flexibility activity alongside asset owners and energy partners; API licensing, for partners, aggregators and energy market participants; and enterprise partnerships across OEM, fleet, infrastructure and energy channels. TOGL publishes no rate card, because terms depend on fleet size, vehicle type, integration scope and which flexibility services a site can access. Pricing is agreed per deployment and discussed directly.