labs@atheron:~/industries/trucking/cloud$ deploy --managed --monitored

Fleet cloud operations

Your fleet systems run, watched and backed up.

Fleet systems are only useful if they are up when the trucks roll. We set up the cloud they run in as code, watch it, back it up and look after it, so a broken connection is fixed before dispatch notices.

Start a project See the example projects

// what matters here

What is different in this industry.

In your account

Everything runs in a cloud account you own, so you can move it or hand it to someone else.

Set up as code

Infrastructure is written down in Terraform, so it can be rebuilt the same way.

Watched and backed up

Monitoring, alerts and tested backups for the hub, the warehouse and the apps.

A runbook you keep

What to do when a provider's API changes or a job fails, written down.

// 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 projectAPI

Fleet integration hub

Hypothetical. Not a client, not a result.

// The problem

A fleet's ELD, fuel card, shop software, dispatch system and payroll are joined by staff copying numbers between them, and the scripts someone wrote stop without telling anyone.

// What we would build

An internal API that connects five systems through their published APIs, moves odometer readings, fuel purchases, work orders and hours where they are needed, and sends webhooks when something changes. We run it on managed cloud with monitoring, backups and alerts, so you know when a provider's API changes.

// What is in it

Connectors for ELD, fuel card, shop, dispatch and payroll systems
Webhooks when a unit, a work order or a fuel purchase changes
Monitoring, alerts and retries when a provider is down
Infrastructure as code, backups and a written runbook
OpenAPI documentation for anything else you connect later

// Stack

Node.js
PostgreSQL
OpenAPI
Terraform
AWS Canada

// estimate

Build: ≈ US$56,700 to US$86,800, delivered within 14 weeksCAD 80,800 to 123,600
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

API contract agreed: 2.9 to 3.9 weeks
Core resources built: 2.9 to 4.4 weeks
Security, gateway and connections: 1.9 to 2.9 weeks
Docs, SDKs and load tests: 1.4 to 1.9 weeks
Launch and first callers: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

API access from each ELD and telematics provider: 1 to 4 weeks

How it is paid

Deposit 20%: CAD 16,160 to 24,720
API contract agreed 8.7%: CAD 7,029.60 to 10,753.20
Core resources built 26.2%: CAD 21,169.60 to 32,383.20
Security, gateway and connections 17.5%: CAD 14,140 to 21,630
Docs, SDKs and load tests 8.7%: CAD 7,029.60 to 10,753.20
Launch and first callers 8.9%: CAD 7,191.20 to 11,000.40
Holdback, 30 days after launch (10%): CAD 8,080 to 12,360

Start from this example

Example projectWeb app

Fleet data warehouse

Hypothetical. Not a client, not a result.

// The problem

A private fleet's ELD, telematics, fuel card and shop data sit in separate portals, and fuel tax mileage by province and state is rebuilt by hand every quarter.

// What we would build

A data warehouse that pulls from each portal's published API every night, checks the numbers, and feeds dashboards for cost per kilometre, idle time, fuel economy and maintenance spend by unit. Distance and fuel by jurisdiction are prepared for the person who files your fuel tax returns to review. We do not give tax advice.

// What is in it

Nightly loads from ELD, telematics, fuel card and shop systems
Quality checks that flag missing days, odd readings and duplicate fuel purchases
Dashboards by unit, terminal and driver group
Distance and fuel by province and state, prepared for review before filing
Exports your accountant can open

// Stack

PostgreSQL
dbt
Metabase or a dashboard we build
Provider APIs
AWS Canada

// estimate

Build: ≈ US$65,000 to US$99,500, delivered within 16 weeksCAD 92,600 to 141,700
Hosting: ≈ US$492 a monthCAD 700 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
Design approved: 2.4 to 3.9 weeks
Core features: 2.4 to 3.4 weeks
Full build: 1.4 to 2.4 weeks
Testing and fixes: 0.9 weeks
Fuel tax data reconciled against a past quarter: 0.9 weeks
Launch: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

API access from each ELD and telematics provider: 1 to 4 weeks

How it is paid

Deposit 20%: CAD 18,520 to 28,340
Discovery 6.8%: CAD 6,296.80 to 9,635.60
Design approved 6.8%: CAD 6,296.80 to 9,635.60
Core features 20.4%: CAD 18,890.40 to 28,906.80
Full build 13.6%: CAD 12,593.60 to 19,271.20
Testing and fixes 6.8%: CAD 6,296.80 to 9,635.60
Fuel tax data reconciled against a past quarter 8.7%: CAD 8,056.20 to 12,327.90
Launch 6.9%: CAD 6,389.40 to 9,777.30
Holdback, 30 days after launch (10%): CAD 9,260 to 14,170

Start from this example

// questions

Questions we get about this.

Where is our fleet data hosted?

In Canada by default, in a cloud account you own. If you need another region, the estimator asks where.

Can our own IT team take over fleet hosting later?

Yes. The infrastructure is code and the runbook is yours.

Do we need managed operations for one small fleet app?

Not always. A small app on simple hosting may only need essential support. We will say which fits.

Back to the industry: Trucking and fleet operators About the service: Cloud, DevOps and operations

// 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