Can I export my Lovable or Bolt app and host it myself?
Yes, and it is wiser than putting it off. What exactly you get with an export, what is not in there, and what to watch for before you press the button.
This question usually comes up at one of two moments: you want to use your own domain name, or you start feeling uneasy about your entire business sitting on a tool's account. Both are fair reasons, and in both cases the answer is yes.
What you get
Most tools export to a GitHub repository. What is in there is real code: the screens, the logic, the configuration. That is your property and you can put it with any hosting provider that handles this kind of project. You are not locked in, and that is better news than a lot of people assume.
What is not in there
- Your database. It usually sits with a separate service and does not travel with the code; you have to take it over or export it separately.
- Your environment variables. The keys to your database, payment provider and email were in the tool and have to be set up again in the new place.
- The build steps the tool did invisibly for you. Running locally often takes a few commands that are written down nowhere.
- Everything you configured in the tool itself: domains, forms, analytics, built-in authentication.
Those four points together are why an export often ends in a repository nobody touches again. The code is there, it just does not run anywhere.
The order that does work
Export first, while everything is still running. Then get the code working locally, with your own copy of the database and your own keys, so you know for certain you have every part. Only after that put it live on your own hosting, and keep the old version up for another week. Move your domain last, not first.
An export is not a move. It is packing the boxes; the keys to the new house are a separate arrangement.
Do this immediately on export
Rotate your keys. Anything that has been in the tool and has passed through chat windows, treat as no longer secret. Creating new keys takes five minutes and is one of the few security measures you can take yourself without any knowledge.
Then check whether the export landed properly: one commit with the whole app in it means your history starts today. Not a disaster, but worth knowing, because going back to “how it was last week” is then no longer possible.
When you need help
If your app takes payments, has users or stores data that is not yours, the export is the right moment to have someone look at it. Not to rebuild everything, but to check whether the keys are in the right place and whether the database shields anything. Those two are almost always missing, and they are still missing after an export.