TeamSigner

TeamSigner makes sure no single person can trigger your most critical operations. You decide how many people must approve, and nothing happens until they do.

THE ACTION IS WHATEVER YOU WANT IT TO BE

This is the important part: TeamSigner does not do the thing. You do.

An "action" is anything your own systems can already perform. Locking a production database. Revoking an employee's access. Shutting down a server. Releasing a payment. Wiping a device. Publishing a release. Opening a door. If you can trigger it with a request to your own endpoint, TeamSigner can put a team approval in front of it.

You set the action up on your side. You give TeamSigner a name for it, how many approvals it needs, and the address on your system to notify. When your team approves, TeamSigner sends the approved, signed result to that address and your system does the rest. We never touch your infrastructure and we never decide anything for you.

HOW IT WORKS

1. Define an action. Give it a name, set how many approvals are required, and point it at an endpoint you control.
2. Anyone you authorise raises a request, with an optional reason for the record.
3. Each member approves on their own phone. The approval is signed by a key that was created on that device and never leaves it.
4. Once the threshold is met, TeamSigner delivers the signed result to your endpoint, and your system carries out the action.

WHAT'S IN THE APP

Teams and roles. Invite members with a code, manage the roster, and let admins control who can define actions and who can raise them.

Actions on your terms. Set the approval threshold, how long a request stays open before it expires, where it gets delivered, and exactly which members are allowed to raise each one.

Live approval tracking. Watch a request move from 1 of 3 to 3 of 3 as it happens, see who has approved, and cancel one that was raised by mistake.

A full activity trail. Every request, approval, delivery attempt and response, timestamped. Open any delivery to see the exact call that was made and what your endpoint replied.

Test mode. Rehearse the entire flow with a test flag, so your endpoint can confirm everything works without acting on it. Plus a one tap check that your endpoint is reachable.

Multiple devices. Each of your devices holds its own approval key. Lose a phone and you revoke that device; the rest keep working.

Key sync checks. Confirm that the keys your own system trusts still match your team's, so a mismatch is caught in advance instead of in the middle of an emergency.

BUILT SO YOU DON'T HAVE TO TRUST US

Approval keys are generated on your device and held in the secure keychain. The private key never leaves it and never reaches our servers. Every delivery to your system carries each approver's signature along with a signature over the whole message, so your endpoint can verify for itself that the approvals are genuine before acting on them. TeamSigner relays the decision. Your system is what makes it real.

WHO IT'S FOR

Infrastructure, security, operations and finance teams that want a second, or third, pair of eyes before something irreversible happens. Four eyes principle, separation of duties, break glass access, change approval: the controls your auditor asks for, without building the approval layer yourself.

Free while we're getting started.