Describe the feature you want to add
I am looking to deploy and use bolt.diy as a self-hosted, persistent server-side application rather than running it strictly as a local development server on localhost. Additionally, I want the deployment to automatically generate a secure, private URL so I can seamlessly access my workspace and AI assistant from any device (desktop, tablet, or mobile) without exposing it to the public internet.
Describe the solution you'd like:
Server-Side Execution: The ability to run the core bolt.diy engine on a remote server, VPS, or home lab setup permanently in the background.
Persistent Sessions: Projects, file trees, and chat histories should remain active and accessible regardless of which device logs in.
One-Click/Easy Remote Access: An integrated, easy-to-configure tunneling or reverse-proxy solution (like Cloudflare Tunnels, Tailscale, or Ngrok) built into the setup script or Docker configuration.
Private Authentication: A simple password or token-based authentication layer at the entry point of the private URL to ensure only the owner can access the interface.
Describe alternatives you've considered:
Local SSH Tunneling: Running ssh -L manually from external devices. It works, but it is tedious to set up on mobile devices and frequently disconnects.
Manual Reverse Proxy Setup: Manually configuring Nginx, Let's Encrypt, and firewall rules. This requires advanced networking knowledge and defeats the "DIY/Easy to use" ethos of the project.
Third-Party Web Hosting: Attempting to push the build to static hosts, which fails because bolt.diy requires server-side node processes to function properly.
Additional context:
Why this matters: bolt.diy is an incredible tool for developer productivity. Bringing server-side processing and private URL access to the project transforms it from a "local laptop tool" into a personal cloud-based development powerhouse that can be utilized on the go.
Describe the feature you want to add
I am looking to deploy and use bolt.diy as a self-hosted, persistent server-side application rather than running it strictly as a local development server on localhost. Additionally, I want the deployment to automatically generate a secure, private URL so I can seamlessly access my workspace and AI assistant from any device (desktop, tablet, or mobile) without exposing it to the public internet.
Describe the solution you'd like:
Server-Side Execution: The ability to run the core bolt.diy engine on a remote server, VPS, or home lab setup permanently in the background.
Persistent Sessions: Projects, file trees, and chat histories should remain active and accessible regardless of which device logs in.
One-Click/Easy Remote Access: An integrated, easy-to-configure tunneling or reverse-proxy solution (like Cloudflare Tunnels, Tailscale, or Ngrok) built into the setup script or Docker configuration.
Private Authentication: A simple password or token-based authentication layer at the entry point of the private URL to ensure only the owner can access the interface.
Describe alternatives you've considered:
Local SSH Tunneling: Running ssh -L manually from external devices. It works, but it is tedious to set up on mobile devices and frequently disconnects.
Manual Reverse Proxy Setup: Manually configuring Nginx, Let's Encrypt, and firewall rules. This requires advanced networking knowledge and defeats the "DIY/Easy to use" ethos of the project.
Third-Party Web Hosting: Attempting to push the build to static hosts, which fails because bolt.diy requires server-side node processes to function properly.
Additional context:
Why this matters: bolt.diy is an incredible tool for developer productivity. Bringing server-side processing and private URL access to the project transforms it from a "local laptop tool" into a personal cloud-based development powerhouse that can be utilized on the go.