If you squint, a minisite looks a lot like a landing page. It has a URL, some content, and a clear call to action. So why did we bother building MiniSite Host instead of recommending “just use another landing page builder”?

Because most teams don’t struggle to design pretty pages. They struggle to ship lots of small, time‑sensitive sites without adding DevOps overhead.

The problem with traditional landing page stacks

When we talked to agencies and enablement teams, the same patterns kept coming up:

• “We have a big marketing site, but every new partner launch needs its own URL.”
• “Engineering is busy. Spinning up a new repo + CI + DNS entry for a short‑lived page feels ridiculous.”
• “We want to give non‑developers more control without giving them the keys to production.”

Traditional landing page tools are great at visual editing, but they struggle with:

• File‑based workflows – uploading a zip from your design system or static export.
• Dozens or hundreds of microsites – all with their own slugs, redirects, and access rules.
• Edge‑native hosting – getting traffic close to users without learning a new infra stack.

That’s the gap MiniSite Host was built to cover.

Minisites as a first‑class primitive

At MiniSite Host, a “minisite” is just a folder in Cloudflare R2 with a bit of metadata in D1. That makes some powerful things very simple:

• Each minisite lives at its own slug: yourbrand.minisite.host/campaign-name.
• A single Cloudflare Worker handles routing, SSL, and edge caching for every minisite.
• You can archive, clone, or roll back a minisite without touching DNS or Terraform.

Instead of fighting a monolithic marketing site, teams get a sandbox built for small, focused web experiences: launch hubs, demo portals, partner pages, onboarding kits, and more.

Who MiniSite Host is for

We designed MiniSite Host for teams who:

• Ship new campaigns or partner launches weekly.
• Need self‑serve uploads for non‑developers but still care about governance.
• Want Cloudflare‑grade performance without managing Cloudflare directly.

If that sounds like you, MiniSite Host probably fits your stack. You bring a zip file or static export; we handle the boring parts: storage, routing, SSL, and quotas.

What’s next

Over time, we’re layering in the kinds of controls you’d expect from a full platform—teams, roles, quotas, and eventually SSO and impersonation—without making the core idea heavier.

Simple mental model: you upload a minisite, we make sure the world can see it safely and quickly.

If you’d like to see how this feels in practice, start from the dashboard and ship a throwaway minisite in a few minutes. The best way to understand MiniSite Host is to publish something small today and iterate from there.