labs@atheron:~/industries/clean-energy/apps$ build app --web --mobile

EV charging apps

A charging platform and driver app on open protocols.

Charging networks and renewable portfolios grow by adding hardware from whichever maker had stock. We build the software that stays the same while the hardware changes: open protocols to the chargers, APIs to the inverters, and billing that follows the meter.

Start a project See the example projects

// what matters here

What is different in this industry.

Open protocols, any charger

OCPP 1.6 and 2.0.1 to the chargers and OCPI to roaming partners, so you can change charger makers without changing your platform. Each model is tested on the bench before it goes live.

Drivers who can actually pay

Start and pay in the app, through a processor's hosted checkout, so card data stays out of your systems and a frozen card reader does not end a session.

Billing that follows the meter

Community solar credits and power purchase invoices built from metered production, with every adjustment logged for the member or offtaker who asks.

Deadlines that cannot slip

Interconnection studies, deposits and utility replies tracked against each project, with reminders before every date.

// example projects

Priced examples for this service.

Each one is hypothetical, labelled as such, and priced live from our rate card. Open any of them in the estimator and make it yours.

Example projectWeb appMobile app

EV charging and a driver app

Hypothetical. Not a client, not a result.

// The problem

A charge point operator runs chargers from several makers through their separate portals, cannot offer roaming, and drivers pay with a card reader that fails in the cold.

// What we would build

A charging station management system speaking OCPP 1.6 and 2.0.1 to every charger, OCPI roaming with other networks, and an iOS and Android driver app to find a charger, start a session and pay, with pricing and faults managed from one web console.

// What is in it

OCPP 1.6 and 2.0.1 for chargers from several makers, tested model by model
Live status, sessions, faults and remote resets in one console
Driver app to find, reserve, start and pay, in English and French
OCPI roaming so drivers from partner networks can charge, and yours can roam
Pricing by time, energy and idle time, with payments through a processor's hosted checkout

// Stack

Node.js OCPP server
OCPI 2.2.1
React Native
Next.js
PostgreSQL
AWS

// estimate

Build: ≈ US$179,000 to US$273,000, delivered within 39 weeksCAD 254,500 to 389,300
Hosting: ≈ US$492 a monthCAD 700 a month
Support: ≈ US$5,010 a monthCAD 7,135 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 3.5 to 4 weeks
Design approved: 12.5 to 22 weeks
Core features: 3 to 4 weeks
Full build: 1.5 to 3 weeks
First build on devices: 5 to 8 weeks
Testing and fixes: 1 week
Store submission: 1 to 2.5 weeks
Launch: 1 to 1.5 weeks

Outside our hands, and added to the calendar

App store review: 1 week
Test chargers on the bench: 2 to 6 weeks
Roaming hub or partner onboarding: 1 to 4 weeks

How it is paid

Deposit 20%: CAD 50,900 to 77,860
Discovery 9.2%: CAD 23,414.00 to 35,815.60
Design approved 9.2%: CAD 23,414.00 to 35,815.60
Core features 7.6%: CAD 19,342.00 to 29,586.80
Full build 5%: CAD 12,725 to 19,465
First build on devices 20.1%: CAD 51,154.50 to 78,249.30
Testing and fixes 2.5%: CAD 6,362.50 to 9,732.50
Store submission 6.7%: CAD 17,051.50 to 26,083.10
Launch 9.7%: CAD 24,686.50 to 37,762.10
Holdback, 30 days after launch (10%): CAD 25,450 to 38,930

Start from this example

Example projectWeb app

Community solar billing portal

Hypothetical. Not a client, not a result.

// The problem

A community solar co-operative works out each subscriber's credits from meter exports in a spreadsheet, and members email to ask what they are owed.

// What we would build

A subscriber portal and a billing engine that allocates each month's production to subscribers by their share, issues statements, takes payments and posts invoices and payments to QuickBooks Online, built on the QuickBooks Online API.

// What is in it

Production read from the site's monitoring, month by month
Allocation to subscribers by share, with every adjustment logged
Member portal with statements, payments and production history
Invoices and payments synced both ways with QuickBooks Online
Waitlist and transfers when a member moves away

// Stack

Next.js
PostgreSQL
QuickBooks Online API
Payment processor's hosted checkout
DigitalOcean

// estimate

Build: ≈ US$96,600 to US$148,000, delivered within 26 weeksCAD 137,500 to 210,300
Hosting: ≈ US$176 a monthCAD 250 a month
Support: ≈ US$2,500 a monthCAD 3,565 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Data mapping and sandbox connection: 0.4 weeks
Design approved: 4.4 to 7.4 weeks
Core features: 1.9 to 3.4 weeks
Full build: 1.4 to 1.9 weeks
Sync built and reconciled in sandbox: 2.4 to 3.9 weeks
Testing and fixes: 0.4 to 0.9 weeks
Bills checked against a past month: 0.9 to 1.4 weeks
Launch: 0.9 to 1.4 weeks
Live cutover: 0.9 to 1.4 weeks
Hypercare: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

API keys from each maker or the SCADA owner: 1 to 4 weeks

How it is paid

Deposit 20%: CAD 27,500 to 42,060
Discovery 3.4%: CAD 4,675.00 to 7,150.20
Data mapping and sandbox connection 5%: CAD 6,875 to 10,515
Design approved 3.4%: CAD 4,675.00 to 7,150.20
Core features 10.3%: CAD 14,162.50 to 21,660.90
Full build 6.8%: CAD 9,350.00 to 14,300.40
Sync built and reconciled in sandbox 15.1%: CAD 20,762.50 to 31,755.30
Testing and fixes 3.4%: CAD 4,675.00 to 7,150.20
Bills checked against a past month 8.7%: CAD 11,962.50 to 18,296.10
Launch 3.4%: CAD 4,675.00 to 7,150.20
Live cutover 5%: CAD 6,875 to 10,515
Hypercare 5.5%: CAD 7,562.50 to 11,566.50
Holdback, 30 days after launch (10%): CAD 13,750 to 21,030

Start from this example

Example projectWeb app

Interconnection pipeline tracker

Hypothetical. Not a client, not a result.

// The problem

A renewable developer tracks dozens of projects through utility interconnection queues in a spreadsheet and email, and misses a study deposit date.

// What we would build

A web app that holds each project's interconnection applications, studies, utility correspondence and deadlines, with reminders before every date and a pipeline view the whole team reads from.

// What is in it

Projects with sites, capacity, utility and queue position
Applications, studies and letters stored against each step
Deadlines and deposits with reminders to the right person
A pipeline view by stage, utility and region
Documents searchable across every project

// Stack

Next.js
PostgreSQL
S3-compatible storage
DigitalOcean

// estimate

Build: ≈ US$52,300 to US$80,000, delivered within 15 weeksCAD 74,500 to 113,900
Hosting: ≈ US$176 a monthCAD 250 a month
Support: ≈ US$1,000 a monthCAD 1,425 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Design approved: 2.9 to 4.4 weeks
Core features: 1.9 to 2.9 weeks
Full build: 1.4 to 1.9 weeks
Testing and fixes: 0.9 to 1.4 weeks
Launch: 0.9 to 1.4 weeks

How it is paid

Deposit 30%: CAD 22,350 to 34,170
Discovery 6.6%: CAD 4,917.00 to 7,517.40
Design approved 6.6%: CAD 4,917.00 to 7,517.40
Core features 20%: CAD 14,900 to 22,780
Full build 13.3%: CAD 9,908.50 to 15,148.70
Testing and fixes 6.6%: CAD 4,917.00 to 7,517.40
Launch 6.9%: CAD 5,140.50 to 7,859.10
Holdback, 30 days after launch (10%): CAD 7,450 to 11,390

Start from this example

// questions

Questions we get about this.

Which OCPP versions do you support?

OCPP 1.6 and 2.0.1, side by side. Chargers differ in how they read the standard, so we test each model on the bench and record what works.

Can our drivers roam on other networks?

Yes, through OCPI, directly with a partner network or through a roaming hub. Onboarding with a hub or partner is shown as a lead time.

Can community solar billing post to our accounting?

Yes. Invoices and payments sync with QuickBooks Online, built on its API, or with a larger system through its interfaces.

Back to the industry: Clean energy and EV charging About the service: Web and mobile apps

// next

Not quite your project?

Tell us what you have in mind. We will come back to you with a range and the questions that would narrow it. Or book a call and talk it through.

Start a project Book a call