Companies with drivers and field staff juggle dispatch lists, phone calls and paper delivery notes. When a customer disputes a delivery, the proof is a crumpled signature sheet — if it can be found at all. The client wanted a product they could sell to many such companies: each customer fully separated from the others, documents that stand up legally, billing built in, and German-language marketing and legal pages. And it had to run on standard shared hosting rather than an expensive cloud setup.
Logistics & field operations · Case study
FlowSNX: a multi-tenant operations platform for dispatch and field work
A multi-tenant SaaS that runs dispatching, route execution, customer tracking and legally durable documents with signatures — built to run reliably on ordinary shared hosting.
- Client
- A logistics & field operations company in Germany
- Industry
- Logistics & field operations
- Year
- 2026
- Duration
- Since June 2026
- Location
- Germany
We built FlowSNX as a PHP 8.2 and MySQL platform with a strict security envelope around every request. • Dispatch and route execution, with live status for the office and tracking for the end customer. • A PDF pipeline for operational documents with signatures, kept in a legally durable form. • Multi-tenant separation, an internal back office and Stripe billing readiness. • A GDPR deletion concept, plus German marketing and legal pages. • Quality gates: static analysis at PHPStan level 8, PHPUnit contract tests, Playwright end-to-end tests and a production monitor that checks the system every five minutes. • An automated FTPS release pipeline from GitHub Actions to production.
Results
- 189API actionsAll behind one security envelope.
- Level 8Static analysisPHPStan, checked on every change.
- Every 5 minProduction checksAn automated monitor watches the live system.
One security envelope for 189 actions
Instead of many scattered endpoints, every one of the API's 189 actions passes through the same envelope: authentication, tenant isolation, permission checks, validation and logging happen in one place, so a new action cannot forget one of them.
Built for shared hosting
The platform deliberately avoids anything that needs a dedicated server — no long-running workers that shared hosts kill, no exotic extensions. Scheduled work runs in short, restartable steps, which keeps hosting costs low for the client.
Tested before it is trusted
Static analysis at the strictest practical level, contract tests for the API and browser tests for the main flows run on every change. In production, a monitor checks the system every five minutes. Before the external beta opens, a restore drill proves that backups can actually be restored.
Where it stands
FlowSNX runs in production at flowsnx.com. The external beta opens once the restore drill and the worker-schedule checks are signed off.
Free discovery call
Have a similar problem? Let's solve it.
Tell us what you need. We'll come back within 24 hours with an approach, a timeline and a number.