PostlyoPostlyo

Running a blog properly means a CMS, an SEO plugin, an analytics script, a paywall tool and hosting. Five accounts, five bills, five places to break, before a word is written. Postlyo put those in one multi-tenant system. The engineering question was never features, it was isolation: one endpoint missing a tenant filter shows one customer another customer's unpublished drafts, and you find out from the customer. So tenancy is enforced at the data layer rather than trusted to each query. What did not get built was a page builder, because every publishing product drifts toward one and it eats the roadmap permanently.

Each tenant gets its own domain, its own certificate and its own billing, which sounds like three features and is really one problem: everything has to be provisioned without a human, because the alternative is me doing setup by hand for every signup.