MAGMIFY: A MULTI-TENANT DJANGO CMS PLATFORM

Overview

Magmify is a multi-tenant CMS and commerce platform built on Django. Each tenant gets its own real PostgreSQL schema, so content and products are isolated at the database level rather than by row filtering. It exposes a headless content API for tenants who want to bring their own frontend, and ships a Django and HTMX admin.

The Problem

Building multi-tenant SaaS infrastructure is repetitive and easy to get subtly wrong, especially the isolation boundary. Magmify provides multi-tenancy, a CMS, and the beginnings of commerce as a ready platform for SaaS builders and agencies, so a new client site is a new tenant rather than a new codebase.

The Approach

The backend splits into shared apps (users, billing, tenants) and per-tenant apps (CMS, commerce, customers), with schema-based isolation via django-tenants. Auth uses JWT with two-factor, access is governed by role-based permissions, and the admin is being built in Django with HTMX and Tailwind after an earlier React single-page admin was retired in favour of a simpler, server-rendered approach.

Status

Magmify is in active development. Working today: multi-tenant schema isolation, authentication with two-factor, billing with plans and subscriptions, a CMS with pages and a library of content block types, and role-based access with a content API. Still to build: the full Django and HTMX admin, the commerce API and checkout, and payment processing.

What It Demonstrates

• Schema-per-tenant isolation on PostgreSQL as the core architectural bet.
• A clean split between shared and per-tenant apps.
• A pragmatic frontend reset: a server-rendered admin over a heavier SPA.
• Working multi-tenancy, auth, billing, and CMS, with commerce in progress.