What is Fingerly?

Fingerly is a device intelligence platform that identifies the device behind each web or mobile session and scores how suspicious it looks, so applications can stop fraud and abuse without adding friction for real people. It works at the moments that matter, such as signing up, logging in or paying, and it hands the decision to your code rather than blocking anyone itself.

#What does Fingerly do?

Every identification returns a stable visitor ID, a confidence value from 0 to 100, whether the visitor is new to your organization, a suspect score with a level of low, medium or high, the signals behind the score, and network context such as country and whether the connection comes through Tor, a VPN or a proxy. In browsers, the same device gets the same visitor ID on its next visit, even after cookies and storage are cleared.

The score is a sum of weights you can read, explain and change. Weights and thresholds are yours to tune, per organization or per key. Fingerly gives you evidence, and your own policy decides what happens.

#Who is Fingerly for?

Fingerly is for product, engineering and risk teams that run an application where a repeat or hostile device costs money or trust. Typical uses are protecting sign-ups and logins, limiting promotion and referral abuse to one reward per device, adding context to checkout, and keeping communities and games fair. It is not an advertising or cross-site tracking tool: a visitor ID is scoped to one customer and cannot follow a person across companies.

One identification takes a few hundred milliseconds end to end, and nothing is ever asked of the visitor. The SDK only collects and sends. Every decision is made on the server, so a rule can change without an app release, and which signals fired is told only to your backend and the dashboard, never to a browser or an app.

#What can Fingerly detect?

Fingerly scores signal groups that cover the network, the client and, on mobile, the app itself. Examples include Tor, VPN and proxy connections, automation and bots, virtual machines, tampered browsers, private browsing, devices that look mass-provisioned, rooted or jailbroken phones, emulators and simulators, cloned apps, and intercepted app traffic. A short list of groups is catalogued but not active yet, so the documentation marks which are live.

A signal is context, not a verdict. A VPN user may simply value privacy, and no single signal should block a customer on its own.

#How do you integrate Fingerly?

An integration has four parts:

• Web: the JavaScript browser SDK, with bindings for React, Next.js, Vue, Nuxt, Svelte and Angular, identifies the visitor with a public key and returns a request ID.
• iOS and Android: native SDKs written in Swift and Kotlin, plus React Native, Flutter and Lynx packages, do the same inside an app.
• Server verification: your frontend sends the request ID to your backend, which reads the stored result with a secret key and decides. Server SDKs exist for Node.js, Python, Go, Java, .NET, PHP, Ruby and Rust, and any other language can call the HTTP API.
• Webhooks: results are pushed to your systems as they happen, including identification completed and visitor suspect events.

Development and staging keys run the same detection as production and cost nothing, so you can build the whole flow before you pay for anything.

The dashboard shows every identification as an event with its visitor, score and signals, so an analyst can investigate why a session was scored the way it was. Teams can tune risk weights, set the threshold that decides what counts as high, and have results pushed to their own systems through webhooks.

#How much does Fingerly cost?

Fingerly is pay as you go from a prepaid balance, with no plans and no monthly fee. An identification costs $0.0025, falling to $0.0020 after 250,000 identifications in a calendar month and $0.0015 after 1,000,000, with each band pricing only the identifications inside it. Requests Fingerly cannot identify are free, and so are development and staging keys, retries of the same request and reading results from your server.

Every new account starts with $1 of credit, enough for 400 identifications, and no card is needed to spend it. You add funds from $5 when you are ready.

#How does Fingerly handle privacy, and where are the docs?

Fingerly sets no cookies, never collects page content or anything a visitor types, shows no permission prompt, and does not sell or share visitor data. Every SDK defaults to collecting nothing until you set consent to granted, and visitors can be erased. You remain the controller and Fingerly your processor, and the right lawful basis for your use is a question for your own legal advice.

The documentation lives at https://docs.fingerly.io, with a quick start that takes you from an empty account to a verified identification, SDK guides for every platform, the API reference and the webhook reference. For questions that the documentation does not answer, support@fingerly.io reaches the team. The session demo at fingerly.io runs a real identification of your own browser, so you can see a result before you sign up.

Prices are per identification and fall with monthly volume. See the pricing page for the full schedule.