Three Layers.
One Coherent System.
The hypervisor controls the metal. The multi-tenant API handles the business logic. The provider console gives you visibility. Each layer is designed to operate independently and integrate seamlessly.
Why It Works the Way It Does
Every architectural decision in SwarmEngine was made for a reason. Here's the logic behind the design.
Non-Destructive Billing Enforcement
When a tenant's payment lapses, SwarmEngine freezes new resource creation and emits a billing webhook. It never destroys live VMs. Your clients don't lose data because of a missed payment — and you don't get blamed for it.
Zero Revenue Visibility
We charge you per socket, per year. We have zero visibility into your pricing, your customers, or your billing amounts. SwarmEngine integrates with Stripe and Commerce Engine on your side — your revenue stays yours.
Resource Bucket Architecture
Traditional VPS panels sell fixed plans. SwarmEngine's Resource Bucket model lets you sell pools of compute — 100GB RAM, 40 vCPU — that tenants carve into however many VMs they need. This is how AWS, GCP, and Azure actually work. Now it's within reach without their price tag.
Hardware You Own, API You Control
SwarmEngine is a socket-based license deployed on your bare-metal infrastructure. There's no cloud dependency, no data-plane SaaS, no vendor lock-in at the compute layer. If you pull the SwarmEngine license, your VMs keep running — we just revoke the control plane.
Modular Interface Options
API-first for total control, but built for speed when you need it. Integrate our pre-built management modules directly into your existing site, or use our turn-key customer portal to launch a full hosting business that replaces legacy panels like Commerce Engine entirely.
Built on What We Run
SwarmEngine isn't a product we designed for a market. It's the infrastructure layer we needed to run SwarmRacks. We eat our own cooking — every feature shipped is a feature we depend on in production before we release it.
Where We Are. Where We're Going.
Three phases. Each one ships a complete, production-usable system — not a partial demo. Phase 1 alone is a functional cloud VPS platform.
The Core Hypervisor
The Pipe
The foundational control layer. Direct KVM management, REST API surface, and the provider admin dashboard. This is what lets you provision and manage VMs from an API call instead of a GUI.
- KVM hypervisor management layer — direct libvirt integration, no middleware
- Local-node REST API: create, start, stop, delete, snapshot VM lifecycle
- Provider Admin Console — node health, resource usage, IP pool status
- IPAM: automated IPv4/IPv6 allocation, release, and audit trails
The Multi-Tenant API
The Merchant
This is where SwarmEngine becomes a cloud business platform. Tenant isolation, Resource Bucket logic, billing enforcement, and webhook-driven integrations that connect to your payment stack.
- Tenant isolation layer — scoped API keys, resource namespaces, permission boundaries
- Resource Bucket tracking: sold allocation vs. physical node capacity, real-time headroom
- Heartbeat licensing system — socket-based with tamper-detection and remote kill switch
- Webhook system: 402 billing events, provisioning events, and Stripe / Commerce Engine integration
The Mini-AWS Suite
The Cloud
Advanced cloud primitives that turn SwarmEngine from a VPS provisioning engine into a full cloud platform. VPCs, object storage, and auto-scaling — all behind your API.
- Software-Defined Networking (VPCs, private subnets, security groups, routing tables)
- S3-compatible object storage hooks — integrate existing Ceph or MinIO clusters
- Auto-scaling triggers based on real-time CPU/RAM load averages per resource bucket
- Multi-region node federation — single API surface across geographically distributed clusters