SaaS Platforms Live
LogiFlow
Multi-tenant logistics SaaS platform with inventory, warehousing, production, distribution, billing, and platform admin modules.
- Category
- SaaS Platforms
- Status
- Live
- Core stack
- Django · Django REST Framework · Next.js · TypeScript · PostgreSQL

“Multi-tenant SaaS · Stripe, M-Pesa & crypto billing”
01 — Overview
LogiFlow is a production-grade multi-tenant logistics SaaS platform built to serve companies of varying scales. Each tenant gets isolated data, custom branding, and role-based access for their teams.
The backend is built with Django REST Framework and the frontend with Next.js and TypeScript, using a services + hooks state management pattern without Redux or Zustand.
02 — What it does
- 01Multi-tenant architecture with full data isolation per company
- 02Inventory management with stock tracking, reorder points, and transaction history
- 03Warehousing module with stock transfers and approval workflows
- 04Production module with orders, steps, and materials tracking
- 05Distribution module with real-time route tracking via Leaflet.js and geocoding
- 06Billing system with automated trial expiration and recurring billing via Celery
- 07Platform Admin module for managing tenants, subscriptions, and system health
- 08Prometheus and Grafana monitoring stack
03 — Architecture
A Next.js client talks to a Django REST API that isolates every tenant’s data, with Celery handling billing in the background and Prometheus watching it all.
Hover or tap a component to see what it does and what it talks to.
- Client
- Service
- Data
- External
- Ops
04 — Engineering challenges
- 01Designing a clean multi-tenant architecture that scales without data leakage between tenants
- 02Implementing a centralized auth guard architecture using layout.tsx to avoid repetition across pages
- 03Fixing a critical auth bug where verifyAuth() hardcoded all role fields to false on token refresh
- 04Replacing mock SVG maps with real Leaflet.js maps using dynamic imports to avoid SSR issues
- 05Handling HTTP 204 empty responses that caused JSON parse errors in the API layer
- 06Building automated billing workflows with Celery including trial expiration and payment reminders
- 07Integrating Stripe, M-Pesa, and NOWPayments crypto into a unified billing experience
05 — Stack
- Django
- Django REST Framework
- Next.js
- TypeScript
- PostgreSQL
- Redis
- Celery
- Docker
- Stripe
- M-Pesa
- NOWPayments
- Leaflet.js
- Prometheus
- Grafana
Next project
FlixVideo