Virtual Machines on Your Own Servers
Virtual machines on your own servers: shared, dedicated or custom sizes, Linux distribution and custom images, SSH keys, user data and a metadata service, volumes, snapshots and scheduled backups, private networks, cloud firewalls, reserved IPs and IPv6, billed per hour a machine runs, to the second.
Core Offerings & Service Capabilities
Comprehensive capabilities designed to deliver immediate visibility, security, and operational efficiency for Virtual Machines.
Machines Sized the Way You Need
Pick a size from the catalog or set your own vCPUs, memory and disk, on servers you already own.
- Shared vCPU sizes for everyday workloads
- Dedicated vCPU sizes, general purpose, CPU optimized or memory optimized, pinned to their own CPUs
- Custom sizes, resized later; disks grow and never shrink
Images, Access and First Boot
Start from a verified Linux distribution or your own image, and log in the way you prefer.
- Ubuntu, Debian, Rocky Linux, AlmaLinux and Fedora, on x86-64 and Arm64, or your own image imported from a URL
- SSH keys, or a generated root password shown once and never stored
- User data run at first boot and a metadata service each machine reads about itself
Storage, Snapshots and Backups
Add volumes, take snapshots and schedule backups into backup storage you own.
- Volumes formatted and ready to mount, attached while the machine runs and grown online
- Live snapshots of a machine or a volume, kept until you delete them
- Backups every 4, 6 or 12 hours, daily or weekly; restore in place or create a new machine from one
Networking and Security
Private networks, firewalls and public addresses managed with the rest of your cloud.
- Private networks and private hostnames through Virtual Private Cloud
- Cloud firewalls with inbound and outbound rules by address, machine, tag or network
- Reserved IPs assigned to a machine and moved between your servers, and IPv6
Operational Architecture & Control Plane Guarantees
Rigorous data sovereignty, least-privilege security boundaries, and high availability metrics engineered for Virtual Machines.
Deployment Model
Virtual machines on your own Linux servers with hardware virtualization, enrolled as hypervisor hosts through Fleet Manager.
Data Plane Isolation
Machines, disks and traffic stay on your servers; snapshots and backups go to backup storage you own.
Latency Profile
Hardware-virtualized machines with dedicated vCPU sizes pinned to their own CPUs; capacity reserved per machine.
Compliance & SLA
Every action and change recorded in the audit trail; alerts and incidents when a machine fails or a server goes offline.
Scope & Platform Capabilities
Linux virtual machines on your own servers: shared, dedicated or custom sizes, distribution and custom images, volumes, snapshots and backups, private networks, firewalls, reserved IPs and IPv6.
- Virtual machines on your own Linux servers, enrolled as hypervisor hosts through Fleet Manager, on x86-64 or Arm64
- Shared vCPU sizes, dedicated vCPU sizes (general purpose, CPU optimized, memory optimized) pinned to CPUs no other dedicated machine uses, or custom vCPUs, memory and disk
- Each machine placed on the least loaded server of the zone with room for it, or on the server you pick; capacity reserved per machine, with no overcommit unless you allow it
- Ubuntu, Debian, Rocky Linux, AlmaLinux and Fedora images verified by checksum, or your own image imported from a URL in a common disk image format
- SSH keys, or a generated root password shown once and never stored; user data scripts run at first boot; a metadata service each machine can read about itself
- Power on, shut down, power off, reboot, power cycle, resize, rebuild, rename and password reset, each recorded as an action with its history; power actions on every machine with a tag
- Create up to ten machines in one request, and tag machines, volumes and snapshots
- Volumes formatted and ready to mount, attached and detached while the machine runs, and grown online
- Snapshots of a machine or volume, live while it runs, and scheduled backups every 4, 6 or 12 hours, daily or weekly into your own backup storage; restore in place or create a machine or volume from them
- Private networks through Virtual Private Cloud, cloud firewalls with inbound and outbound rules by address, machine, tag or network, reserved IPs that move between your servers, and IPv6
- CPU, memory, disk and network metrics per machine and the machine's boot console output
- Quotas per organization, alerts and incidents when a machine fails or a server goes offline, setup checks, and every change in the audit trail
Implementation & Infrastructure-as-Code
Provision, configure, and automate Virtual Machines using the Syntoric CLI, the REST API and JSON specifications.
# Reboot a machine
curl -X POST "https://api.syntoric.com/v1/compute/machines/$MACHINE/actions" \
-H "Authorization: Bearer $TOKEN" \
-H "X-Syntoric-Org-Id: $ORG" \
-d '{"type": "reboot"}'Enterprise & Technical Questions
Key questions about architecture, compliance, credential security, and deployment for Virtual Machines.
See Virtual Machines on Your Own Cloud
Book a technical walkthrough with our team to see it working against your own environment.