Three access plans for the bench, quoted with the test plan
Hourly sessions for one acceptance, a monthly subscription for release regression, a dedicated rack for teams that test every week. Every plan comes with reserved units, automatic patching, an engineer on chat and the report format from the service pages. There is no public price list: the quote follows the test plan in 1–3 business days.
- 1–3 daystest plan and quote
- 0public prices, every quote with a plan
- 3plans, one bench behind them
- 1 chatengineer in every plan
Compare
What each plan includes
The bench, the instruments and the engineer are the same in all three. The plans differ in how long the units stay yours and what is kept between runs.
| What you get | Hourly sessions | Subscription | Dedicated rack |
|---|---|---|---|
| 01Bench time | a day or a week, per booking | hours per month, booked in the portal | all year, your rack |
| 02Units | reserved for the booking | reserved per session, same set each time | yours and ours, patched on demand |
| 03Your device | one unit or VM for the booking | stays in the rack between sessions | as many as the rack holds |
| 04Suites and topologies | written for the run, handed over | kept and rerun on every release | kept, grown by your team and ours |
| 05Who runs the tests | our engineers, or yours under the plan | your engineers, ours on chat | your team, our engineer on the plan |
| 06Report | per run, signed | per release, with the comparison table | per run or per release, your format |
| 07Fits | one acceptance, a rerun, a dispute | release regression, yearly checks | vendors and labs without a rack of their own |
Capacities on every plan: L2-3 at 1G, 10G and 100G, L4-7 and security at 200 Gbit/s and more, WAN emulators, Wi-Fi up to 6, RoCEv2 agreed per setup
Which plan
Pick by the question, not by the device
The same firewall can be an hourly session before a purchase and a subscription once it is in production. The plan follows the decision you make with the results.
-
1
Hourly sessions
one decisionA tender, a device on trial, a rerun after a dispute. You book a day or a week, the units are reserved, the run ends with a signed report and the suites in your hands
From a day
-
2
Subscription
a release cycleFirmware every quarter, the same suites every time. Hours per month on the bench, your device stays in the rack, the report adds a column per release
Monthly
-
3
Dedicated rack
a teamYour units and devices in a reserved rack, our instruments on the same field. Your engineers run what they need, ours keep the bench current and step in on the plan
Long term
In every plan
The bench comes with the engineers, in every format
Instruments are never hired out on their own. Whichever plan you pick, a TEST4NET engineer writes or reviews the plan, is on chat during the run and signs the report. That is what keeps the result usable in a dispute with a vendor.
- 1–3 days
- from brief to test plan and quote
- Live
- counters, captures and console in every session
- NDA
- before any device detail is shared
Prices are quoted per project or per plan after the test plan is agreed
How to request
From this form to a booked session
Send the device, the question and the dates. The rest is on us until the quote is on your desk.
-
1
Brief
day 0The form below or a call: device model, the decision behind the test, preferred dates, who runs the tests
Call booked within a day
-
2
Plan and quote
days 1–3Test cases, thresholds, traffic profile, units reserved, plan recommended. The quote comes with it
One document to approve
-
3
Access
after approvalPortal accounts for your engineers, the device shipped or the VM uploaded, the first session on the calendar
Session opens on the booked day
How CloudLAB works Hosted DUT and remote access Why TEST4NET
FAQ
Questions before you request a plan
Why is there no price list?
A price depends on the units reserved, the hours and whether our engineers or yours run the cases. A list would either hide that or be wrong for most projects. The quote comes with the test plan, so you see what you pay for before you approve it.
Can we switch plans later?
Yes. An hourly session before a purchase often turns into a subscription once the device is in production. Suites, topologies and the report history carry over; nothing is written twice.
What is the minimum booking?
One day for hourly sessions; the term of a subscription or a dedicated rack is set in the contract. A single run usually takes two weeks from the first packet to the signed report, so a day is for reruns and short checks.
Do our engineers need training on the instruments?
No. The test plan is loaded and the units are configured by us. Your engineers start, stop and repeat cases in the portal and work on the device console. Instrument-level changes go through our engineer on chat.
Can we bring our own test equipment into a dedicated rack?
Yes. Your units sit in your rack on the same patching field as ours. We cable, power and patch them; licences and support stay with you.
Ask for a plan and a quote
Device, question, dates. Test plan and quote in 1–3 business days.
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.