Multi-tenant Sales Platform
A scalable sales-management backend serving multiple clients from one deployment on AWS.
- Problem
- A growing sales operation needed one system to serve many clients without their data ever crossing streams.
- Solution
- A FastAPI + PostgreSQL backend with tenant isolation, clean migrations and managed AWS infrastructure.
- Impact
- Supported multiple tenants on shared infrastructure with safe, reproducible schema migrations.
Stack
- Python
- FastAPI
- PostgreSQL
- SQLAlchemy
- Alembic
- AWS
Context
A sales operation was scaling to serve multiple clients and needed a single backend that kept each tenant’s data strictly isolated while sharing infrastructure cost.
Architecture
A FastAPI service backed by PostgreSQL, with SQLAlchemy models and Alembic migrations for safe, reproducible schema evolution. Infrastructure runs on AWS — EC2 for compute, RDS for the database and Lambda for event-driven jobs.
Details
- Tenant isolation enforced at the data layer so no request can leak across clients.
- Alembic migrations make schema changes reviewable and reversible.
- Managed AWS services keep the operational surface small for a lean team.
What I’d do next
Introduce per-tenant usage metrics and autoscaling policies so cost tracks real demand.