About Services Tools Blog Contact us

Staging Password Gate

A shared-password lock screen for every page and data response on test and pre-launch sites, with a human check and a limit on attempts.

  • Security & Hosting
  • Cross-sector
  • Tool
  • Productised
  • Hybrid
  • 2026

The problem

A staging copy of a listed company's site, or any pre-launch site, must not be indexed or browsed before launch. A hidden URL is easy to find and is no lock.

What it does

On every site except the live one, the gate runs before any page or data is shown to a visitor who has not yet passed it. A password entry is checked with a security token and a Cloudflare Turnstile human check, and repeated failures lock the visitor out. Images, styles and scripts are not behind the gate.

Outcomes

  • Staging pages and API responses sit behind one lock.
  • Repeated failures pause further attempts.
  • The live host is unaffected.

Simplified mockup

Interactive preview with sample data. Nothing is sent to a server.

Staging password gate

Staging copy · not for index
North Quay Furnishings

Every page and API response stops here until the shared password, the challenge and the form token all pass.

Attempts 0 of 3 token gate_b31

Demo password: north-quay. Three wrong tries pause the gate for 60 seconds.

Ranges API

GET /api/ranges same gate

A locked visitor does not receive the range list. Styles, scripts and images never reach this check.

While locked
After the gate

What the gate skips

RequestStaging hostLive host
Page, visitor still lockedLock screenPage
API, visitor still lockedLock screenJSON
Visitor already clearSkipSkip
Styles, scripts, imagesNever reach the gateServed
Three failed postsPause 60 secondsNo gate
Each password post must include
Shared password Bot challenge Form token

How it works

  1. Run the gate before any page or data is shown on test and pre-launch sites.
  2. Let through visitors who already hold a cleared session, and skip images, styles and scripts.
  3. Require the shared password, a Cloudflare Turnstile human check and a valid security token.
  4. Lock out after repeated failures.
  5. Leave the live site ungated.

Pipeline

flowchart LR
  A[Request] --> B{Live host?}
  B -->|Yes| C[Page]
  B -->|No| D[Lock screen]
  D --> E{Password and Turnstile}
  E -->|Pass| C
  E -->|Fail| F[Lockout]