Zulfanoon: one Django codebase running 11 live websites

The problem

A single idea kept failing: building one hit product at a time means every new site starts from zero — new login system, new database, new deployment. The owner wanted a portfolio of small tools that share one audience: a calculator on one subdomain referred users to a PDF converter, which referred them to the AI tool directory. Repeating login and infrastructure for each would make the tenth site as slow to ship as the first.

The build

A Django monorepo became the foundation. One Django project hosts a central API; each product is a Django app served on its own subdomain. The architecture decisions were written down as documented ADRs so the system scales with clear rules:

• Schema-per-site Postgres: every subdomain gets its own PostgreSQL schema; users, auth, subscriptions and analytics live in a shared public schema.
• JWT cookie auth across subdomains: login once on the main site and stay logged in on calc.zulfanoon.com, tools.zulfanoon.com and the rest.
• Docker per site: each subdomain runs as its own container, so one site can be redeployed without touching the others.
• Server-rendered HTML + Tailwind: SEO was a first-class requirement, so pages ship as HTML instead of JavaScript-only apps.
• Cloudflare in front: CDN, DNS and SSL handled at the edge for all subdomains at once.
• Shared services: analytics tracking, an ad-slot system and SEO config management are features the central API gives every site.

Early milestones came from a written roadmap with success metrics: the first subdomain (finance calculators) shipped in weeks 5–12, including 12 finance calculators covering Zakat, EMI, gold, USD/PKR rates and prize bonds — each with SEO meta and schema markup.

The results

• 11 websites live today — a main hub plus calculators, PDF & image tools, developer tools, an AI directory with 490+ listings, prompts, a CV builder with 12 designs and PDF export, QR tools, media downloader and background remover.
• One shared backend: single login across every subdomain — users move from tool to tool without re-registering.
• Zero-friction scaling: adding a new site is an app in the monorepo, not a new project; CI/CD and Docker make the deploy repeatable.
• SEO-first output: every page ships server-rendered HTML with meta and schema, designed so the ecosystem ranks together.

The same monorepo pattern is how Duramo Lab and the AI platforms were launched — each is a subdomain-style product on a shared, proven backend rather than a fresh gamble.

Why the "ecosystem" matters to clients

An ERP with multiple warehouses, a media house with multiple products, or a SaaS provider with multiple tools face the same architecture question: one system or many? Zulfanoon answers it — a single codebase, isolated data, shared login, one deploy pipeline. If you run several properties, this keeps maintenance and licensing costs linear instead of multiplying per site.