Unlocking Ultra-Lightweight Container and VM Management: Why Tech Agencies are Migrating to Incus on VPS

Introduction: The Infrastructure Dilemma for Modern Tech Agencies

Tech agencies today face a relentless balancing act. On one side, clients demand rapid deployment, absolute environment isolation, and high availability. On the other side, agency finance teams demand strict cost control. Traditionally, managing multi-tenant client workloads meant choosing between two extremes: the heavy resource overhead of traditional Hypervisors like VMware or Proxmox, or the application-centric limitations of Docker when managing persistent, OS-like environments.

For years, LXD (Linux Containers) filled this gap perfectly, offering "system containers" that behave like virtual machines but run at bare-metal speeds. However, following recent corporate shifts and licensing changes surrounding LXD, the open-source community rallied behind a powerful, independent fork: Incus. Maintained under the Linux Containers project, Incus has rapidly evolved into the premier open-source solution for orchestrating both system containers and lightweight Virtual Machines (VMs). For tech agencies operating on standard Virtual Private Servers (VPS), Incus represents a paradigm shift in resource efficiency and infrastructure flexibility.

What is Incus? The True Successor to LXD

Incus is a next-generation infrastructure management tool designed to manage Linux containers and virtual machines through a clean, secure, and highly scalable REST API. It is not an entirely new technology built from scratch; rather, it is a refined refinement of LXD, stripped of canonical-specific dependencies and optimized for community-driven innovation.

Unlike Docker, which focuses on packaging single applications (microservices), Incus focuses on system containers. An Incus container runs a full Linux distribution (such as Ubuntu, Debian, or Alpine) with its own init system, networking, and storage, but shares the host kernel. This structural difference results in a massive performance advantage, allowing agencies to pack dozens of isolated client environments onto a single, affordable VPS.

Why Tech Agencies are Choosing Incus over Traditional Virtualization

When operating a digital agency, software house, or DevOps consultancy, infrastructure choices directly impact your bottom line. Here is why Incus on a VPS is superior to traditional setups:

• Ultra-Lightweight Footprint: Incus system containers share the host VPS kernel. There is zero hypervisor overhead. A container idling with a full system system init process can consume as little as 15-30MB of RAM.
• Dual-Engine Flexibility: Need to host a lightweight Node.js or PHP stack? Use an Incus system container. Need to run a specialized Windows instance or a custom Linux kernel for a legacy client enterprise app? Incus can launch a full, KVM-backed Virtual Machine using the exact same CLI commands and API.
• Multi-Tenancy and Security: Incus uses unprivileged containers by default. Root inside the container maps to a non-privileged user on the host VPS. This ensures strict isolation between different client projects sharing the same hardware.
• Extreme Cost Efficiency: Instead of provisioning five separate low-end VPS instances for five small clients—and paying for five operating system overheads—you can provision one high-performance VPS and use Incus to partition it cleanly, dramatically increasing your margins.

"By shifting our client staging environments from individual cloud instances to a centralized VPS running Incus, we reduced our monthly cloud infrastructure spend by over 60% while simultaneously increasing deployment speeds."

Architecting Incus on a VPS: Key Components

To successfully leverage Incus within a tech agency workflow, it is important to understand its underlying architecture and how it interacts with standard VPS resources:

1. Storage Pools (ZFS and Btrfs)

Incus supports advanced storage backends such as ZFS and Btrfs. When deployed on a VPS, utilizing these filesystems unlocks advanced capabilities like instantaneous container snapshots, efficient cloning (copy-on-write), and strict storage quotas per client environment. If your VPS provider only offers standard EXT4 volumes, Incus can easily manage a loop-backed storage pool without breaking a sweat.

2. Advanced Networking and OVN

Managing network traffic across multiple clients requires robust isolation. Incus provides built-in support for bridged networks, macvlan, and SR-IOV. For advanced agencies managing multi-node VPS deployments, Incus integrates natively with OVN (Open Virtual Network), allowing you to create complex software-defined networks (SDN) with private subnets, custom firewalls, and internal load balancers spanning across your infrastructure seamlessly.

3. The Powerful Incus API and CLI

Everything in Incus is API-first. This means your agency can automate the creation, destruction, and modification of client environments. Whether you want to hook up Incus to your internal CI/CD pipelines, build a custom hosting dashboard for your clients, or integrate with provisioning tools like OpenTofu or Ansible, the developer experience is seamless and production-ready.

Step-by-Step Production Use Cases for Agencies

How does this translate to everyday agency operations? Let us look at three practical scenarios where Incus outshines the competition:

1. Isolated Client Staging Environments: When developing custom web applications, you can spin up an exact replica of the client's production OS inside an Incus container in less than two seconds. Test updates, database migrations, and configurations safely without any cross-contamination.
2. Legacy Application Hosting: Many agencies inherit legacy projects requiring specific, outdated OS packages. Running these in lightweight Incus containers keeps them completely segregated from your modern stacks, preserving system security without requiring dedicated hardware.
3. Micro-SaaS Multi-Tenancy: If your agency builds and manages SaaS platforms for multiple clients, you can dedicate an Incus system container to each tenant. This gives them dedicated system resources and independent network boundaries, keeping data strictly segregated.

Migrating from LXD to Incus: What You Need to Know

If your agency is already utilizing LXD, transitioning to Incus is remarkably straightforward. The open-source community has developed an automated migration tool called lxd-to-incus. This utility safely inspects your existing LXD configuration, migrates all storage pools, networks, profiles, and running containers over to the Incus daemon with minimal to zero downtime.

Because Incus maintains backward compatibility while actively stripping out legacy bugs and licensing restrictions, making the switch now ensures your agency's internal tooling remains sustainable, open-source, and fully supported by the broader DevOps ecosystem for years to come.

Conclusion: Future-Proofing Your Agency Infrastructure

In the competitive landscape of digital agencies and tech consultancies, infrastructure agility is a core business advantage. Adopting Incus on a VPS delivers the perfect trifecta: the performance of bare metal, the flexibility of full virtualization, and the cost-efficiency of modern system containers.

By moving away from resource-heavy hypervisors and restrictive single-app container structures, your agency can deliver highly secure, fast, and scalable client solutions on highly optimized hardware budgets. It is time to elevate your DevOps strategy, regain control of your hosting margins, and embrace the power of Incus.