Skip to content

Your device in our rack, your engineers on its console

A physical unit is shipped to the lab, cabled in the rack with KVM, serial and power control and patched to the generators. A virtual appliance is uploaded to the lab hypervisor. Either way your team opens the console in the browser, changes the config between runs and watches the counters, with no VPN client and no inbound ports on your side.

Host a device Access plans
One device, four ways in Everything reaches your unit through the portal over HTTPS
Your browser portal, HTTPS only HTTPS CLOUDLAB RACK Your device physical unit or VM KVM management port Serial console port Power reboot, hard reset Patching field to the generators VM: hypervisor console
  • KVM · serialon every hosted unit
  • 1 hto upload and start a VM
  • 0inbound ports on your network
  • 1 customerper topology and VLAN

Two formats

A box in the rack or an image on the hypervisor

Most firewalls, routers and switches come as hardware; load balancers, SD-WAN edges and virtual firewalls often come as an image. The bench takes both on the same patching field.

  1. 1

    Physical unit

    shipped to the lab

    Courier to Armenia with the customs paperwork we prepare. Cabled in the rack, management port on KVM, console on serial, power control on the outlet. Returned after the project or kept for the subscription

    In the rack 1–2 days after arrival

  2. 2

    Virtual appliance

    uploaded to the hypervisor

    OVA, qcow2 or vendor image uploaded through the portal. vCPU, memory and virtual ports as the datasheet asks. Console through the hypervisor, snapshots between runs

    Running within an hour

What you get

Access to the device, by path

Each path is a tab in the session window. Nothing is installed on your side; the portal is the only address your team needs.

PathPhysical unitVirtual applianceUsed for
01Management KVM on the management port, web UI and SSH through the portal web UI and SSH through the portal config changes between runs, log reading
02Console serial console, boot messages included hypervisor console firmware upgrades, recovery, crash analysis
03Power remote power control per unit start, stop, reset, snapshot cold boot cases, failover drills
04Data ports patched to the generators, 1G to 100G virtual ports on the lab switch, 10G the test traffic itself
05Files upload and download through the portal same, plus image and snapshot export firmware, configs, captures, reports

Sessions, console logs and captures stay in the project folder for the length of the plan and are deleted at the end unless you ask for an export

From your door to the session

Four steps for a physical unit

A VM skips the first two. The portal shows each step as it completes.

  1. 1

    Shipping

    days 1–5

    We send the address, the packing list and the customs text. You ship by courier; we track it and confirm arrival

    Device at the lab

  2. 2

    Racking

    1–2 days

    Mounted, powered, management and console cabled, optics checked against the test plan

    KVM and serial live in the portal

  3. 3

    Patching

    minutes

    The patching field links the data ports to the reserved generators and emulators as the topology in the plan says, without anyone touching a cable

    Topology matches the plan

  4. 4

    First session

    booked day

    Your engineers log in, load the config, run a smoke case with our engineer on chat. The project runs from here

    Run starts

Isolation

One customer per topology, nothing shared

Your device sits in its own VLANs on the patching field and the management network. Generator ports are reserved per session and released clean. Access is by named accounts per engineer; portal and console logs are kept for the project and are yours on request.

NDA
signed before the device details are shared
Named
accounts per engineer, no shared logins
Wiped
configs and images deleted at the end of the plan

A physical unit is returned with the config you leave on it. Ask for a factory reset before shipping and we do it on the console with you watching.

What is in place for a hosted device
Own VLANs per customer data and management networks in place Named accounts per engineer, revoked when the plan ends in place Session logs kept exported on request in place No inbound ports HTTPS to the portal only in place Deleted at the end configs, images, captures in place

FAQ

Questions about hosting a device

How CloudLAB works Access plans Firewalls and NGFW Routing and switching

What about customs and shipping back?

Temporary import for testing is the usual route. We prepare the packing list and the customs text, you ship by courier, and the unit goes back the same way after the project. Shipping costs are outside the quote.

Can the vendor ship the device directly to the lab?

Yes, and that is common in tenders. The vendor ships, you keep the console and the results, and the vendor sees only what you share. The NDA covers both sides.

How fast can we get to the console after shipping?

One to two days after arrival for a physical unit: racking, cabling and the optics check. A virtual appliance runs within an hour of upload.

Can we keep the device in the rack between releases?

Yes, on a subscription or a dedicated rack. The unit stays powered, patched and reachable; the next firmware is a rerun of the kept suites.

What if the device crashes during a run?

The serial console shows the crash, power control gives a hard reset, and the capture at the moment of failure goes into the report. That is often the most useful page in it.

Put your device on the bench

Model, format and the question. Test plan, shipping instructions and the quote in 1–3 business days.

Host a device Access plans

Send the shortlist

You have the method. Now get the numbers.

Name the models and the KPIs that matter. An engineer replies within one business day with a test plan draft and a quote.

Prefer to chat? Message an engineer on WhatsApp

We use what you send only to answer you. See our Privacy Policy.