Our hardware,
your workload
AMD EPYC compute, all-NVMe storage with Ceph triple replication, 400Gbps internal network. Shared, private, and hybrid tiers, with bare metal and managed backups alongside.
Six ways to host with us
Virtual server, virtual data center, private cloud, bare metal, managed backups, website hosting. Same platform, different surface for the workload.
A VM on our cloud, sized to fit
Provisioned virtual machines from a few cores to dozens, with the hypervisor, network, and storage operated by us. Standard images, custom images, or a build from scratch.
Tell me moreA pool of resources, your VMs on top
Reserve CPU, RAM, and storage as a pool. Spin up VMs against it on your schedule. We hold the platform; your team operates the workloads.
Tell me moreDedicated hardware, your tenant alone
Single-tenant cloud sized to the workload. Dedicated hosts, dedicated storage, dedicated network underneath, hypervisor of your choice. Operated by our team.
Tell me morePhysical servers without the cabinet
Dedicated AMD EPYC servers in our facilities, on our network, without renting the rack. Same compute the cloud runs on, exposed directly to your workload.
Tell me moreBackup as a service, on Ceph or backuppc rsync
Scheduled snapshots and offsite replication for the workloads we run, with retention you set. Triple-replicated on the same storage tier behind the VMs.
Tell me morecPanel hosting
Shared and reseller hosting on cPanel, plus fully-managed deployments where we handle the platform end-to-end. Built for agencies and developers who want to focus on the application.
Tell me moreWhat's behind the VM
The compute, storage, and network choices that shape what the workload feels like from inside.
Compute. Single-socket and dual-socket nodes, with the core count to match the workload.
Storage. Triple-replicated across separate hosts, with snapshots and offsite replication available as a service.
Internal network capacity. East-west traffic stays inside our backbone, never the public internet.
The trust signals, plainly
What we'll commit to in writing and what's behind the commitment.
Compute platform across the cloud. New nodes added at each refresh cycle.
Triple-replicated all-NVMe storage. No spinning disk in the storage path.
Internal network capacity. Storage and inter-VM traffic on our backbone.
Outbound traffic on our own autonomous system. Same network the rest of the platform sits on.
Two Troy datacenters, SOC 2 Type II audited. PCI-compliant facility.
Operating continuously. We just didn't call it cloud back then.
Production workloads, production infrastructure
Three workloads, three customer profiles, three case studies. Names withheld; the engineering is what we'll talk about.
A regional digital agency hosts their customers' workloads on our cloud, across hosting, DirectAdmin management, colocation, private cloud, and disaster recovery.
Read the case studyA global VoIP carrier runs production voice across our cloud and network. Uptime matters because their customers hear it inside the same second the monitoring graph does.
Read the case studyA cloud security platform announces anycast IP space out of our infrastructure across multiple regions, with the storage and compute behind it operated by us.
Read the case studyQuestions IT directors actually ask
The ones we get on the first call from someone comparison-shopping cloud. If yours aren't here, the answer is on the other end of the phone.
Can I bring my own images, or only yours?
Both. We have a catalog of standard Linux and Windows images that boot in minutes, and we'll accept a custom image you upload (VMDK, qcow2, OVA, or a raw disk). For migrations from VMware, Hyper-V, or another cloud, our team handles the conversion and the cutover; you don't need to rebuild the VM.
What does migration assistance look like?
For a small workload, we send instructions and stay on the phone while you cut over. For anything past a handful of VMs, our engineering team scopes the migration with you, runs the test environment in parallel, schedules the cutover with you, and is on the bridge when it happens. Migration time is billed at standard rates or rolled into the contract.
How do backups work, and can I get them offsite?
Managed Backups is a separate service that snapshots the VMs on a schedule you set, with retention you set, on the same Ceph storage triple-replicated across the cluster. Offsite replication to our second Troy facility is available; cross-region replication to another provider is also available where the contract calls for it.
Where does the data live, physically?
Two Troy, Michigan datacenters that we own and operate. 600 Executive Drive is the primary; 319 Executive Drive is the second facility. Both are Tier III+, SOC 2 Type II audited, PCI-compliant. Customer workloads can be placed in one facility or both depending on the redundancy contract.
What hypervisor do you run?
Proxmox on the current-generation platform, with KVM as the underlying hypervisor. Older private-cloud deployments running OnApp are still supported through their migration window. The hypervisor itself isn't usually a customer-visible decision; what matters is the network, storage, and operations underneath. If your application has a specific dependency, tell us in the quote and we'll confirm.
Big enough to deliver, small enough to care
Tell us the workload. The shape, the SLA, the migration. We'll quote what fits. If that's not us, we'll point you to who.
Get in Touch