Skip to content

Prove your agent's writes land, on up to three write tools, with us.

A pilot is founder-assisted: we write outcome checks for up to three of your state-changing write tools, add them to your CI against a test account you create, and send a fix report with evidence. Everything runs on your machines.

Prefer email? Write to hifzabuild.ai@gmail.com.

Five steps, from scope call to review.

  1. 1

    Scope

    30-minute call

    Pick up to three state-changing write tools that matter, and the API that can confirm each write.

  2. 2

    Contracts

    written with you

    We write the outcome contracts for those tools with you; you review and approve them.

  3. 3

    Test-account scan

    fourgate scan

    Run against a test account you create to prove each contract: a healthy write is PASS, a deliberate mismatch is FAIL.

  4. 4

    CI job

    pull request you merge

    We add the checks to your CI through a pull request you review and merge. They run against your test account.

  5. 5

    Fix report

    review call at day 30

    We send a fix report with evidence for anything that says success without doing it, and review it with you on a call at day 30.

What you get

  • Founder-assisted setup
  • Outcome contracts for up to three write tools, reviewed with you
  • A CI job added through a pull request you merge
  • Fix report with evidence: PASS / FAIL / UNKNOWN
  • A review call at day 30
  • Fourgate Founding Pilot: $300 one-time, invoiced after the scope call. Ongoing support after the pilot is optional, by agreement.

A short evaluation on a staging environment or a disposable account can be free.

Requirements and limits

  • Limited beta 0.4.0b1: local command-configured stdio only. Customer CI, Desktop UI, and production reliability are unvalidated. No remote MCP transport, no hosted endpoint, and no telemetry.
  • Read-back is an HTTPS GET to an API that can return the written record, authenticated with a Bearer token, a custom header (e.g. X-Api-Key), Basic auth, or no auth.
  • Each check is capped at 2000 ms. On a Windows laptop the HTTP verifier measured 1.2–1.6 s per call, so add this latency to protected calls.
  • Contracts are written by hand and reviewed by a human.
  • Python 3.10+. Tested on Windows and Linux.

Where your data goes during a pilot. Nowhere near us unless you choose. There is no Fourgate cloud, account, database or telemetry, and Fourgate never stores your credentials. The summary page is built to be shareable, and sharing it is your decision. Full detail: PILOT.md and the security page.

Ready when you are.

Bring up to three write tools and the API that can confirm their writes.