A multi-tenant creator publishing and automation platform. Every creator gets their own subdomain, their own buffer page, their own link tree, their own publish queue and their own webhook callbacks. Schedule a post once and a worker pushes it to Instagram, fires a signed callback to whatever system needs to know it shipped and logs the entire trip through a persistent event bus. No SaaS sitting in the middle, no rate-limited shared inbox, no third-party CDN watching every asset go by.
Modern publishing stacks all share the same shape. A shared inbox you rent. A queue you do not control. Analytics that disappear if you stop paying. A CDN that hands your asset URLs to every third party in the chain. The creator is always the product, never the customer.
Publishing Automation flips that arrangement. Each creator runs on their own subdomain, their own buffer page, their own job queue, their own callback URL and their own event log. The publishing engine is shared infrastructure. Everything visible to the audience and everything tied to the creator's identity belongs to the creator. The platform is plumbing the creator can route through, not a landlord standing between them and their audience.
A Node and Express backend with a React 18 admin SPA, served behind Nginx with regex-matched subdomain routing. Better-sqlite3 holds the multi-tenant data model. An in-process worker polls a job queue every ten seconds and pushes scheduled posts to the Meta Graph API. Every meaningful action lands on an event bus with a 30-day persistent store. The whole platform installs from one repo and runs under one Node process.
Every creator gets a Profile tab, a Links tab and a live preview pane that updates as they type. Display name, tagline, avatar, background, favicon, OG image. Link order, link image, link style preset, accent color. The preview reflects every change in real time and the page goes live the moment they save.
No theme marketplace, no upsell tier, no platform-branded footer. The page is the creator's surface end to end and it lives on the creator's subdomain from the moment they pick it.
The admin SPA is the cockpit for the entire platform. Creators, social accounts, the post-job queue, the event stream, the media library, API keys, page style, link presets, lifecycle policy, the CDN, webhook history and database migrations all live behind one login. Built for the operator who runs the platform, not for the audience who consumes it.
A small, sharp toolkit. Nothing depends on a vendor's roadmap or a SaaS subscription. Multi-tenant from day one, single-process by design, and cheap to run no matter how many creators land on it.
Every creator owns their subdomain, their page, their queue, their callback URL and their event log. Every operator owns the infrastructure underneath. Publishing Automation is not a destination the audience visits and it is not a brand competing for the creator's logo. It is the publishing engine that runs quietly behind whichever surface the creator wants the world to see.