Deploy and operate
Choose who runs the io.sign backend, then deploy, configure, and run it
An io.sign deployment has a backend that coordinates signing, and signers that hold the key shares. You can run the backend yourself, or let io.finnet run it for you. Either way, your key shares stay on your signers.
Choose a deployment
Deployment options compares running the backend yourself with the io.finnet-managed backend, and explains where your Virtual Signers can run.
Run the backend yourself
- Try the backend on one machine with the Quick start.
- Plan your deployment with Configuration, which covers the components, prerequisites, and topology.
- Set up what the backend depends on:
- Authentication with your identity provider.
- The MQTT broker that signers connect to.
- The database, with backups and audit logging.
- The webhooks service, if you use webhooks.
- Install your licence.
- Set up logging, monitoring, and health checks.
The Configuration reference lists every setting.
Keep it running
- Migrations and upgrades explains how to upgrade to a new release, and how to roll back.
- Disaster recovery explains how to recover a vault if you lose access to enough signers to meet its threshold.
Updated 20 days ago
Did this page help you?