Critical actions,
approved by your team.
No single person can pull the trigger. TeamSigner collects cryptographic approvals from your team and only fires your system's webhook once enough of them agree.
Start using TeamSigner for free now!
Log in & get startedHow it works
-
1
Define an action
An admin sets up an action — a name, how many approvals it needs, and the webhook it should hit. Think "Lock database" or "Revoke access".
-
2
Raise a request
When something happens, any authorised member opens a request. The whole team is notified instantly on their mobile device.
-
3
Members approve on mobile
Each approval is signed with a key that never leaves the member's mobile device — so every approval is attributable and independently verifiable.
-
4
Threshold met → your webhook fires
Once enough members have signed, we deliver the signed payload to your endpoint. Your system verifies the signatures — and from there, it does whatever the moment demands: revoke a compromised GitHub token, lock a production database, freeze payouts, kill a leaked API key, page on-call. TeamSigner guarantees the authorization; your systems do the rest.
delivers the signed request ↓responds ↓
Approving requires the mobile app — your signing key stays on your phone. Everything else (teams, actions, raising requests, history) works right here on the web.
Or gate a merge.
Install the GitHub App and a pull request waits for a signed approval from a phone. Same signatures, no webhook to build.
About the GitHub plugin ›Why two people, not one.
Short reads on the controls TeamSigner enforces — what each one requires, and what an auditor expects to see.
See it applied
Break-glass access · Production database · Infrastructure teardown · Production deploys · Emergency kill switch · Payment release