# Frequently Asked Questions > Common questions about Seedly Sites - the license, building and migrating client sites, hosting, client access, and billing. ## General ### What is Seedly Sites? A self-hosted 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](/docs). ### How is this different from Webflow, Duda, or Wix Studio? Those are hosted platforms you rent, priced per site, per month. Seedly Sites is a platform you own: one $999 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. ### What does the license allow? 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. ### Do I need to be a developer? 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](/docs/getting-started). ### Is there AI in the product? 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. --- ## Building Sites ### Is the builder drag-and-drop? Yes - real drag-and-drop over a Section, Row, Column hierarchy with 40 element and block types, native style fields, and per-breakpoint layout control. See [Builder basics](/docs/help/builder-basics). ### Can I reuse sections I have already built? Yes. Save any section to your saved-blocks library and drop it into other pages or sites, alongside the 16 built-in section presets. See [Presets & saved blocks](/docs/help/presets-saved-blocks). ### Can it migrate an existing site? Yes. The migration pipeline crawls the source site and reproduces it closely in the builder - typically around 91 percent content parity, measured by 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. ### What does migration NOT bring over? 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](/docs/help/port-a-site). ### Is there a form builder? 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 automatic UTM capture into the embed). See [Forms](/docs/help/forms). --- ## Hosting & Domains ### Where are the client sites hosted? Each client site publishes as static files to its own Cloudflare Pages project on the client's custom domain. See [Architecture](/docs/architecture). ### Is hosting free? 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) plus R2 media storage. The point is that costs are flat - they do not grow per site. ### Are the sites fast? 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. ### When do changes go live? 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 and operator-controlled. See [Preview vs Publish vs Deploy](/docs/help/preview-publish). --- ## Clients ### Can my clients edit their own sites? 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](/docs/help/client-guide). ### What can I restrict? WordPress-style roles (Administrator, Editor, Author, Contributor, Subscriber) plus a per-tenant role override and a separate deploy permission. See [Users & roles](/docs/help/users-roles). ### Is it white-label? 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. --- ## Billing ### Can I bill clients through the platform? 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](/docs/help/billing). ### What happens when a client stops paying? 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. ### Whose Stripe account is it? Yours. Your instance carries your own Stripe keys, and client payments go straight to your account. There is no revenue share. --- ## Getting Started ### How long does setup take? About 15 to 30 minutes to a working local sandbox, then a couple of hours, spread over sittings, for the live setup on Railway and Cloudflare. See [Getting Started](/docs/getting-started). ### What accounts do I need? Railway, Cloudflare, and GitHub (a private repository). The local sandbox needs none. ### What if I get stuck? Run the built-in doctor (`npx pnpm run setup:check`), check [Troubleshooting](/docs/help/troubleshooting), or ask in the Seedly community group on Facebook. ### Can I see it before buying? Yes - [try the live demo](/demo). The [purchase page](/purchase) lists exactly what is included. --- Source: https://seedlysites.com/docs/faq