Common questions about Seedly Sites - the license, building and migrating client sites, hosting, client access, and billing.
Loading the guide...
Did this answer your question?
Help us make the guides more useful.
0 helpful · 0 not helpful
Common questions about Seedly Sites - the license, building and migrating client sites, hosting, client access, and billing.
Loading the guide...
Help us make the guides more useful.
0 helpful · 0 not helpful
Use the handbook and release notes included with your download for version-specific instructions.
All Seedly Sites docsLearn the foundationsA website builder and multi-tenant CMS for agencies. You buy the source code once, run it on infrastructure you control, and build, host, and manage unlimited client sites from one login. See the Product Overview.
Those are hosted platforms you rent, priced per site, per month. Seedly Sites is a platform you own: one $1,199 license, unlimited client sites, your infrastructure, your data, and static published output that stays portable. The trade is that you operate it yourself - setup is guided and takes a couple of hours.
You own and can modify your copy of the code, run it for your agency, and bring unlimited clients onto your instance. Building and selling add-on modules is allowed and encouraged. You may not resell or redistribute the core platform code itself, original or modified. One license covers one agency: if another agency wants to use the platform to build and host sites for its own clients, it needs its own license. Your own clients logging in to edit their sites is normal and fine. The full terms ship in your download as LICENSE.md.
No. Setup is a guided copy-paste walkthrough led by Pixl, the setup companion, and day-to-day use is a visual builder and a normal CMS. See Getting Started.
Yes, two ways: generate a starting draft site from a client's brand inputs, and AI assistance inside the building flow. Generated pages are always drafts for you to review and finish in the builder - nothing publishes itself.
Yes - real drag-and-drop over a Section, Row, Column hierarchy with 50 element and block types, native style fields, and per-breakpoint layout control. See Builder basics.
Yes. Save any section to your saved-blocks library and drop it into other pages of the same site, alongside the 21 built-in section presets. See Presets & saved blocks.
Yes. The migration pipeline crawls the source site and reproduces it closely in the builder, scores its content parity with a deterministic gate, and lands the result as drafts on a review board. You finish the remaining details in the builder before anything ships. It is honest to call this "closely, then finish in the builder," not pixel-perfect.
Forms and custom plugin code do not survive a migration - you re-add forms as an embed from your CRM or form provider. External backlinks are preserved only through the 301 redirects you set up for changed URLs. See Port a site.
Yes. Alongside porting, you can generate a fresh site from a client's brand inputs: you invite the client and they fill out a guided intake questionnaire themselves (or you complete it with them). You can also clone a live site as a near-exact copy. All three land as drafts you review before anything goes live. See Generate a site and Clone a site.
No. Every site built through the client intake is structurally varied per client - layout, color rhythm, spacing, imagery, and photography - within brand-safe bounds, and each build is checked against your prior builds so a near-identical one is re-rolled into a distinct variant. See Never the same site twice.
Yes. Seven template packs ship inside the download (cedar, fresh, grit, surge, swift, vista, and warm), and you can add packs of your own. The platform also works without them: port, generate, and clone all work on day one.
Generated copy is written in the client's own voice from their intake inputs, and honesty gates flag any statistic, rating, or superlative the client did not actually supply, such as "17 years in business" or "5-star rated", listing each against its page on your review board so you fix it before you publish. Generic AI phrasing is flagged for review. See Copy in the client's voice.
Not a native one. Sites embed forms from your CRM or form provider (an HTML embed block renders them, with a built-in thank-you page, and an optional setting that passes the visitor's campaign to the form embeds you list). See Forms.
Yes, optionally. A Reviews element set to Connected pulls a location's reviews from Google, Facebook, Yelp, and about a hundred other platforms and keeps them current, with no redeploy after the page is deployed once. It runs on a paid third-party account you open and fund yourself, and every connected listing is billed again every 30 days for as long as it stays connected. Typing reviews in by hand with the Manual mode is free. See Auto-Updating Review Widgets.
Each client site publishes as static files to its own Cloudflare Pages project on the client's custom domain. See Architecture.
The static hosting itself rides Cloudflare Pages' free tier, but running the platform is not zero-cost: you pay for the app host and database (Railway), R2 media storage, email sending (SendGrid, paid after its trial), and Anthropic API usage for the AI features. None of that is a per-site fee. Connected review widgets are optional and are the exception: each connected listing is billed every 30 days through your own provider account (see Auto-Updating Review Widgets).
The architecture is built for it: published pages are prebuilt static files served from Cloudflare's edge with no runtime framework. Actual scores are measured per site, as always.
On your next deploy of that site. Publishing content updates the CMS; the live static site changes only when you press Deploy. Deploys are always manual: you, or a client whose login has Can deploy this site switched on presses Deploy. See Preview vs Publish vs Deploy.
Yes. Invite a client as a user on their tenant; they log in through a branded screen and edit only their own site in the visual builder. Their changes go live on your next deploy. Hand them the Client guide.
WordPress-style roles (Administrator, Editor, Author, Contributor, Subscriber) plus a per-tenant role override and a separate per-site deploy permission. The deploy permission starts on when you create a login, so switch it off for anyone who should not publish to the live site. See Users & roles.
The parts clients see are: a branded login screen, no powered-by badge on their published site, and their own domain. The admin dashboard interface itself keeps its standard look, and email sending identity is configured per instance, not per client.
Yes. Native Stripe billing per tenant: the client subscribes through a Stripe-hosted checkout, manages their card and invoices in a Stripe customer portal, and you watch every tenant's billing state on an operator dashboard. See Billing.
You choose the enforcement, per instance and per tenant: do nothing, freeze editing while the site stays up, or suspend the site. New subscribers mid-payment-setup are never treated as delinquent.
Yours. Your instance carries your own Stripe keys, and client payments go straight to your account. There is no revenue share.
About 15 to 30 minutes to a working local sandbox, then a few hours of hands-on work for the live setup on Railway and Cloudflare, spread across a day or two, plus waiting on signups, DNS, and email-domain verification. See Getting Started.
Railway (the app and its database), Cloudflare (Pages hosting and R2 media storage), and GitHub (a private repository). The go-live check also requires a SendGrid account, so password resets and client emails can send, and an Anthropic API key, which the AI generate and port features run on. You will want a domain registrar for each site you launch. Stripe is only needed if you bill clients through the platform, and Zembra only if you use the optional connected review widgets. The local sandbox needs none of these.
Run the built-in doctor (npx pnpm run setup:check), check Troubleshooting, or ask in the Seedly community group on Facebook.
Yes - try the live demo. The purchase page lists exactly what is included.