Skip to content
Gasket

About

Gasket exists because the useful agents are the ones that can do things, and the things worth doing are the ones you can’t take back.

Why Gasket

An agent that can only read is a search box. The value arrives when it can refund the customer, merge the fix, update the record, send the email. Those are also the moments where a confident mistake costs real money or trust.

Most teams handle this with prompt instructions, a wrapper function, or by not letting the agent act at all. None of those give you a decision you can point to later. Gasket is the missing layer: a place where every consequential action is asked for, decided by rules you wrote, held for a person when it should be, and recorded.

Principles

  • Fail closed. Silence, ambiguity or a missing rule means no.
  • Decide before, not after. A log you read after the refund is history, not control.
  • Readable rules. If you can’t say a policy out loud, you can’t review it.
  • One record. Request, decision, rule, approver and result belong together, with one id.
  • Nothing invented. No made-up customers, metrics or capabilities on this site. What isn’t built is labeled planned.

Where Gasket is

Gasket is early. The API, MCP server, policies, approvals, activity and usage billing are live and documented. Credentials storage and official SDKs are on the roadmap. The changelog records what ships.

Talk to us

Questions, a use case you want to try, or a security report: contact reaches a person.