Skip to main content
Pricing

Free for the pilot. Per managed device after it.

The guided pilot costs nothing for up to 30 days and up to 50 managed devices. Paid use is $12 USD per managed device, per month. A RedactWall employee confirms the seats and the terms before anything is billed.

Two states

A pilot, and then a paid workspace

Nothing about the product changes at conversion. What changes is what is billed, the device ceiling, and whether the workspace keeps admitting new devices.

Guided pilot

Free

Up to 30 days, up to 50 managed devices

A supervised first deployment with an agreed scope. Nothing is billed, and both bounds below are held by the product rather than by a sentence on this page.

What it includes

  • Up to 30 days, counted from the day the workspace is provisioned.
  • Up to 50 managed devices. A seat is a managed device. A browser sensor and an endpoint agent on the same machine share one seat.
  • The agreed pilot scope: the managed Chrome path, and the Anthropic gateway path where it is included and verified separately.
  • Evidence from your own environment, and the coverage and verification tools the rest of this site describes.

What it does not

  • Access on request. When the in-app pilot entry is available, choose Request a guided pilot and complete Auth0 verification with your work email. The app records your request after it verifies your identity and email. A RedactWall employee reviews the request before a workspace can be created. Sending a request grants no workspace access. If the in-app entry is unavailable, ask about the status of the pilot terms by email first. Employee approval and workspace provisioning are required before anyone receives workspace access.
  • Expansion past the agreed cohort. Each step up needs a verified release and a working rollback path.
  • New device enrollments after the 30 days elapse, until the pilot is converted.

Paid

$12

USD, per managed device, per month

Billed per managed device per month once a pilot converts. A seat is a managed device. A browser sensor and an endpoint agent on the same machine share one seat.

What it includes

  • The device ceiling confirmed at conversion, in place of the pilot ceiling.
  • The pilot expiry lifted once the payment is recorded, so devices keep enrolling.
  • The same product, the same scope and the same evidence. Converting changes what is billed and how long the workspace keeps admitting devices, not what is deployed.

What it does not

  • A published discount or a committed term. Seats and terms are confirmed by a RedactWall employee at conversion.
  • A self-service upgrade. The request is made in the console and reviewed before it is billed.
How you pay

Invoice by default. Card where it is configured.

Both paths bill the same price for the same confirmed device count. Which one a workspace offers depends on how that deployment was configured, and the console offers only the path it can complete.

Manual invoice

The default, in every deployment

A RedactWall employee confirms the device count and the terms, records the payment against your workspace, and invoices you. This is what happens when nothing else is configured, which is the state a deployment starts in.

Card, through Stripe Checkout

Only where that deployment has been configured for it

Where an operator has configured a Stripe secret-key file and a price id, the console can open a Stripe Checkout session for the confirmed device count. It runs in Stripe test mode today. A deployment without that configuration offers the invoice path only, rather than a control that cannot complete.

How conversion works

From one device to a paid workspace

These are the steps the get-started page publishes, read from the same list. The last one is the conversion this page prices.

  1. 1

    Confirm the fit

    Name a policy owner, the managed Windows 11 and Chrome cohort, and the ChatGPT workflow you want to govern. Identify any separate Anthropic application path.

  2. 2

    Request guided setup

    In the app, choose Request a guided pilot and complete Auth0 verification with your work email. The app records your request after it verifies your identity and email. A RedactWall employee reviews the request before a workspace can be created. Sending a request grants no access, enrollment, or coverage. A draft pilot agreement with processing terms has been prepared for counsel review. It has not been reviewed by counsel, agreed or signed, and it must be reviewed and agreed before any enrollment. Billing applies to paid conversion.

  3. 3

    Approve workspace access

    After a RedactWall employee approves the request, the workspace is provisioned and the requester is emailed as its owner. Your organization approves the policy and the people allowed to review evidence before enrollment.

  4. 4

    Enroll one managed device

    Start with one Windows 11 device and its managed Chrome profile. Confirm device health, the installed extension and the approved policy before use.

  5. 5

    Prove the path with synthetic data

    Run an agreed safe test, check what reached the destination, and match the decision to its evidence. Verify the Anthropic gateway separately when included.

  6. 6

    Expand after the proof

    Review failures and coverage gaps before moving to five devices, then the agreed cohort of up to 50. Each expansion requires a verified release and a working rollback path.

  7. 7

    Convert

    Request conversion from the Overview banner in the console. A RedactWall employee confirms the seats and the terms, you pay by invoice or by card where that deployment is configured for it, and the pilot expiry is lifted once the payment is recorded.

Read these beside the two cards

  • A pilot request is reviewed by a RedactWall employee before any workspace exists. Requesting one records the request; it does not grant access.
  • Card payment runs in Stripe test mode, and only where that deployment has been configured with a Stripe secret-key file and a price id. Manual invoicing is the path that always exists.
  • A pilot that is not converted stops admitting new device enrollments once its 30 days elapse. Devices already enrolled keep their policy; the workspace takes no new ones until the conversion is recorded.
  • This site takes payment from nobody. It is a static export: no Stripe key is published here, no payment form is rendered here, and this page makes no request to Stripe. Payment is arranged inside the console.

Conversion is requested from the Overview banner inside the console. Requesting a pilot does not grant access, and asking to convert does not bill you: a RedactWall employee confirms the seats and the terms first.

Price the pilot before you run it.

Confirm the scope with RedactWall, prove one managed device, and convert on terms a person confirmed.

  • Free for up to 30 days and 50 managed devices
  • $12 USD per managed device, per month once converted
  • Invoiced by default, card only where that deployment is configured