Choose your infrastructure
Provider neutrality is a design direction: your host choice should not be dictated by a proprietary hosting integration. Actual compatibility still depends on provider policy, hardware and qualification.
Why Svavyom
Why build your personal cloud with Svavyom?
Explore Svavyom’s design choices, infrastructure ownership and the responsibilities of running your own dedicated server.
Principles
Own the infrastructure. Skip the guesswork.
Three design choices shape everything else.
Understand the tradeoffs
Owning the infrastructure gives you control, but also leaves you responsible for access, updates, recovery, networking and backups. A management interface cannot remove those responsibilities.
Build on familiar layers
KVM, QEMU and libvirt separate kernel virtualization, the VM process and its management interface. Svavyom builds on these rather than inventing a new hypervisor.
Responsibility
What stays yours, and what Svavyom aims to help with
Svavyom is not yet a substitute for an operational virtualization platform. Evaluate currently available tools against your immediate needs.
Always yours
- Access, updates and security patching
- Recovery, rescue consoles and reinstall paths
- Public addressing, firewalls and routing
- Off-server backups and tested restores
Where Svavyom aims to help
- A single web console for machines (Preview)
- Typed, restricted host operations
- Familiar, inspectable virtualization layers
- Plain-language guides, available today
Get started
Get the code. Get the next steps.
Download and share the source any time. Add your email and we will send the repository link and next steps, then occasional updates as the project moves.
Prefer to look first? Open the repository