We build the blogging layer your product was missing
BlogForge is a multi-tenant blogging platform. One installation serves every brand, product or client you run: each gets its own domain, its own branding and theme, its own admins and its own readers, while you keep a single codebase to maintain.
What we actually build
Not a page builder, and not a headless CMS you still have to assemble yourself. A complete publishing product that plugs into the site you already have.
Multi-tenant from the first line of code
Every tenant is resolved from its own domain, with its own content, admins, branding and analytics. Adding a tenant is a record, not a deployment.
A publishing workflow editors can run alone
Drafts, scheduling, categories, tags, series, authors, comment moderation and SEO fields all live in an admin panel built for editors, so nobody needs a developer to publish.
Integration that respects your stack
A signed JSON API, direct login links from your main site and tenant-safe sessions make the blog behave like part of your product instead of a bolted-on subdomain.
How a blog goes live
Three steps between an empty tenant and a fully branded blog serving readers on your own domain.
Provision the tenant
Create the application, point its domain or subdomain at the platform and pick a theme. Its API credentials are generated along with it.
Publish the content
Write in the admin panel or push posts through the signed API. Content is translatable, schedulable, and old URLs keep working through slug history.
Serve it as your own
Readers land on your domain, your branding and your theme. Views, likes, comments and logins are tracked and forwarded to your own analytics account.
What we hold ourselves to
Four decisions that are already in the code, not on a roadmap.
Secure by default, not by configuration
Signed API requests, CSRF protection, optional two-factor authentication on both admin panels and single-use SSO tokens ship enabled, so there is no insecure mode to accidentally stay in.
Multilingual and RTL as a baseline
Content and interface are translatable field by field, and right-to-left layouts are part of the design rather than a patch applied afterwards.
One tenant can never see another
Tenant resolution happens in middleware before a single query is written, so isolation never depends on a developer remembering to filter.
Your content, your templates, no lock-in
Themes are plain Blade files you can upload and replace at any time, and everything readers see is reachable through the same API that writes it.
Want to see it on your own domain?
Tell us what you are building and we will walk you through the parts that matter to you.