Service Update

Intake Forms Now Show Submission Status and an Email Fallback

How Helixrack intake and beta forms report form-service returns, show failures clearly, and provide a direct email fallback for customers.

A request form reaching the relay, with confirmation, visible failure, and email fallback paths.
A request form reaching the relay, with confirmation, visible failure, and email fallback paths.

On July 15, 2026, we updated the server-intake and beta request forms so the browser reports whether it returned from the form service or received an error response. Both forms also provide a direct email fallback.

What the return message means

A completion message means the browser returned from the form service after a submission attempt. It does not prove email delivery, staff review, deployment approval, or a reserved receiving slot.

Wait for a written reply from Helixrack before shipping hardware. That reply is where we confirm fit, current pricing, the receiving label, dock details, and the next step for the specific machine.

If the form reports an error, or if you need to follow up before a staff reply arrives, email hello@helixrack.com. Include the hardware model, approximate size and power draw, expected workload, and the best way to reach you.

Keep sensitive information out of the request

The forms are for planning and intake details. Do not submit passwords, private keys, recovery codes, payment-card data, application data, or other secrets. A hardware review does not require them.

Use the server-intake form for a standard server request or the Homelab Beta invite page for an eligible desktop or tower system. The current privacy language and form behavior appear on those pages.