In production
Multi-tenant content platform
A content operations platform running multiple client accounts from a single codebase.
Each account has its own isolated brand rules, channel setup and content history, enforced by the system rather than by whoever is writing that day. Weekly content calendars are planned per account, content is generated against the plan, and approved output is passed to an automated publishing pipeline. Batch runs execute server-side and survive a closed browser. A human approval step sits between generation and publishing - the system handles assembly, a person decides what ships.
Six client configurations. Adding a new one is a form, not a code change.
Built with
- Node.js
- n8n
- multi-tenant architecture
- server-side job execution
- self-hosted