MVP Standard Stack — Opinionated 4-Week Architecture

The MVP Standard Stack is di-factory's reference blueprint for delivering a first monetizable version of a digital product in a fixed 4-week sprint. It rejects the industry-default 'build me something' MVP that ships a prototype and dies the day the founder tries to charge for it. Instead it delivers a production-hardened Django application — data models, API contracts, auth, admin, deployment, and observability — ready to accept its first paying customer on day 29.

The stack is opinionated on purpose. Django 5 + PostgreSQL + Django REST Framework + Bootstrap 5 is the constant across every engagement, because opinionation is what buys the 4-week timeline. What changes by client is the cloud path: the four tabs below show the same application deployed against Open Source, AWS, GCP, and Azure — so corporate innovation teams, VC-backed founders, and PyME operators all see a runway they can defend to their CFO, CIO, or board.

Seven layers wrap the app — Presentation, API & Contracts, Application Framework, Database, Storage & Media, Runtime & Deploy, and Observability. Each layer is scoped to what a first-production version needs (auth, migrations, admin, health checks, error reporting) and explicitly excludes what it doesn't (multi-region replication, complex CDN edge logic, ML pipelines). That's what makes the 4-week sprint honest — clients get the architecture that ships, not the one that impresses on a whiteboard.

Below the diagram, three use cases show the standard stack in production shape for the archetypes we sell to hardest in Mexico: a real-estate marketplace, a healthcare access platform, and a fintech onboarding and KYC flow. The stack is the same. The domain model changes. The delivery timeline does not.