Free tools Windows power users keep installed
One-click scans. No signup required.
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
You cannot install the hosted Bolt.new service itself on a VPS. Bolt.new is a browser-based StackBlitz product powered by WebContainers; its official repository describes a service that runs without local setup. The self-hostable project people usually mean is bolt.diy, an open-source sibling maintained by StackBlitz Labs. You can run bolt.diy on your own Linux VPS with Node.js and pnpm, or with Docker Compose. The practical setup is to keep the AI workspace bound to localhost and reach it through an SSH tunnel or a properly authenticated reverse proxy. This guide uses the bolt.diy repository and commands, then explains how generated projects, databases, API keys and production deployment remain separate concerns.
Can I install Bolt.new on a VPS?
Not the hosted Bolt.new service. Bolt.new is presented by its official repository as an AI-powered web-development agent that lets you prompt, run, edit and deploy full-stack applications in a browser, with no local setup. Its WebContainers architecture is not documented as a VPS installer.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
As an Amazon Associate I earn from qualifying purchases.
For a self-hosted workspace, use the open-source bolt.diy repository. bolt.diy lets you select an LLM provider for each prompt and run the workspace on infrastructure you control. Treat the names as different products: commands in this article install bolt.diy, not the hosted Bolt.new service.
There are three separate things you might be trying to host:
Popular on Amazon
- The builder: bolt.diy itself, which provides the AI coding interface.
- The generated application: code exported from the builder and deployed as its own service.
- Supporting services: a database, object storage, authentication system and secrets used by that application.
Installing the builder does not automatically move a hosted database, copy production secrets or publish a generated application.
What VPS resources and software does bolt.diy need?
Use a Linux VPS with sufficient disk, memory and CPU for your prompts, builds and any containers started by generated projects. A 2026 third-party walkthrough uses 100 GB of storage, 16 GB of RAM and four CPU cores as a planning baseline. Those figures are not an official StackBlitz Labs sizing guarantee; the current bolt.diy README does not promise a minimum production configuration.
| Requirement | Planning value | Qualification |
|---|---|---|
| Storage | 100 GB | Example from a third-party 2026 VPS walkthrough; increase it for Docker images, build artifacts and generated projects. |
| Memory | 16 GB RAM | Example baseline, not a vendor SLA. Large builds and local models can require more. |
| CPU | 4 cores | Example baseline for a usable workspace; concurrency and compilation workload change the requirement. |
| Node.js | 22.12.0 or newer | Required by the bolt.diy README checked in 2026. |
| pnpm | 9.15.9 or newer | Required by the bolt.diy README checked in 2026. |
| Operating system | Linux VPS | The repository does not state a single distribution as a production requirement; use a supported 64-bit Linux image and keep it patched. |
Install Git, Node.js and pnpm before cloning. Verify the versions from the same shell that will run the service:
git --version
node --version
pnpm --versionIf Node.js reports a version below 22.12.0 or pnpm below 9.15.9, upgrade before running the install. A process manager or terminal multiplexer is useful for a non-Docker development process; screen is one simple option, but it does not provide authentication, TLS or automatic recovery.
How do I prepare and secure the VPS?
Create a non-root administrator account, apply operating-system updates and allow only the network ports you actually need. Keep SSH restricted to your administration network where possible, and use key-based authentication rather than a password.
- Update the operating system. Use your distribution’s normal update mechanism and reboot if a kernel update requires it.
- Install prerequisites. Add Git, Node.js 22.12.0 or newer and pnpm 9.15.9 or newer. Distribution packages may lag behind the required versions, so verify the output rather than trusting the package name.
- Choose a data location. Keep the repository and any Docker volumes on a disk with enough free space for dependencies, image layers, logs and generated projects.
- Set a firewall policy. Permit SSH and only the web ports used by an authenticated reverse proxy. Do not open the development server’s internal port to the internet.
- Plan backups. Back up source repositories, configuration and provider settings separately from any database used by a generated application.
The safest first deployment leaves bolt.diy listening on localhost. That means an internet scan cannot directly reach the AI agent, even if the VPS has a public address.
How do I clone and run bolt.diy directly with Node.js?
The direct route is the shortest installation and is convenient for evaluation or a single administrator. It runs the repository’s development server rather than a hardened, independently managed production service.
Also popular on Amazon
- Clone the self-hostable repository and enter it:
git clone https://github.com/stackblitz-labs/bolt.diy.git
cd bolt.diy- Install the exact dependency set resolved by the repository:
pnpm install- Start the development server:
pnpm run devThe README exposes the default development URL at http://localhost:5173. On the VPS, “localhost” means the VPS itself, not your laptop. Leave this terminal attached while you work, or run it inside a controlled screen session. A terminal multiplexer keeps the process alive after an SSH disconnect, but it is not a substitute for a service manager, health checks or log rotation.
When updating an existing checkout, inspect the repository’s current scripts and lockfile before changing commands. Run git pull, review any migration notes, then repeat pnpm install. Avoid deleting the lockfile to force an install; that can produce a different dependency graph from the one maintained by the project.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11How do I open the private workspace from my computer?
Use SSH local port forwarding while the development server remains bound to the VPS loopback interface:
ssh -L 5173:localhost:5173 user@your-vpsKeep that SSH session open, then visit http://localhost:5173 in your local browser. The browser connects to your computer’s port 5173, and SSH carries the traffic to port 5173 on the VPS. If your local port is already occupied, select another local port, for example:
ssh -L 8517:localhost:5173 user@your-vpsThen open http://localhost:8517. This arrangement avoids publishing the AI agent on 0.0.0.0. Publicly exposing an unauthenticated agent can disclose API keys, prompts, generated source and other sensitive data. If several people need access, place the service behind a reverse proxy that provides TLS, identity-aware authentication, rate limiting and a firewall policy. Do not treat a reverse proxy’s HTTPS certificate alone as user authentication.
How do I configure OpenAI, Anthropic, Gemini or a local model?
In the bolt.diy interface, open Settings → Providers, choose a provider and enter its key or endpoint. Provider billing, quotas, model names and regional availability remain controlled by that provider; self-hosting the interface does not make inference free.
Recommended Free Tools
The repository also documents environment variables that can be placed in .env.local, including:
Also popular on Amazon
ANTHROPIC_API_KEYOPENAI_API_KEYGEMINI_API_KEYOLLAMA_BASE_URLLMSTUDIO_BASE_URL
Copy the example file when using the container workflow:
cp .env.example .env.localProtect .env.local with restrictive file permissions and keep it out of Git. A local endpoint such as Ollama or LM Studio still needs to be reachable from the process or container running bolt.diy. If the model server runs on another machine, bind it to a private network or VPN rather than exposing its API to the public internet.
How do I run bolt.diy with Docker Compose?
Docker provides repeatable dependency isolation and makes it easier to rebuild the workspace, at the cost of another layer to monitor. The official README lists separate development and production profiles.
Development profile
- From the repository root, create the local environment file:
cp .env.example .env.local- Start the development profile:
docker compose --profile development upUse the logs to confirm that the application started and note the port reported by the checked-out version. Keep the compose project on a private network and expose only a deliberately configured proxy.
Production build and profile
- Build the production image using the script listed by the current README:
pnpm run dockerbuild:prod- Start the production profile:
docker compose --profile production upCommands can change between revisions. Some older walkthroughs show npm run dockerbuild instead; use the scripts present in the version you cloned, and inspect package.json if a command is unknown. Do not combine a compose file from one revision with scripts from another without checking compatibility.
Should I use the direct Node route or Docker?
Both routes run the same self-hostable project, but they suit different operational needs.
| Decision point | Node and pnpm | Docker Compose |
|---|---|---|
| Setup speed | Fewest moving parts: install Node and pnpm, then run the scripts. | Requires Docker and Compose in addition to the repository. |
| Isolation | Dependencies share the VPS host’s userland. | Application dependencies and runtime are packaged in containers. |
| Repeatable rebuilds | Depends on the checkout, lockfile and host environment. | Image builds and compose files provide a more reproducible deployment unit. |
| Background operation | Needs a process manager or a supervised terminal session. | Compose can restart containers, but you still need log, disk and health monitoring. |
| Upgrades | Pull the repository and reinstall according to its lockfile. | Pull, rebuild the image and recreate the profile; persistent volumes must be handled deliberately. |
| Operational complexity | Lower for one user and short-lived development. | Higher initially, often preferable when several services or environments must match. |
Choose direct Node execution when you need a quick private workspace and understand that the development server is not a complete production platform. Choose Docker when repeatable builds, isolation and a clear separation between application and host are more important than the smallest setup.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsAlso popular on Amazon
How do I expose a production-style deployment safely?
Do not make the development server a public, unauthenticated website. A safer architecture is:
- Run bolt.diy on an internal address or Docker network.
- Terminate HTTPS at a reverse proxy with a certificate for your domain.
- Require an identity layer before forwarding requests to the workspace.
- Restrict inbound traffic with a firewall and, where practical, an allowlist or VPN.
- Store provider keys as protected secrets, not in a public repository or client-side configuration.
- Monitor CPU, memory, disk, container health and failed authentication attempts.
AI prompts can contain source code, credentials pasted by mistake or personal data. Apply the same access controls you would use for an internal development system. If your goal is only to publish an application generated by Bolt, expose the application—not the builder—and keep the builder private.
Can I run Bolt.new locally instead of on a VPS?
You can run bolt.diy on a local Linux, macOS or Windows environment that satisfies its Node.js and pnpm requirements, but that is still bolt.diy rather than the hosted Bolt.new service. A local installation is useful when one person needs the workspace and model endpoints are reachable from that machine.
A VPS is preferable when the workspace must remain available while your computer is offline, when several administrators need controlled access, or when the model endpoint and build tools are already on a server network. A local installation avoids VPS administration but leaves uptime, backups and network reachability to your own machine.
What happens to projects, databases and secrets after generation?
Export the generated source to a Git repository or another controlled system, then deploy that application independently. The builder’s workspace and the deployed application are different lifecycles.
- Source code: export or synchronize it to Git and review dependencies before deployment.
- Database: provision a database you control, apply the application’s schema and migrate data separately. A database previously hosted for a builder project is not automatically included in the source export.
- Secrets: recreate API keys, database credentials, OAuth values and signing secrets in the deployment platform’s secret store. Never commit them to the generated repository.
- Domains and HTTPS: point DNS to the application server and issue a certificate through your reverse proxy or deployment platform.
- Build and runtime: use the application’s own package scripts, Dockerfile or Compose file; do not assume the builder’s development process is its production server.
A common production path is Git-based deployment to a Docker or Compose host, with DNS and automatic Let’s Encrypt HTTPS handled by an operations platform. The exact platform is optional; the important boundary is that application deployment, data migration and builder hosting are planned as separate tasks.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What are the most common installation failures?
pnpm install rejects the Node.js version
Check node --version. Upgrade to Node.js 22.12.0 or newer, reopen the shell so the new binary is on PATH, and run the command again. Do not bypass the requirement by forcing installation; native dependencies may compile incorrectly.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Also popular on Amazon
The browser cannot reach port 5173
Confirm that pnpm run dev is still running and that the process reports http://localhost:5173. If it is on the VPS, use the SSH forwarding command and browse to the local forwarded port. A VPS firewall rule cannot fix a tunnel pointed at the wrong remote port.
The provider returns an authentication or quota error
Recheck the key in Settings → Providers or in .env.local, then verify that the selected model is enabled for that account and region. Self-hosting does not remove provider quotas or billing limits.
Docker starts but the application exits
Read the compose logs for a missing environment variable, an unavailable image or an incompatible script. Confirm that you used the profile and build command from the same repository revision. Remove neither named volumes nor environment files until you know whether they contain data or credentials.
The VPS runs out of memory or disk
Inspect container layers, package caches, logs and generated project artifacts. Stop unused containers, rotate logs and expand storage or RAM before retrying a large build. The 100 GB, 16 GB and four-core figures are planning guidance, not a guarantee for every model or workload.
How does self-hosted bolt.diy compare with hosted Bolt.new and exported deployment?
The right choice depends on whether you value convenience, infrastructure control or ownership of the finished application.
| Option | What you operate | Model choice | Data and security responsibility | Typical reason to choose it |
|---|---|---|---|---|
| Hosted Bolt.new | No VPS installation; the service is browser-hosted. | Defined by the hosted product’s available integrations. | Shared between you and the service operator under its terms. | Fastest start with no server maintenance. |
| Self-hosted bolt.diy | Linux host, dependencies or containers, updates, backups and access controls. | You select configured cloud or local endpoints. | You control the VPS, keys, network and workspace data. | Provider flexibility, private networking or internal development. |
| Exported application | The application’s runtime, database, domains, monitoring and deployment pipeline. | Determined by the application’s code and services. | You own migration, secrets, user data and production security. | Publishing a finished product without exposing the AI builder. |
For most VPS administrators, the sensible sequence is to keep bolt.diy private, use it to generate or edit code, export that code to version control, and then deploy the application through a separate production workflow.
Frequently Asked Questions
Does bolt.diy include an LLM or API credits?
No. The workspace connects to a provider or a local model endpoint that you configure. API charges, rate limits and model access are determined by that provider, while local inference uses the CPU, memory and storage of the machine running the model.
Can multiple developers share one self-hosted workspace?
Only after you add an access-control design around it. The basic development server is not, by itself, a multi-tenant identity system, so use separate accounts or an authenticated proxy and establish rules for shared projects, logs and provider keys.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →How should I update bolt.diy without losing configuration?
Keep .env.local, Docker volumes and exported source outside the disposable checkout, then pull the new revision and follow its current README scripts. Test the upgrade privately before switching a reverse proxy or shared DNS name to the new process.
Can a generated project keep using the builder’s database in production?
Only if that database is explicitly reachable, supported and migrated under your control. Plan a database export, schema migration, credential rotation and backup policy instead of assuming that exporting source code also transfers hosted data.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
