How Seedly deploys - what you get, how Sprout walks you through it, where it runs, and what you need.
Loading the guide...
Did this answer your question?
Help us make the guides more useful.
2 helpful · 0 not helpful
How Seedly deploys - what you get, how Sprout walks you through it, where it runs, and what you need.
Loading the guide...
Help us make the guides more useful.
2 helpful · 0 not helpful
This is the plain-English overview of how you get from buying Seedly to a live CRM running on infrastructure you control. It is not an exhaustive runbook; the full step-by-step lives in the setup guide that ships inside the product.
The moment you purchase, you receive two things by email:
From there, the path is: download the source, run the guided setup, and deploy. Most people who are comfortable following technical instructions get to a working deployment in an afternoon.
You do not have to wire this together from memory. There are two supported paths, and you can mix them:
Either way, the included documentation covers each account you create and each value you need to set.
Seedly is a modern web app: a frontend deployed on Vercel and a backend running on Convex.
This is the honest version of "self-hosted": you own and control the source and your data, and you choose where it is deployed. The default path leans on Convex Cloud so you are not running database servers by hand.
A realistic checklist before you start:
npx pnpm, which needs Node to work. If node --version returns "command not found," install it from nodejs.org (LTS is fine) before you unzip the download. Skipping this is the most common reason the very first setup command fails.For most agencies, hosting runs somewhere between $25 and $200 a month depending on how hard you push it. A small operation often starts on free tiers. The usage-based services you connect (email, texting, AI) are billed by their providers at their own rates, and you can rebill that usage to your clients at your own markup.
Plan for a couple of hours the first time, mostly spent creating accounts and pasting in credentials. The setup itself is guided; the time goes into the one-time configuration tasks (connecting providers, verifying your sending domain) that you do once and never touch again.
You buy once, you own the code, and you decide when to update. Nothing changes on your build unless you pull it in.