2. Build
Host and deploy your product
Put your product on a reliable host with your own domain, automatic deploys, HTTPS and backups, without overpaying.
| Stage | 2. Build |
|---|---|
| Time needed | 1-3 days |
| Typical cost | $0-50 per month |
| Difficulty | Medium |
| Done when | Product live on your own domain over HTTPS, Every merge to main deploys automatically, Database backed up and a restore tested |
How to host and deploy your product
Why this step matters
Your product only exists for customers when it is live on a stable address. Good hosting is mostly invisible: pages load quickly, deploys happen safely, data is backed up and you hear about problems before users do. Bad hosting shows up as outages during your launch, lost data and surprise bills. For an early-stage team the aim is a setup that one person can understand and fix in an evening.
Think about hosting as a set of separate decisions: where the domain is registered, where DNS is managed, where the front end and the backend run, where the database lives and where files are stored. Keeping a short written note of each choice, with the account owner and login method, saves hours when something breaks or a new team member joins.
How to do it
- Register your domain properly. Buy it through a reputable registrar in an account owned by the company, with
two-factor login and auto-renew switched on. Use a shared admin email rather than a founder's personal inbox.
- Pick the right kind of host. The main options are static and front-end hosting platforms (ideal for marketing
sites and front-end apps), managed application platforms (you push code, they run it), serverless functions, managed databases and backend-as-a-service platforms, and virtual servers you manage yourself. Most MVPs fit well on a managed platform plus a managed database. A virtual server is cheaper at scale but makes you responsible for updates, security and uptime.
- Connect deploys to your repository. Set up continuous deployment so that merging to the main branch builds,
tests and deploys automatically. Most platforms do this out of the box. Add preview deployments for each pull request if your host offers them.
- Create a staging environment. Keep a separate copy with its own database for testing changes. Never test
destructive migrations on production data.
- Handle secrets and configuration. Put API keys, database passwords and tokens in the platform's environment
variable settings. Rotate any key that has ever been committed or pasted into a chat.
- Turn on HTTPS and a CDN. Most hosts issue certificates automatically. A content delivery network in front of
your site speeds up static files and absorbs simple attacks; many offer a free tier.
- Back up and test a restore. Enable automatic database backups and actually restore one into staging. A backup
you have never restored is a hope, not a backup.
- Add monitoring. Set up an uptime check on your main page and an error-tracking tool in your app so crashes reach
you by email or chat. Check that alerts arrive by breaking something on staging.
What it costs and how long it takes
Many managed platforms have free tiers that cover a prototype and early users; expect roughly $0-50 a month for a small product, plus about $10-20 a year for a common domain. Costs climb with traffic, database size, bandwidth and background jobs, so read each platform's usage pricing and set billing alerts. The initial setup takes one to three days for someone who has done it before.
Free credits, perks and services that help
The large cloud providers and several hosting platforms offer startup credits that can cover a year or more of early hosting. See cloud credits and hosting and domains for current programs and providers, and developer tools perks for monitoring and CI discounts. Credits expire, often after one or two years, so design your setup so that it stays affordable when they run out. More offers sit in the perks directory.
Common mistakes
- Over-engineering. Container orchestration and multi-region setups are rarely needed before product-market fit.
- Credit lock-in. Building around one provider's credits can leave you with an expensive bill when they end.
- No staging. Testing on production is how launch-day outages happen.
- Lost domain. A domain registered by a former freelancer or co-founder can take months to recover.
- Silent failures. Without monitoring you learn about downtime from angry users.
- Region and data rules. If you serve EU or UK users, check where personal data is stored and processed.
Go deeper
Find deployment and DevOps-focused AI agents, Agent Skills and MCP servers for hosting platforms on VibeCodes.
Programs and services for this step
Do
- Start on a managed platform with a free or low tier
- Keep staging and production separate
- Store secrets in the host's environment settings, never in code
Avoid
- Do not run your own servers until you have a reason
- Do not skip a backup restore test
- Do not register your domain in a personal account you might lose
Host and deploy your product: frequently asked questions
How much does it cost to host and deploy your product?
Expect $0-50 per month. Free credits and perks from the programs below can cover much of it in the first year.
How long does it take?
Plan for 1-3 days. Difficulty: medium.
What does this step get you?
It mainly gets you product, save money.
How do I know it is done?
Product live on your own domain over HTTPS, Every merge to main deploys automatically, Database backed up and a restore tested, Uptime monitoring and error alerts switched on.
Which programs and services help with it?
startups.ws lists 35 programs, 0 accelerators and 7 founder services for this step, each with who qualifies and how to apply.
Other steps in 2. Build
The full path →Choose your AI coding stack Easy
Pick the AI coding tools, language and framework your team will build with, so you ship fast without boxing yourself in.
Build your MVP Medium
Build the smallest version of your product that solves one real problem, and get it into users' hands within weeks.
Set up analytics Easy
Track the few numbers that show whether people find, use and come back to your product, while respecting their privacy.