BETA Testing area — experimental features. Data here is separate from production and may be reset.
Tester environment
Beta.
Access is checked by the server.
This page is only rendered when /api/beta/status accepts your session. The obscure URL reduces accidental discovery only — access needs an account, a confirmed email address and the Tester role, all verified server-side.
Beta access required
—
A normal customer account cannot open the Beta. A Tester flag is granted by an administrator in the admin panel — it can never be set from the browser.
Signed in to the testing area
—
Feature flags
Evaluated on the server from the Beta configuration. The browser only renders what the API reports — flipping something here in DevTools does nothing.
Loading…
Experimental tools
Small, self-contained probes that are only reachable with the Tester role.
A ticket is single-use, expires in 120 seconds, and can only be redeemed by the same Tester account. It exists so an independently deployed Beta host can start a session without sharing the production cookie.
Beta feedback
Stored in the Beta feedback table (beta_feedback), which production never reads.
AetherAccount