Log inTalk to us

Starter apps

Start from a working app.

Open-source apps for each kind of charging business, built on the Ivora API. Open the live demo, then put your own name on it: your developers or a partner connect your Ivora project and payment provider and run it on your own website. The app, its data and its customers are yours.

Talk to usBrowse on GitHub
ivora-examples/installer-kitLive
Lugline demo home: On site. Plug in. Prove it.Lugline demo home: On site. Plug in. Prove it.

Lugline

Installer kit

For installers and hardware sellers: connect a charger, test it, and print a QR sticker for the site.

Uses: station provisioning, OCPP connection details, station status, remote operations

Open live demo of LuglineFork on GitHub: Lugline
ivora-examples/forecourt-checkoutLive
Fillbay demo home: Charge at the pump, pay your way.Fillbay demo home: Charge at the pump, pay your way.

Fillbay

Forecourt checkout

For fuel and convenience sites with DC fast chargers: drivers pay at the charger with a card and no app or account, or pay in the store like fuel, from a cashier console.

Uses: stations and connectors, tariffs, externally funded sessions, settlement reports, webhooks

Open live demo of FillbayFork on GitHub: Fillbay
ivora-examples/fleet-depotLive
Rotabay demo depot overview: site power held under a 150 kW cap.Rotabay demo depot overview at dawn: every vehicle ready, site power held under a 150 kW cap overnight.

Rotabay

Fleet depot

For fleet depots: RFID cards per driver, charging planned to finish by departure time, and cost per vehicle.

Uses: RFID authorization, charging sessions, meter values, bills, webhooks

Open live demo of RotabayFork on GitHub: Rotabay
ivora-examples/cpo-starter-kit
Ampleaf overview from the starter kit, with sample data: sites, chargers online, connectors and charging now.Ampleaf overview from the starter kit, with sample data: sites, chargers online, connectors and charging now.
Coming soon

Ampleaf

CPO starter kit

For small charging operators with no developers on staff: fork it, put your own name on it, connect your Ivora project and run your network from one place.

Follow on GitHub: Ampleaf
ivora-examples/emsp-starter
eMSP starter: a phone screen of the driver app, with a map of sample chargers.eMSP starter: a phone screen of the driver app, with a map of sample chargers.

eMSP starter: Coming soon

Coming soon

eMSP starter

Driver app

For networks running their own driver app and payments.

Follow on GitHub: eMSP starter

Live demos run in demo mode: sample data, no keys, nothing charged and no charger contacted.

For your developers

Same conventions, every template.

Each template is a complete, deployable web app in its own folder, with its own README, CI and demo mode. Apache-2.0, so the fork is yours.

Stack

Next.js and TypeScript

Node.js 22, the Next.js App Router and npm. npm ci, npm run dev, and you are looking at the demo.

Safety

Keys stay on the server

Server-side API keys, one Ivora project per deployment, verified webhooks and idempotent writes.

Ownership

Your domain, your brand

QR codes on your own domain and a brand folder you replace. Apache-2.0, so the fork is yours.

Run a template on your own machine in demo mode

Run one locally

git clone https://github.com/Ivora-Charge/ivora-examples
cd ivora-examples/fleet-depot
npm ci
npm run dev  # demo mode: sample data, no keys
Node.js 22 · Next.js App Router · one folder per template

Your idea next

A charging business we haven't templated?

Propose a template or improve one. Every pull request runs the same checks.

Contribute on GitHubRequest API access