One API origin
Every SDK submits to api.fingerly.io. There is no host to look up and no region segment in a key to get wrong.
One API. One place.
Fingerly runs as a single cluster in the European Union. Your account, your keys and everything identified through them are served from it, archives and backups are kept in object storage in the United States, and there is nothing to select at sign-up.
- European UnionWhere the cluster runs.
- One clusterEvery account uses it.
- Backups encryptedBefore they leave the server.
- Nothing to pickNo residency setting to get wrong.
[ 01 / 05 ]One cluster
Not a region you pick. A cluster we run.
Plenty of platforms hand you a residency dropdown and then make the choice permanent, so the first decision you make is one you cannot revisit and cannot verify. Fingerly does not have that dropdown. There is one cluster, it runs in the EU, and every account uses it. Long-term storage is the one part outside it: archived submissions, analytics older than two days and encrypted backups live in object storage in the United States.
The shape we are building toward is the one a managed datastore gives you: a multi-region cluster, where the geography is the unit and the machines inside it are ours to place, replace and spread. Today that cluster is a single EU deployment. It is worth saying plainly which of those two sentences describes what is running: the first is the direction, the second is the fact.
- Servers and databases in the EU, in France
- Archives and backups in US object storage
- No per-organisation residency setting
- Backups encrypted before they leave the machine
[ 02 / 05 ]What lives where
What lives where.
The cluster serves everything; long-term copies live in object storage.
| Data | Where | Notes |
|---|---|---|
| Users, organisations and memberships | EU cluster | Your account and your team |
| Billing and credit | EU cluster | Payments, balances and top-ups |
| SDK keys and proxy credentials | EU cluster | Stored hashed |
| Visitor IDs and recent identifications | EU cluster | The last two days of analytics on the servers |
| Risk weights | EU cluster | Your scoring policy |
| Webhook endpoints and deliveries | EU cluster | Signing secrets encrypted at rest |
| Archived submissions and older analytics | US object storage | Kept for their retention period |
| Backups | US object storage | Encrypted before they leave the server |
[ 03 / 05 ]Routing
One address. Nothing to configure.
Every SDK knows where to go, and none of them can be pointed anywhere else by accident.
Proxies forward to us
A first-party proxy runs on your own domain and forwards to Fingerly and nowhere else. In the Cloudflare Worker the upstream is a constant in the source, not a setting.
Your own endpoint wins
Point an SDK at your proxy and it uses it. That is the one place where traffic goes somewhere you chose, and it is under your control rather than ours.
[ 04 / 05 ]Questions
Can we choose a region?
No, and there is nothing to choose. Fingerly runs one cluster, in the European Union, and every account uses it. If you need data kept in a specific other jurisdiction, talk to us before you integrate rather than after.
Is our data replicated outside the EU?
Yes, for long-term storage. The servers and databases run in the EU, while archived submissions, analytics older than two days and encrypted backups are kept in object storage in the United States. The privacy policy describes these transfers.
Does EU hosting make our deployment compliant?
It supports your residency requirements, but it is not a legal determination on its own. Your notices, agreements and any transfer mechanisms still need review by your privacy and legal teams.
Less guessing. More knowing.
Make the next connection a trusted one.
Start with the signals, keep your own decisions, and pay only for what you identify. No credit card needed.