Indicative examples — sizing based on quote (depending on workloads and hardware configuration).
Allocated vCPU are indicative, depending on CPU variant and workloads.
Storage refers to internal SSD/NVMe (node-local).
*25 GbE available with the 285HX variant.
How it works
1
Qualification
15–30 min
We align on goals, constraints and priorities (security, performance, budget, timeline).
2
Sizing & pre-configuration
We size the box and prepare the setup (network, access, governance, templates).
3
Delivery & setup
Box shipped ready to plug in. You connect it, we validate remotely and bring your first workloads live.
On-site installation available on request.
4
Operations & support
Support, updates and guidance depending on the plan.
Frequently asked questions
On your premises (on-site). No third-party hosting by default.
Yes: VLAN/network integration, VPN access, and gradual adoption alongside your current setup.
After a short qualification and sizing step, go-live is quick (depending on delivery and network constraints).
Yes. We provide a method and best practices for gradual migration. A complete migration service can be offered through partners, depending on scope.
Scheduled backups, snapshots when needed, and restore procedures you can test.
You stay in control. CloudCan can provide support and operations depending on the plan.
Network segmentation, traffic control, admin VPN access, and hardened components.
No lock-in: standard formats, VM/data export, and documentation. Assistance is available for migrating to another platform or a second site, depending on scope.
Yes. You can scale your capacity in several ways: Scale-up (increase CPU/RAM/SSD resources on existing Boxes), Scale-out on-site (add one or more Boxes to extend compute and storage capacity), or Multi-site CloudStack (add a zone on a remote site — second site, colo, datacenter — to increase capacity or bring workloads closer to users). Network requirements (VPN, latency, addressing) are defined in the quote.
A CloudCan Box is deployed on your premises (office, server room, rack). Typical prerequisites include: a stable network connection, a validated addressing plan (IP/VLAN), DNS access (internal if needed), and suitable physical conditions (power, space, ventilation). We validate these points during scoping before deployment.
Yes. The compact form factor of CloudCan Boxes is designed to be easy to move and redeploy: you can relocate a Box (office, server room, another site) and reconnect it to power and network. Depending on the environment, a brief network revalidation (IP/VLAN/DNS/VPN) may be required. CloudCan can assist you in preparing a relocation with a minimal switchover window.
Yes. CloudCan Boxes are well-suited for edge deployments: running applications close to the field (branch office, industrial site, retail location, remote site) to reduce latency, keep data on-site, and continue operating even with limited connectivity. For multiple sites, you can deploy one Box per site and operate them as a multi-site setup (CloudStack zones), depending on the chosen architecture.
