Software you run a business on deserves an honest answer to one question: what happens after it ships? Our support keeps the platform fast, secure, and dependable — with a scope that's written down, not implied. Here is exactly what's included, what isn't, and how the two work together.
The left column is the ongoing care that keeps your platform healthy. The right column isn't a catch — it's the work that belongs in its own dedicated engagement, so it gets the attention and pricing it deserves.
Ongoing care to keep the platform running the way it does today — and better over time.
New work that changes or extends the platform. Not off-limits — just handled as a scoped Custom Development engagement.
No ticket maze, no runaround. A direct line, a real look at the problem, and honest communication about where things stand — because the person who built the platform is the person maintaining it.
Reach out the way that suits you — a message, an email, a call. Tell us what happened, on which app, and roughly when. If it's captured, a screenshot or the trip in question helps us move faster.
Anything that loses a job, loses money, blocks dispatch, or crashes the app is treated as urgent and looked at first. Everyday tweaks and smaller fixes are batched so releases stay stable and low-risk.
The platform's black-box audit trail helps us reproduce and pinpoint the cause, not just the symptom. We fix it, verify it against real behavior, and roll it out — with a change you can actually see.
Frequent, unscheduled changes are how stable software gets destabilized. So we hold a simple, honest line: fix what's breaking the business immediately, and batch the rest into planned releases that are checked before they reach your fleet.
Good support isn't only what happens after a report — it's what the software does to make problems findable in the first place. This platform was built with maintenance in mind.
This isn't code that's only seen a test bench. It runs in daily production for a real transportation company — through rush hours, dead zones, and the edge cases only live dispatch surfaces. The bugs found in real operations are the ones already fixed.
Every meaningful event is recorded to a durable audit log with one-tap restore. When something goes wrong, we don't guess — we replay exactly what happened, find the true cause, and recover the data instead of debating it.
Error boundaries and live logging run inside both apps, and the serverless backend surfaces issues instead of hiding them. Problems show up in the light — which means they get diagnosed and fixed faster, not left to fester.
Disk-first queues and a socket watchdog mean jobs and completions survive dead zones and sync on reconnect — fewer emergencies to support.
Config-gated behavior lets many fixes ship as flags — turned on or rolled back instantly, without waiting on an app-store build.
Deny-by-default security rules, a custom dispatcher claim, and phone + PIN + Face ID / Touch ID auth keep the surface small and defensible.
We don't publish response-time promises or uptime percentages we can't stand behind. What we commit to is real: business-critical issues handled with urgency, everything else moved deliberately, and an honest answer about where anything stands. If a request is custom work, we'll tell you — and quote it up front, not after.
Your fleet runs on it every day — support should be just as steady. Let's walk through what's covered, what your operation needs, and how the custom work fits in.