ForgeVPSFind your way around
Learn what ForgeVPS does, what each tab is for, and how the different parts of your workspace fit together.
On this page
What can I do with ForgeVPS?
ForgeVPS gives your Linux server a browser interface. You can run commands, edit project files, start applications, connect domains, and work with PostgreSQL databases without switching between separate tools for every task.
Your code and applications live on your machine. ForgeVPS is the place you use to work with them. For example, you can edit a website in Files, run its setup commands in Terminal, keep it running through Servers, and give it an address in Domains.
A machine and a server are different things here
A machine is the VPS you connect to ForgeVPS. It supplies the CPU, memory, disk, and operating system. A server in the Servers tab is an application running on that machine, such as your website, API, or development preview.
One machine can run several application servers and databases. They share the machine’s resources. When this documentation says “select your machine,” it means the VPS; when it says “open your server,” it means the application entry in Servers.
Start by checking your machine
- Open ForgeVPS and look at the machine name in the navigation. This is the machine whose files, terminals, and applications you are viewing.
- In hosted ForgeVPS, use the machine selector to switch between connected machines. In self-hosted, you work in the panel’s local workspace.
- Open Dashboard to see the machine’s connection details and resource usage. If setup is incomplete, follow the setup controls before continuing.
The tabs below all belong to the selected machine. Switching to another machine changes the files, servers, and databases you are looking at.
What each tab is for
- Dashboard — check the machine’s connection, memory, disk, CPU load, and setup status. Start here if something feels slow or unavailable.
- Terminal — type commands on the machine. Use it to install a project’s dependencies, run scripts, or work with a command-line coding agent.
- Files — browse folders, edit code, search your project, and review Git changes.
- Servers — start and manage applications. Choose a development preview, a production app, or a GitHub deployment where available.
- Domains — connect a web address to an application and set up HTTPS.
- Databases — create and browse PostgreSQL databases, edit tables, run SQL, import from Supabase, and manage backups.
On smaller screens, navigation may show icons instead of full labels. On desktop, hovering an icon shows its name. The underlying workspace is the same.
Try a complete workflow
- Open Files and find the folder containing your project. Read its README to see how the project is started.
- Open Terminal, change to that folder, and run the project’s required setup commands.
- Go to Servers → Add server. Choose Development server, select the same folder, and enter its development command.
- Open the server’s details and check Logs. Once it responds, use its displayed address to view the application.
- Return to Files, make a small change, and save it. If the project supports live reloading, the development preview should update. Otherwise follow its rebuild/restart instructions.
For a live application, register it as a Production server and add a domain when it is ready. Development and production describe how you intend to use the app, not which package manager it uses.