Configure your organization to start exchanging data.
1
Org Details
2
Key Generation
3
First Exchange
Step 1 of 3
Organization Details
Tell us about your organization. This information establishes your identity in the exchange network.
Comma-separated list of patient data categories for matching.
Step 2 of 3
Cryptographic Key Generation
An Ed25519 keypair is generated for your organization. The public key is shared with counterparties; the private key never leaves your infrastructure.
How key generation works
Squyr uses Ed25519 (RFC 8032) for signing data bundles. When you rotate keys, in-flight bundles are rejected to protect integrity.
Public key — shared with counterparties during exchange setup
Private key — never transmitted; used to sign bundles locally
Rotation — every 90 days; warnings sent 14 days before expiry
Public Key
→
Generated
→
Private Key
Your Public Key (shared with counterparties)
B7vK3xQpL9mYz4nRfH8jK2sT5wG6dN8aP3eX1cM9oU4Y
Key generated locally · private key stored in secure enclave
⚠ Rotating keys immediately invalidates the active Ed25519 key. In-flight bundles will be rejected. Schedule rotation during low-traffic windows.
Step 3 of 3
Invite First Counterparty
Start a bilateral exchange by inviting your first partner. They'll receive a secure link to join the network.
Each exchange agreement defines the data categories, match criteria, and transmission rules between your organization and a counterparty. You'll share your active Ed25519 public key (generated in step 2) with the counterparty when establishing the connection.
Invites are valid for 7 days.
HTTPS endpoint for real-time bundle delivery notifications.
