How livemy.app built its infrastructure layer with VMmanager

livemy.app is a UK-based technology startup operating from London. It is a new hosting platform designed for the emerging generation of “vibe coders.”

The company is a young startup that was launched less than a year ago. livemy.app allows users to deploy applications without dealing with traditional infrastructure complexity. A user can upload a ZIP archive or provide a Git repository link, while the platform handles code validation, infrastructure provisioning, application deployment, networking, and access configuration.

The service is aimed both at non-technical creators who build applications with AI assistants and at professional developers who want to deploy prototypes and production applications quickly.

livemy.app currently has a compact team of six people. The team combines product development, backend engineering, infrastructure management, DevOps, platform operations, and customer support.

Because the team is small, automation is essential. Routine infrastructure operations must be handled by software, allowing employees to focus on product development, platform reliability, customer experience, and business growth.

As livemy.app is a new startup, there was no large legacy infrastructure that had to be migrated. The platform was designed from the beginning around a bare-metal architecture, with VMmanager serving as the central virtualization management layer.

During the initial prototype stage, the main challenge was to connect the application deployment workflow with physical infrastructure. The livemy.app team needed a reliable way to create, configure, monitor, and remove virtual machines without developing an entire virtualization management platform internally.

The current infrastructure consists of eight physical servers managed through VMmanager. KVM is used as the virtualization technology, providing strong workload isolation and predictable allocation of CPU, RAM, storage, and network resources.

The livemy.app team built a custom control plane and integrated it with VMmanager.
The control plane manages the complete application deployment lifecycle:

The platform also uses NestJS for the backend and control plane, Prisma and MySQL for persistent state, Redis queues for asynchronous tasks, Gitea for internal source-code storage, ClamAV for security scanning, Docker for application packaging, and HAProxy for incoming traffic routing.

VMmanager is not exposed directly to livemy.app customers. Instead, it operates as the infrastructure layer behind the platform’s custom user experience.

The primary task was to create a scalable infrastructure foundation for a new type of hosting platform.

livemy.app customers should not have to understand servers, SSH, operating systems, firewall rules, or container orchestration. From the customer’s perspective, application deployment should be reduced to uploading the code and receiving a working URL.

Behind this simple workflow, however, the platform must securely provision isolated computing resources, allocate network resources, track infrastructure status, recover from failures, and remove resources when they are no longer required.

Developing all virtualization management functions internally would have significantly increased development time and operational risk. It would also have required the livemy.app team to maintain its own provisioning, node management, networking, resource allocation, and virtual machine lifecycle systems.

Public cloud platforms were also less suitable for the project’s long-term model because livemy.app wanted to operate its own bare-metal infrastructure, maintain control over resource allocation, and avoid building the business entirely on top of third-party public cloud pricing.

Why VMmanager was selected:

VMmanager provided a centralized platform for managing KVM virtualization across multiple physical servers. It enabled the team to focus on the livemy.app product and its deployment automation instead of developing a virtualization control layer from scratch.

API integration capabilities, centralized management of physical nodes and virtual machines, and support for infrastructure scaling.

The availability of direct technical assistance from the ISPsystem team.

The implementation of VMmanager took approximately two months. In parallel, the livemy.app team developed a custom integration between VMmanager and the platform’s control plane.

The integration required more than simply installing the platform. VMmanager had to become part of an asynchronous provisioning workflow in which several operations take place simultaneously: source-code validation, malware scanning, virtual machine preparation, network configuration, Docker image creation, and application startup.

The implementation was supported by the ISPsystem team throughout the process. The team assisted livemy.app with complex configuration tasks and helped resolve infrastructure-specific issues in the early stages of deployment.

This cooperation helped livemy.app move from an early-stage architecture to a production-ready virtualization environment and reduce the risks associated with launching a new infrastructure platform.

VMmanager is used as the central virtualization management platform for the livemy.app infrastructure.

The client’s engineering and infrastructure teams use it to manage eight physical servers, create and remove KVM virtual machines, control virtual machine resources, monitor infrastructure status, and support the automated deployment lifecycle.

Approximately 200 virtual machines have already been created within the infrastructure, even though the platform has been operating for less than a year.

The hot-pool model significantly reduces the delay perceived by the customer and supports the main livemy.app promise: infrastructure should feel instant, even when the underlying deployment process involves multiple security and orchestration stages.

The main results achieved with VMmanager include:

Centralized management of eight bare-metal servers.

Approximately 200 virtual machines created during the startup’s first year.

Automated KVM virtual machine provisioning through the livemy.app control plane.

Faster customer deployment through a pool of pre-provisioned virtual machines.

Reduced need for manual infrastructure operations.

A scalable foundation that can grow by adding new physical servers.

Greater focus on product development instead of maintaining a custom virtualization platform.

As livemy.app grows, the team expects to expand the number of physical servers, virtual machines, and deployed customer applications. VMmanager will remain the core infrastructure management layer supporting this growth.