About
Built in a station, not in a boardroom.
OpsBrio started as the software one Amazon DSP wrote for itself. It ran two stations for months before it was offered to anybody else, and it is still what those stations use every morning.
Where it came from
A DSP runs on a spreadsheet until it can’t. Ours was a roster tab, a van tab, a third-party tool for the bits neither covered, and a group text holding the whole thing together. Nothing was wrong with any one of them. What was wrong was that the schedule did not know about the vans, the vans did not know who was driving them, and the answer to “can this person work Saturday” lived in someone’s head.
So we built the board we actually wanted, one module at a time, in the order the day happens: roster a week, dispatch it, put the fleet behind it, then the parts nobody enjoys — hours against the rolling seven-day window, the injury log, the write-ups, hiring. Every one of them shipped because a real morning went badly without it.
The result is a product with an unusual shape. It is opinionated about things most software is vague about — that a shift is not a wave, that a van’s VIN is its identity and its number is only a label, that Amazon evaluates a rolling seven days and not a calendar week — because getting those wrong cost us something real first.
- Two stations
- Run on it daily, one of them opened on it from its first board.
- ~150 drivers
- Each with their own login, seeing their own day and nobody else’s.
- 11 modules
- Plus the drivers’ app. No tier, no add-on: a station gets all of it.
- Used before sold
- It was the system of record for a live operation before it had a price.
What that buys you
The awkward parts are the point.
- It starts before the drivers do
- The desk is in by six on a Cycle 0 morning, with a board to build before anybody arrives. Dense screens, big tap targets, dark by default and light when you want it — decisions made for a cheap phone in a cold yard, not for a demo.
- The edge cases are built
- A driver at two stations. A van that changes yards and changes name. A suspension that is days, not months. These are not roadmap items here; they are Tuesday.
- Short way to a change
- The people who build it dispatch on it. When something is wrong on a Monday it is usually wrong for us too, which is the fastest bug report there is.
What OpsBrio is not
It is not an Amazon product. OpsBrio is not affiliated with, endorsed by or connected to Amazon. “Amazon” and its product names belong to Amazon, and are used here only to say what this software works alongside.
It does not replace Cortex. Amazon’s tools stay where they are. OpsBrio reads what your dispatcher can already see, in their own signed-in session, and never asks for an Amazon password.
It is not payroll, and it is not your accountant. It will tell you hours paid against hours clocked and where a bonus lands, and then hand you the numbers. Money leaves the building somewhere else.
It is not a data business. Your company runs on its own database at its own address. Nothing is pooled with another DSP, nothing is sold, and the records are yours to take with you if you leave.
Next
See the screens before you decide.
Every module, photographed from a real station on an ordinary week.