How Seedly Sites is put together - a multi-tenant CMS and builder on your app host, publishing static client sites to Cloudflare Pages.
Loading the guide...
Help us make the guides more useful.
0 helpful · 0 not helpful
Seedly Sites splits cleanly into two halves: the platform you and your clients log into, and the static sites your clients' visitors see. Understanding the split explains why published sites are fast, cheap to host, and safe to edit.
The CMS and the visual builder run as an application on your app host (Railway is the supported setup), backed by a Postgres database.
This half is the only part with a server and a database. It is where you and your clients sign in, and it also runs the platform's scheduled jobs (publishing posts you scheduled, the automatic backup, and routine clean-up sweeps). npx pnpm run setup:scheduler switches off GitHub's duplicate copies.
When you press Deploy, the platform renders the tenant's published content into plain static files - HTML and CSS with no runtime framework - and pushes them to that client's own Cloudflare Pages project, created automatically when the site is created. Each deploy also regenerates the site's sitemap, robots rules, and redirects.
A healthy-looking dashboard is not the same thing as an update being complete. Your cms service runs its database migrations each time it starts, before the server boots, so if a migration fails the new version never starts and your previous version usually keeps serving. Judge an update by the cms deploy's status and log, not by the site being up.
There is a deep health check for exactly this: it reports whether the running code and the database agree, so you can confirm an update rather than infer it from a green deploy. Use it after any update that lists migrations. See Updating.
Each tenant serves on its own custom domain, connected in Cloudflare. The platform's preview URLs are kept out of search engines so only the client's real domain ranks. See Hosting & domains for the setup walkthrough.
Everything is on infrastructure you control: content and settings in your Postgres database, media in your R2 bucket, published files in your Cloudflare account, and the publish pipeline in your private GitHub repository. Backups and exports are built in - see Backups & disaster recovery.