Managed standby
Managed standby
Live
A hot standby built so only one of your nodes votes at a time: Pipe's fence leases the voting right to one node per validator, with a fencing token and a signed audit log, and your agent switches identity only under the lease. Your keys stay on your machines.
Included in: Managed standby.
Each lease and the audit log are signed by the fence’s own key, listed in /attest/keys.json; the fence holds no validator key.
Endpoints
Served from http://186.233.184.235:8080. Send a key as Authorization: Bearer psol_…. Indexes and status files need no key.
/standby/v1/enroll/standby/v1/lease/standby/v1/lease/<identity>/standby/v1/audit/<identity>
pipe-standby-agent keygen --out /etc/pipe-standby/node-key.json
pipe-standby-agent enroll --config agent.json --identity-keypair identity.json --node mia-a=<key> --node ams-b=<key>
pipe-standby-agent run --config agent.json
pipe-standby-agent audit --config agent.jsonAccess and limits
standby: The managed standby's fence: enrollment, the voting lease (acquire, renew, release), the lease view and the signed audit log.
| Plan | standby | Data a month |
|---|---|---|
| Managed standby | 10 requests a second, bursts of 40 | 100 GB per key |
Limits apply to each key; the free tier’s apply to each address. Prices for each plan are on the plans page.