# Hosting and CI Building Solutions

DatoCMS doesn't host your frontend. You deploy it wherever you like, and we make sure your editors can make changes and publish content with minimal friction.

Once you connect a build trigger, editors can kick off a new build of the website from inside DatoCMS and see whether it went through or failed, right from within the project.

## Pick your setup

-   [Netlify](https://www.datocms.com/docs/hosting-and-deployment/netlify.md)
-   [Vercel](https://www.datocms.com/docs/hosting-and-deployment/vercel.md)
    
-   [GitLab CI](https://www.datocms.com/docs/hosting-and-deployment/gitlab.md)
-   [Custom webhook](https://www.datocms.com/docs/hosting-and-deployment/custom-webhook.md): for everything else. If your CI can receive a POST request and call us back with the result, it works without issues.
    

## Do you need one?

If your site is static, yes. Every content change needs a rebuild to show up, and a build trigger is how your editors can push new content live without you having to redeploy the website every time.

If you're server-rendering, or using the [Real-time Updates API](https://www.datocms.com/docs/real-time-updates-api.md) to push changes to the page, you can skip this. A build trigger is still handy if you're using [DatoCMS Site Search](https://www.datocms.com/docs/site-search.md), since it notifies us to re-crawl your site after a deploy.

## Related content in "Hosting & Deployment"

- [Hosting and CI Building Solutions](https://www.datocms.com/docs/hosting-and-deployment.md)
- [Netlify](https://www.datocms.com/docs/hosting-and-deployment/netlify.md)
- [Vercel](https://www.datocms.com/docs/hosting-and-deployment/vercel.md)
- [GitLab CI](https://www.datocms.com/docs/hosting-and-deployment/gitlab.md)
- [Custom webhook](https://www.datocms.com/docs/hosting-and-deployment/custom-webhook.md)