The platform
One stack, four layers, zero landlords.
The products look separate from the outside. Underneath they are one system, built in a deliberate order, each layer paying for the one above it.
Scroll sideways to see the whole system.
What is not on the diagram: What’s Cooking, MoneyBase, and Vacation Pics. Those are household products rather than trade tools, so they do not draw on the repair data layer. They run on the same framework, the same database, and the same machine as everything else.
The data layer
Labor times, torque specs, fluid capacities, diagnostic codes, and repair procedures for passenger vehicles from 1955 forward, plus the heavy-equipment and Class 7-8 equivalent. Free to read on the web, available through an API.
This exists because two vendors control automotive repair data and price it like a mortgage payment. Building our own took a long time and was worth every hour of it, because it is now the reason every product above it can include real repair content at no marginal cost.
The applications
ShopBase for independent auto repair, HeavyBase for equipment and diesel, Recon Desk for dealer used-car reconditioning. Three products, one spine: the same scheduling board, inspection engine, approval flow, and estimating core.
That shared spine is the only reason a team this size can maintain three vertical products. A fix in the inspection engine ships to all three. A new payment path is written once.
The infrastructure
Speech was the expensive one. Per-character text to speech and per-minute transcription look cheap until an AI service writer is answering every call for every shop, at which point somebody else's pricing page becomes your gross margin.
So the speech stack moved onto our own GPU. It now streams the voice that answers a shop's phone and narrates lessons for Cullinan Academy students, and the marginal cost of a conversation is the power bill.
The proving ground
Speedish Automotive is a working European repair shop in Danville, Indiana. BMW, Mercedes-Benz, Audi, Porsche. It has bays, customers, and a service advisor who will tell you exactly what he thinks of your new feature.
Software goes in there before it goes anywhere else. It is the difference between a product built from customer interviews and a product built from Tuesday morning.
The machine
Everything runs on one server, and we own it.
Not a serverless plan, not a managed platform, not a per-invocation bill that quietly follows your growth curve. A machine, in a rack, running Postgres and containers and a GPU, deployed by pushing to git.
It means nobody can deprecate a runtime out from under a customer, the cost of running a feature is knowable in advance, and shipping something generous is an engineering decision rather than a negotiation with a vendor.
The stack
- Framework
- Next.js, App Router, React
- Database
- PostgreSQL, self-hosted
- Deploys
- Git push, Coolify auto-build
- Speech
- Self-hosted TTS and STT on our GPU
- AI
- Anthropic Claude
- Comms
- Twilio voice and SMS, Resend email
- Payments
- Stripe
- Hosting
- One machine we own
Want the layer, not the app?
The repair data is available through an API, with a free tier for hobbyists and paid tiers for volume. If you are building something that needs real labor times, start there.