Access and scope

Glide is built with design partners. It is not a self-serve product.

This page states what is decided about how it works, and what is not.

Glide does not act on its own during a visit.

How a change reaches pre-production

A change reaches pre-production as a preview the live-site owner can open. It is never a script that edits the live page.

Nothing in Glide changes a live page until a person has read it.

The person reads a review packet, not a preview link and a click: the change on every touched screen side by side, the hypothesis and predicted impact, the policy checks line by line, accessibility and performance results, the traffic slice, stop rules and rollback.

  1. Rules you wrote, locked
  2. Glide proposes a change
  3. Pre-production: a preview the live-site owner can open
  4. A person reads the packet and signs
  5. A slice of live traffic moves. The holdout stays on the original.

Price display. Checkout contract. Never changed.

Illustration. A change is prepared in pre-production, read by a person, then a slice of live traffic moves while a holdout stays on the original. Price display and the checkout contract never change.

The size of the holdout is set per journey, from its traffic.

What Glide reads and what it never touches

Price display and the checkout contract stay frozen.

Changes land on landing, product and cart screens. Checkout is measured, not changed. Nothing changes on the payment step. Rules are written by the customer. Each rule becomes a check the change must pass.

What personal data Glide reads, if any: To be agreed with design partners.

How rollback works

A slice of live traffic moves after sign-off. A holdout does not. Rollback is one click and returns the slice to the original.

Scope today

Changes land on landing, product and cart screens. Checkout is measured, not changed. Email and app are measured for contradictions. They are not changed.

Not decided yet

These stay open until they are agreed with design partners.

Security certifications
To be agreed with design partners.
Data residency
To be agreed with design partners.
Vendor-access terms
To be agreed with design partners.
What personal data, if any, Glide reads
To be agreed with design partners.
How an approved change reaches live traffic, per platform
To be agreed with design partners.
How long a holdout runs
To be agreed with design partners.

This page claims no certification.

If one of these decides whether you can go ahead, say so in the conversation.

Talk to us about a design partnership