Trucking software

// The problem

A carrier with several terminals collects pre-trip inspection reports on paper, defects reach the shop days late, and preventive maintenance is tracked in a spreadsheet nobody trusts.

// What we would build

A driver app for iOS and Android for daily inspections with photos and defect notes, defects that become shop work orders automatically, and preventive maintenance scheduled from odometer and engine hours read from your ELD provider's published API. We build to the inspection checklist your maintenance manager sets.

// What is in it

// Stack

• Next.js
• React Native
• PostgreSQL
• ELD provider API
• AWS Canada

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

// Stack

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

// The problem

A carrier settles its owner-operators from an Access database a former employee built, and every fuel advance, deduction and escrow question waits for the one person who knows it.

// What we would build

We start with an architecture review of the old database and write up what it really does, so you decide with the facts. Then a web system replaces it: loads, rates, fuel advances, deductions and escrow, weekly statements in an owner-operator portal, and settlements posted to QuickBooks Online through its API.

// What is in it

// Stack

• Next.js
• PostgreSQL
• QuickBooks Online API
• DigitalOcean Toronto

// The problem

A carrier takes driver applications by phone and paper forms, chases licences and abstracts by email, and keeps qualification records in folders that drift out of date.

// What we would build

A careers site and application flow designed with drivers for a phone, in English, French and Punjabi, with document uploads and consent, an onboarding checklist per hire, and driver files that warn before a licence, medical or training record expires. The checklist is the one your safety manager sets.

// What is in it

// Stack

• Next.js
• PostgreSQL
• S3-compatible storage
• Figma
• AWS Canada

// The problem

Drivers report incidents by phone hours later, details are lost, and staff dig through a thick safety manual and past reports to answer the same questions.

// What we would build

An incident report in the driver app with photos, location and the ELD data around the time, and an assistant that answers staff and driver questions from your own safety manual and policies, citing the section. It runs on an open-source model in your own cloud account so driver and incident records stay private.

// What is in it

// Stack

• Llama or Mistral (open-source)
• vLLM
• PostgreSQL with pgvector
• React Native
• AWS GPU

// The problem

Trailers change hands between carriers, drayage partners and yards, and when damage turns up nobody agrees on who had the trailer or what state it was in.

// What we would build

An Android app that records each interchange with photos, seal numbers and both parties' sign-off, with each record fingerprinted on a private permissioned ledger that every carrier and yard runs a node of. A signed PDF with photos often does this job; the ledger helps when several companies share one record and none wants another to hold it.

// What is in it

// Stack

• Next.js
• Kotlin for Android
• Hyperledger Besu (private, permissioned)
• PostgreSQL
• AWS Canada

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

// Stack

• Node.js
• PostgreSQL
• OpenAPI
• Terraform
• AWS Canada