If you plan to use Netlify, you need to understand more about the platform, and the type of software it’s designed to host. Netlify can’t host your database, or a traditional backend.
What is Netlify?: Netlify’s own description of their purpose and features.
Intro to Composable Architecture: this is a big topic, but it’s worth exploring, as it helps you understand what Netlify can and can’t support, and how to build for deployment to Netlify.
When you first deploy a project with Netlify, it autogenerates a URL for the project. This is a placeholder, and usually something meaningless. If you want users to access the project through your own domain, you need to buy a domain and point it to your Netlify site. The simplest way to do this is to purchase the domain from Netlify.
For users participating in the June 2025 hackathon on the Pro tier:
After you connect your Netlify account to Bolt, and deploy your project to Netlify, it shows a Set up domain button in the chat.
Click Set up domain. Bolt starts the setup process.
Choose whether to purchase a new domain, or connect a domain you already own:
Buying a new domain: this takes you through the process of buying a new domain with Ionos (Ionos will be your domain registrar), configures it with Netlify DNS, and connects it to your Netlify project.
Configuring an existing domain: if your domain is registered with a supported provider, this process changes the DNS settings of the domain to use Netlify’s DNS and connects it to your project.
After completing your setup, allow some time for changes to take effect. Once the domain is set up, the Bolt chat will tell you that your project is deployed to your domain the next time you deploy.
You don’t have to understand deployment and hosting to start building with Bolt, but once you get to the point of deploying your application, it helps to have some knowledge of the concepts and terminology.
If you’re completely new to deploying and hosting websites and web apps, here’s a brief introduction to key concepts. Note that this description is a simplified version of a complex topic. It assumes you’re building a fairly standard site.
When you build a website or application, you need a way to get it to users. For any website or web app, this means hosting the site on a server. The interaction with the site goes like this:
A user goes to your website in their browser.
The browser asks the server for the site.
The server sends the website pages to the browser.
The browser displays the site.
Depending on how complicated your site is, there may be multiple messages between the browser and server as the user interacts with the site.
CI/CD: continuous integration and continuous delivery. This is a devops practice, involving automating the processes to building, testing, and deploying code. GitLab provides a good introductory guide: CI/CD explained.
Deployment: the process of getting your code onto your server.
Devops: development operations.
the integration and automation of the software development and information technology operations (from Wikipedia)
Hosting: storing your project on a server and making it available to users.
Interaction: anything the user does. This includes entering a URL to go to a site, as well as things like clicking buttons or submitting forms.
Request: the browser sends a message to the server.
Response: the server replies to the browser.
Web apps: interactive software applications that run in a browser. For example, Bolt itself is a web app.
Assistant
Responses are generated using AI and may contain mistakes.