Skip to content
Pricing

Try it together.
Bring it to your team.

Try the shared button demo, where two people fix a broken contact button on a fictional studio site, or bring a real pull request into a client review. Repository projects keep people and context for the next review; commercial team setup is agreed separately.

Try together

Request a real client review · Your projects · Connect an agent with agreed limits.

The shared trial needs no account. Team setup starts with an enquiry, not a checkout. Prices exclude taxes and are in US dollars.

Disposable demo repository · fictional invoices · no real paymentsEvery demonstration keeps its own sample authority and is separate from the fourteen-day Team trial.
Free
$0forever

Try the shared job, write a supported standard, or check a record.

Available now · no account needed
  • The shared coding trial: a real pull request in a disposable repository, two approvals, a receiver-applied change, an accepted result
  • The invoice examples: a guided walkthrough, a live agent when available, and rules rehearsal
  • Draft supported requirements, review the readback, and sign in your browser
  • Verify supported evidence files locally
  • The open gateway for your own deployment

Setting standards and checking records remain free. Your own deployment and model usage have their own costs.

Team
$200per workflow per month · founding-team pricing

For recurring work that has to prove itself to someone else, such as every change to one client’s website. Fourteen days free, then monthly until you cancel.

Manual setup · scope agreed before the free days start
  • Checks enforced and recorded on the workflow’s configured routes
  • Shareable check links; unlimited agents, approvers, and recipients
  • Email and call support on Sydney business days, best effort

A workflow is one standard in force: one recurring kind of work under one set of requirements. The fourteen days start once we have confirmed your setup and the first standard for it is signed. When they end, Team continues and is invoiced monthly unless you cancel by email before then; we remind you at least three days before. Founding-team pricing is held for twelve months. Payment and cancelling.

Design partner
$500per month · month to month

The first five teams. Team for one workflow, plus us in the room. Cancel any month by email.

Manual setup · by agreement
  • Everything in Team, for one workflow
  • A weekly working session with the founder
  • A say in what gets built next
  • A case study you approve before publication
  • Custom integration scoped and priced separately
For your own workflow

Agree the scope. Put the controls in place.

We set the first teams up by hand while self-serve billing is built.

  1. 01

    Choose one workflow

    Name the work, the person who reviews it, and the systems involved. We confirm supported checks, setup needs, and commercial terms with you.

  2. 02

    Write and review the standard

    Set limits, approvals, and evidence requirements. Review what is supported before signing. You can write one now in the advanced editor.

  3. 03

    Connect, test, and share

    Configure the gateway for the agreed routes and check its behavior. Run a bounded job, review the exported evidence, and have your recipient check the result.

Details: what installs where, and what it touches

The open-source gateway sits between an agent and its tools. It reads the configured policy, checks calls on the routes you put behind it, and writes receipts. A tool call that bypasses it is outside that coverage. Sharing an evidence file is always a separate choice.

Read the gateway setup commands and deployment requirements. Comparing records and verifying a downloaded file can run locally in your browser.

Details: connect a source system

For a team that has started, an evidence source (a CSV export, an API, or a signed file delivery) can be described so its records carry the source’s confirmation. A reviewer must confirm the mapping. Prepare a source connection.

Details: what a design-partner engagement covers

One real question your team cannot close today, bounded to one period and one source. Week one fixes the standard with the person who must rely on the answer and connects one read-only source. Week two produces the proof, tests the evidence for staleness, gaps, and alteration, and ends in a signed decision: accept, reject, or request inspection. A signed “not established” is a valid outcome.

Historical, read-only evidence at a point in time. Continuous assurance is outside that engagement; enforcement on live routes is a separate step you configure and activate.

Data and trust

Choose the mode with its data path in view.

Hosted collaboration

A shared room uses the service

ScopeBlind stores the room’s names, agreement, sample records, actions and results, and runs its sandbox gate and ledger. Browser signing keys stay in their browsers.

Guided
Scripted requests; no live model.
Live agent
The brief and sample records go to the model provider. Your own agent may send them to its configured provider too.
Two-person agreement
Shared mandates and proposals are visible to both people. A private brief is available to its author, their authorized agent, ScopeBlind, and the hosted provider when used. Shared exports omit private briefs.
Rules rehearsal
Tests run in isolated service ledgers. Optional readback sends your text and sample invoice context to the model provider.
Configured local gateway

Your setup defines the boundary

The installed gateway evaluates configured tool calls and writes receipts locally. Credential isolation and coverage depend on your agent, hooks and destination setup.

Your agent’s model and tools have their own data paths. Optional reporting sends disclosed receipts to a hosted standard page; exports share the files you select.

Verification and sharing

Checking a file runs locally

Files opened in Verify are checked in your browser without uploading their contents. A local CLI check can also run offline once its software and files are available.

Publishing a standard or creating a hosted share sends the selected content to the service. Downloaded exports and proof-carrying links disclose their contents to whoever receives them.