Proxmox Infrastructure
A virtualization platform supporting Linux servers, production applications, networking, and private services.
- Category
- Virtualization platform
- Status
- Private system
- Core stack
- Proxmox · Virtualization · Linux · Networking · SSH
Overview
Most of what runs behind Linear Web Solutions lives on a self-managed Proxmox VE platform. Applications, AI services, and private tools each get their own virtual machine or Linux container, with their own deploy credentials and process supervision.
The result is a small private cloud: workloads are isolated from one another and deployed from Git with scripted checks.
- 01Applications and services isolated in their own VMs and Linux containers
- 02Key-based SSH access and a dedicated deploy key per repository
- 03Process supervision with PM2 and systemd
- 04Git-based deploys that fail fast and finish with health checks
Objective
Host production applications and private services on owned infrastructure, with clear isolation between workloads and repeatable deployments.
Technical approach
- A.
One workload, one guest
Each application or service runs in its own VM or LXC container, which keeps dependencies, credentials, and failures contained.
- B.
Key-based access
Access is over SSH with keys, and each repository has its own deploy key rather than a shared credential.
- C.
Supervised processes
Node.js applications and background workers run under PM2 or systemd, so they restart on failure and return after reboots.
- D.
Verified deploys
Deploy scripts stop on the first error and finish with health checks against the running service.
Architecture
Access
- Key-based SSH
- Per-repository deploy keys
Workloads
- Production web applications
- Background workers
- AI services
Guests
- Virtual machines (KVM)
- Linux containers (LXC)
Host
- Proxmox VE
- Linux
Conceptual view. Hostnames, addresses, and topology details are intentionally omitted.
Technologies
- Proxmox
- Virtualization
- Linux
- Networking
- SSH
- Bash
Visuals
Private infrastructure. Console screenshots are not published.
The artwork above is an illustration of the system, not an interface capture.
Challenges & solutions
Challenge 01
Keeping a growing number of services maintainable.
Solution
Every guest follows the same conventions: a fixed application directory, its own deploy key, a process manager, and a documented deploy routine that ends in a health check.