Nice Technologies — Fleet Platform
In developmentFounder & engineer · 2026 – present
- Tenant isolation lives in the database, not the app. Every table is
guarded by PostgreSQL row-level security, and an unset tenant context fails closed —
so a forgotten
WHEREclause can't leak one operator's riders to another. - The scheduling rules come from how the work actually happens. School bell and release times anchor the run; a drop-off can never be ordered before its own pickup; morning and afternoon legs stay independent, so skipping one never cascades into the other.
- Access control built for a regulated customer. TOTP multi-factor with recovery codes, invitation and password-reset flows, driver name masking, and a support-access tier that staff can only enter with the customer's approval.
- Four surfaces, one language. Next.js control portal, a Node API, and Expo driver and parent apps — all TypeScript, with self-hosted MapLibre and Protomaps tiles rather than a per-request mapping bill.