Calyraen
Searching the site...
No matches. Try another word.
Behind the bench

Inside a server before it ships.

Before a server leaves us, it has to earn its way out the door. Here is what happens on the test bench.

Why we test

We would rather find it here.

Every server we build spends real time on a test bench before it is boxed. The idea is simple. A weak part should give itself away on our floor, in a room full of people who can swap it in minutes, not months later in your rack when the team is counting on it.

So we assemble the machine, then run it hard. Not a quick power-on and a tick in a box. Hours of real load, watched the whole way, until the machine has proven it can do the work you bought it for.

On the bench

From bare metal to boxed.

Every server follows the same path before it ships. There are no shortcuts on a busy week.

  1. Assembled and configured

    The machine is built to your order and brought up for the first time. Firmware is set, every drive is recognised, and the fitted memory is confirmed down to the last stick.

  2. Burned in under load

    We push the processor and memory hard for an extended run and cycle the storage through reads and writes. This is where a marginal part gives up, on our floor rather than yours.

  3. Measured, not assumed

    Temperatures are watched under sustained load to confirm the cooling holds. Memory is scanned for errors across the full range fitted. Every port and every drive bay is checked against the spec sheet.

  4. Signed off and recorded

    A server only ships once it has passed each step clean. The results are saved against its serial number, so its history travels with the machine.

Closer look

The bench does the worrying.

One server, wired up and running flat out, with people watching the numbers. Nothing leaves this room on a maybe.

Imagery in production

A server mid burn-in, held under sustained load.

The checks in detail

What we actually look at.

Imagery in production

Processor and memory, under real load

We load the machine the way a busy week would, then hold it there.

A short test proves a machine can start. A long one proves it can keep going. We run the processor and memory near full for an extended stretch and watch for the smallest wobble. Memory gets its own pass. We scan every stick across the full range fitted, because a single bad cell can turn into a strange crash months from now. If it shows here, it never reaches you.

Imagery in production

Storage, read and written hard

Every drive is cycled through reads and writes before it holds your data.

Storage is where your work lives, so we do not take it on trust. Each drive and bay is exercised with real read and write cycles, and we confirm the machine sees every one of them at the size and speed it should.

Imagery in production

Heat and airflow, watched all the way

Cooling is proven under sustained load, not guessed from a spec.

A server that stays cool on an idle bench tells you nothing. We watch temperatures while the machine works flat out and confirm the cooling holds steady instead of creeping up. A server that runs cool runs quiet, and it lasts.

Imagery in production

Ports and bays, one by one

Every port and drive bay is confirmed to do what the spec sheet says.

It is an easy thing to skip and a miserable thing to discover missing. So we check each port and each drive bay against the spec before the panel goes back on. What you were promised on paper is what arrives on the pallet. Full specs and options live on the [servers page](/computers/server).

See the servers
“A weak part should give up on our bench, in a room full of people who can fix it, and never in your rack when the work depends on it.”
Our shipping promise
After the tests

The part that stays with the machine.

Imagery in production
The record

A history tied to the serial number

Every result from the bench is saved against the machine's serial number. If you ever call us about it, we can see how it left the line and start from there, not from scratch.

Talk to support
Imagery in production
The rule

One clean pass, or it stays

There is no partial credit. A server that stumbles on any step goes back to the bench, not into a box. Only a clean run through every check earns the shipping label.

Questions

Asked and answered.

How long does burn-in take?

Long enough to catch the parts that fail early, which is most of the ones that fail at all. We run an extended load rather than a quick power-on, and a machine is not boxed until that run comes back clean.

What happens if a server fails a check?

It goes back to the bench. The weak part is replaced and the machine starts the checks again from the top. Nothing ships on a partial pass.

Can I see how my server was tested?

Yes. The results are recorded against the serial number. Call us with the machine in front of you and we can tell you how it left the line.

Where are the full specs?

On the servers page, with every option laid out in plain numbers.

Keep reading

More from the newsroom.

See what else we are building, testing and learning across Calyraen.

We value your privacy

We use cookies to run this site and, with your consent, to analyse traffic and improve your experience. You can accept all, reject non-essential, or choose by category. Learn more

Strictly necessary
Required for the site to work — security, sessions, and remembering this choice. Always on.
Preferences
Functional cookies — remember your language, region and interface choices.
Analytics
Help us understand how the site is used so we can improve it.