How Seedly Sites hosts client sites - static hosting on Cloudflare Pages, one project per client, custom domains, and what it actually costs to run.
Loading the guide...
Help us make the guides more useful.
0 helpful · 0 not helpful
Seedly Sites separates the platform you run from the sites your clients' visitors see. The CMS and builder live on your server; every client site deploys as pure static files to its own Cloudflare Pages project. This page covers the hosting model, domains, and the honest economics.
| Piece | Where it runs | Who sees it |
|---|---|---|
| CMS + portal + builder | Your Railway instance | You and your clients (logged in) |
| Client sites | Cloudflare Pages, one project per client | The public |
| Media (images, video) | Cloudflare R2 storage | The public, via each site |
One project per client. When you create a site in the portal, the platform provisions a dedicated Cloudflare Pages project for it automatically. Deploys, domains, and traffic are isolated per client - one site's deploy can never affect another's.
Static output. A deploy builds the site's published content into plain HTML and CSS with no runtime framework. There is no origin server to slow down, crash, or patch; the CDN serves finished pages from locations near the visitor.
That architecture is the performance story: static pages on a global CDN are fast by default, which is exactly what Core Web Vitals reward. See the hosting overview for the marketing-level summary.
Every site gets a <project>.pages.dev address from its Cloudflare Pages project. Its behavior depends on whether the site has launched:
Use the preview address for internal review and client sign-off before go-live.
www.clientbusiness.com works from any DNS provider. A bare domain such as clientbusiness.com needs Cloudflare to run its DNS first: move its nameservers to Cloudflare, then add the custom domain/admin: open Tenants, open the site, and fill in Custom domain in the right-hand sidebar. Saving it also attaches the domain to the site's Pages projectFrom this deploy on, the site's canonical URLs, sitemap, and structured data all use the custom domain, and the preview address redirects to it.
If the client is migrating from an existing site, set up 301 redirects for any URLs that changed as part of the migration. Redirects are managed per site in the portal and ship with every deploy.
Being straight about this, because "free hosting" claims usually hide something:
| Cost | What it covers | Scale behavior |
|---|---|---|
| Railway (CMS) | The platform: CMS, portal, builder, database | Shared across ALL client sites; grows with usage, not site count |
| Cloudflare R2 | Media storage + delivery | Usage-based; typically small |
| Cloudflare Pages | Serving every client site | Free static hosting tier |
| SendGrid | Password resets, client intake links, and job-failure emails | A paid plan once the trial ends; grows with email volume, not site count |
| Anthropic API | AI site generation, client intake analysis, port revision, and visual QA | Pay per use; costs nothing while no AI job is running |
Connected review widgets, if you use them, are the one cost that grows with each connected listing.
So: serving a client site costs you nothing per site, but running the platform is not zero-cost - the CMS host, media storage, and email are real (modest) monthly costs you pay once for the whole fleet, and AI generation is billed by use. There are no per-site platform fees and no per-seat fees; adding your 30th client site costs the same as adding your 3rd.