MEET FINGERLYA clearer picture of every session.Explore the signals
Keys, environments and roles

Scoped by default. Open by exception.

Every credential says what it is for and refuses everything else. Public keys work only from origins you list, secret keys refuse to work from a browser, and every member of your team sees only what their role needs.

  • Public keysOnly from allowed origins.
  • Secret keysBackend only, stored hashed.
  • EnvironmentsProduction, staging, development.
  • Four rolesOwner, admin, developer, billing.

Two kinds of key. Mirror images.

Each key belongs to one environment and one data region, and says both in its prefix.

  1. 01Public keys
  2. 02Secret keys
  3. 03Issued once, revocable
01

Public keys

Safe in a page, useless anywhere else.

Used by the browser and mobile SDKs. In a browser a public key must arrive from an origin on its list, and a key with an empty list refuses everything rather than allowing anything.

Prefix
fly_pk_us_production
Rules
Allowed originsEmpty list refuses all
02

Secret keys

For your backend, refused from a browser.

Read stored events and act as a trusted proxy. A secret key that arrives with a browser Origin is refused, so a key pasted into front-end code stops working instead of leaking.

Prefix
fly_sk_us_production
Rules
No browser OriginEvents of its own environment
03

Issued once, revocable

The secret is shown one time.

A key’s secret is shown at the moment it is issued and never again; afterwards the console shows only its last four characters. Keys can be revoked at any time, and can be issued with an expiry through the API.

Stored as
A keyed hash, never the secret
Actions
RevokeEdit originsExpiry

Four roles. No more access than the job.

Every organisation has exactly one owner. Everyone else is invited with the role their work needs.

CanOwnerAdminDeveloperBilling
Issue and revoke SDK keysYesYesYesNo
Manage webhook endpointsYesYesYesNo
Change risk weightsYesYesNoNo
Invite members and change rolesYesYesNoNo
Payment methods and top-upsYesYesNoYes
Transfer the organisationYesNoNoNo

Invitations are sent for the admin, developer and billing roles. Ownership can only be transferred.

Kept apart on purpose.

Test traffic never mixes with production, and nothing you register can be pointed somewhere it should not go.

Three environments

Development, staging and production keys are separate. Only production is billed, and every dashboard filters by environment.

Test environments

Webhooks, HTTPS only

Endpoints must use HTTPS and resolve to public addresses. Each has its own signing secret, shown once.

Webhooks

Trusted proxies

A first-party proxy authenticates with its own credential, and only a trusted caller may forward a visitor’s address.

Proxy integrations
[ IDENTIFY ][ UNDERSTAND ][ DECIDE ][ FINGERLY ]
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.