Guards

You decide what a client can touch.

Every field category on your site carries a permission level. Open lets the client edit freely. Warn asks first. Review hides it and sends it to you. Locked blocks it entirely.

No credit card, cancel anytime.

Benefits

Why the boundary holds.

  • Set once, holds everywhere

    A guard is a policy on a field category, not a rule you repeat per page. Set headings to Warn and it holds across the whole site.

  • Code only gets stricter

    Structural and code fields start at Review and can be tightened. There is no setting that opens them to a client.

  • Search-facing fields ask first

    Page title, meta description and the on-page heading default to Warn, so a client is told what they are about to affect.

  • Nothing silently fails

    A blocked request is not an error message. It is held and routed to you with the client's own words.

How it works

From default policy to your policy.

  1. 01

    Mapping assigns defaults

    When a site connects, every editable field is sorted into a category with a sensible starting level.

  2. 02

    You adjust the policy

    Settings has one control per category. Change a level and it applies to the next edit.

  3. 03

    The client edits inside it

    Open fields go straight through. Warn fields show a heads-up. Review fields are never offered.

  4. 04

    Anything stricter routes to you

    A Review or Locked field becomes a request in your inbox instead of a dead end for the client.

Use cases

What this actually looks like.

  • A brochure site for a cautious client

    Leave body content, links and images open, keep titles and headings at Warn, and the client can do everything they actually need.

    Example

    The defaults already read this way: body content, links and images Open, page title and meta description Warn, structural and code at Review.

  • A site where SEO is the deliverable

    Move page title and meta description to Review, so every search-facing change comes through you first.

  • A client who has broken something before

    Set the categories you do not trust to Review. They can still ask, and you still get the request.

  • A site still under construction

    Tighten everything while you build, then open it back up at handoff.

Pricing

One plan, priced per website.

Everything included. $39 a month for 5 sites, then $10 each.

50% off for 12 months

with code BREW50 for the first 20 customers (11 left)

Monthly

$39/mo

Billed monthly.

Websites
5 included
Extra sites
+$10 each/mo
  • Chat edits with schema-validated publish
  • Multi-page, blog and multilingual sites
  • One-click revert and version history
  • SEO-sensitive field warnings
  • Teammates and a shared team inbox
  • Email and Slack escalations
  • Guards policy for field permissions
  • Staged drafts and audit trail
Start for $0

Yearly

Save 33%
$26/mo

Billed $312 yearly. Save 33%.

Websites
5 included
Extra sites
+$10 each/mo
  • Chat edits with schema-validated publish
  • Multi-page, blog and multilingual sites
  • One-click revert and version history
  • SEO-sensitive field warnings
  • Teammates and a shared team inbox
  • Email and Slack escalations
  • Guards policy for field permissions
  • Staged drafts and audit trail
Start for $0

FAQ

Guards, answered.

Open, the client edits freely. Warn, editable with a heads-up before publishing. Review, hidden from the client and sent to you as a request. Locked, hidden and blocked entirely, chosen per field.

Stop being the person who updates the phone number.

Give your client the keys to the content. Keep the keys to the code.

Prefer to talk first? Book a 30-minute call