Backend Engineering

FiberVue Multi-Tenant Supply-Chain SaaS Backend — A Developer's Deep Dive

Multi-tenant SaaS backend for the fiber and textile supply chain, with billing and traceable orders.

2026-09-121 min read

Multi-tenant SaaS backend for the fiber and textile supply chain.

The problem

Supply-chain partners needed tenant-isolated accounts, metered billing, and orders that could be traced end-to-end — without every customer needing a separate deployment.

The approach

Designed a multi-tenant Laravel 10 API covering tenant onboarding, Stripe-based subscription billing, QR-code-traceable orders, and Firebase Cloud Messaging push notifications, all on one shared, tenant-isolated backend.

The outcome

Complete API layer: tenant onboarding, Stripe billing, traceable orders with QR codes, push notifications.

Stack

Laravel 10, Stripe, Firebase Cloud Messaging

Live architecture demo

See it move, not just read about it.

Re-using the original animation from the linked project — same diagrams and trace you see on the case-study page.

Supply-Chain Traceability Flow

STEP 1/6
REST API V1 • Laravel Sanctum
tenant request arrives at /api/v1/orders; Sanctum validates token abilities & workspace scope • ~12 ms
Stripe Gateway • Plan Validation
organization subscription active; quota checks permit tiered composition upload • cached
SimpleSoftwareIO • Intervention Image
high-error-correction (Level H) PNG rendered with unique hash for downstream batch verification • ~35 ms
MySQL Ledger • Audit Trail
order committed with fiber certificates, tier records, & sub-supplier mapping; audit log sealed
Laravel Queue • Redis Dispatch
ProcessDownstreamAlert job pushed to Redis; non-blocking API response sent • ~4 ms
Firebase Cloud Messaging • Kreait SDK
push notification broadcasts to manufacturer & auditor devices: "Certificate Verified" • sub-second

← All posts