Multi-region signing
Fortkey is deployed in multiple regions to minimize latency between your trading strategy and the signing engine.
How it works
Global signing replicas do not carry the full platform; they run only the signing endpoint, tuned for the hot path. Policies and access rules are applied to wallets globally in near real time, so a rule you change in the console is enforced at every region.
Bots choose where to sign so they get the lowest possible latency to their venue.
Endpoints
| Endpoint | Purpose |
|---|---|
api.fortkey.io | Main API. Full functionality, including login. |
sign.fortkey.io | Latency-routed: resolves to the signing replica closest to your bot. |
tokyo.fortkey.io | Region-pinned signing replica (example: Tokyo). |
Endpoint hostnames for your deployment are provided during onboarding.
Current regions: Ireland (main) and Tokyo. Additional regions can be deployed on demand; the platform can run in any AWS region.
Usage notes
- The structure of the signing request, including authentication headers, is identical on every endpoint.
- Login happens only on the main API, not on signing replicas. Authenticate once, then sign anywhere.
- Policy changes propagate globally; in testing they reliably take effect within seconds, with a worst-case bound of a few minutes due to caching.