Install Signeto (self-hosted)
Rather not install anything? Try Signeto Cloud. We run the gateway for you: setup happens in the browser, and Claude Code gets one line to paste. Free for 14 days. Signeto Cloud is coming soon: get notified when it opens.
This page is the other way, available today: self-hosted, the free plan. The gateway, the part that holds your GitHub App's key and checks your phone's signature, runs on your own computer, and Signeto never holds your credentials. In about fifteen minutes, Claude Code asks your phone before it merges a pull request into main.
What you need
- A computer: a Mac, a Windows PC or a Linux machine.
- An iPhone, or an Android phone (Android 9 or newer) with the Signeto app from the App Store or Google Play, and Face ID or Touch ID, or a fingerprint or face unlock. Getting the app takes a minute.
- A GitHub repository you administer. It needs to be public, or owned by an account on a paid GitHub plan; see Private repositories on GitHub Free.
Get the app
Start on your phone. Install Signeto from the App Store or Google Play, create your account with your email (there's no password), and save a passkey (Face ID on iPhone, or your fingerprint or screen lock on Android). The app also makes its own key in the phone's secure hardware (the iPhone's Secure Enclave, or the Android Keystore); that key signs every approval. The same passkey signs you in at signeto.dev.
Choose your computer
Each guide starts from a fresh machine: what to install first, what each step of setup prints and what you do, and your first approved merge.
Already have Node.js, the GitHub CLI and Claude Code?
Then it's three commands. Signeto needs Node.js 22.13 or newer and Claude Code with the claude command on your PATH; setup also uses the GitHub CLI (gh), logged in as you.
npm install -g signeto
cd ~/code/your-repo
signeto setup
On a Mac with the Node.js installer from nodejs.org, the first command needs sudo: sudo npm install -g signeto. Global packages go in /usr/local, which belongs to root.
Run signeto setup from your repository's folder. It reads the repository name from the origin remote; pass --repo OWNER/NAME if that's not right. The GitHub CLI is optional: setup uses it once to create the branch ruleset, and without it, setup prints the ruleset to add by hand.
signeto setup runs seven steps. Each one first checks whether it is already done, so if you stop halfway (or something fails), fix it and run signeto setup again: it picks up where it stopped. On macOS and Linux it finishes by printing one more command for you to run with sudo (step 8), which it never runs itself. That needs your Mac's admin password (or sudo on Linux), once.
| Step | What happens | The command it runs |
|---|---|---|
| 1. Gateway | Creates this machine's gateway: its key, a starter policy, the ledger | signeto init |
| 2. Account | Signs you in to Signeto with your passkey and registers the gateway | signeto relay register |
| 3. Phone | Pairs your phone by scanning a QR code | signeto pair --relay |
| 4. GitHub | Creates a GitHub App for this gateway and protects your default branch | signeto setup github --protect |
| 5. Claude Code | Adds Signeto to Claude Code for this project | signeto connect claude-code |
| 6. Test | Sends a harmless request to your phone | signeto test |
| 7. Doctor | Checks the whole chain | signeto doctor |
| 8. System install | Moves the gateway to its own OS account, out of the agent's reach (macOS and Linux; Windows has no system install yet) | you run sudo signeto system install --from ~/.signeto |
Use the Node.js installer from nodejs.org (or your Linux distribution's package), not Homebrew's node. Step 8 copies node into a root-owned directory, and Homebrew's loads libraries from a folder your account can write, so the install refuses it. See Keeping Homebrew's node if you need it for other work.
How setup works explains what each step does and why. If a step goes wrong, see Troubleshooting.
Try it
Open Claude Code in the project and ask it to merge an open pull request into main. Your phone shows the merge: repository, pull request number, target branch, merge method and the exact commit, with a link to the pull request. Approve it, and the merge goes through with a green Signeto check on the commit. Deny it, and Claude Code is told you said no, with your reason if you gave one.
Afterwards (on Windows, without sudo):
sudo signeto ledger # every request, approval and result, hash-chained
sudo signeto github audit # every commit on main traced back to an approval
sudo signeto ledger export audit.html
Your approvals are also listed on the web: Sign in at the top of signeto.dev, then Ledger (api.signeto.dev/account/ledger), where your browser checks every signature itself.
Next
- Using Signeto day to day: what needs
sudo, changing the policy, upgrading, the emergency stop. - Troubleshooting: sign-in, devices, plan limits, private repositories, and errors by name.
- Removing Signeto:
signeto teardown, setup in reverse.
