Device intelligence
Different accounts. Same operation. Surface coordinated device farms, emulators, and suspicious device reuse, and connect sessions that look unrelated at first glance.
Explore device intelligence The context behind every click Signals
Not every visitor is who they appear to be.
See the device, understand the intent, and catch bots, VPNs and device farms before they become your problem. Privacy by design.
No credit card required Pay only for identifications
One integration.
A clearer picture.
A clearer picture.
[ 01 / 10 ]See beyond the session
One session. The whole story.
Every identification answers two questions: which device is this, and what is it doing? One session, one visitor, one score, and every check behind it.
Session inspector
Nothing is read until you ask. Identify this browser to open its session.
NOT IDENTIFIED
Your session is still private.
There is no visitor ID, suspect score or signal report to show yet. Identify this browser to create one real response and open the inspector.
- Only on clickNothing is read before you ask.
- The real pathThe same SDK, matcher and score.
- Kept apartNo event archive and no bill.
- Your addressPlaced, and checked for VPN, proxy and Tor.
A signal is a clue, not a verdict. Your application stays in control of the decision. A few checks need history this demo keeps none of, and it marks those rather than answering them.
[ 02 / 10 ]More signal. Less guesswork.
Built to see what others overlook.
From an anonymous visit to a coordinated device farm. Bring the context that matters into one view.
Network intelligence
Look beyond the IP. Reveal VPNs, proxies, Tor exit nodes, and hosting networks. Context about the connection, not assumptions about the person.
Explore network signals Bot & automation
Spot the script. Identify automation, headless environments, and scripted activity. Separate suspicious bots from the people you want to welcome.
Understand bot signals Private browsing
Private. Not invisible. Surface supported private-browsing indicators alongside device and session context. Privacy mode alone is never a fraud verdict.
Explore private browsing Environment integrity
Question the disguise. Highlight inconsistent browser attributes, emulated environments, and signs of tampering. Know when a session does not add up.
Inspect environment signalsSignal availability and confidence depend on the browser, device, and integration.
[ 03 / 10 ]Simple on the outside. Intelligent underneath.
From a visit to a better decision.
Add intelligence at the moments that matter. Keep your product experience, and your decision-making, your own.
01 Connect
// At signup, login, or checkout
const session = await fingerly.identify();
const session = await fingerly.identify();
A small addition to your stack.
Collect a session event at a meaningful touchpoint. Forward its request ID to your server for trusted verification.
02 Understand
Turn clues into context.
Bring device, network, and automation signals together. Understand the indicators behind each result.
03 Decide
The next move is yours.
Let trusted sessions through. Step up verification when needed. Investigate suspicious activity with evidence.
[ 04 / 10 ]Protect the moments that matter
Less room for fraud. More room for growth.
Device intelligence is not a single-use feature. Put the same signals to work across your customer journey.
01 / ACCOUNT SECURITY
Welcome the customer.
Not the impersonator.
Recognize familiar devices and flag unusual sessions at login. Bring context to account-takeover reviews without treating every visitor as a threat.
Recognize returning device context Surface unusual access patterns Add verification only when needed
Explore the playbook CONNECTION INTELLIGENCEEXAMPLE GRAPH / 01
Signals connect the storySYNTHETIC DATA
Example workflows. Detection signals inform, not replace, your risk policies.
[ 05 / 10 ]Built for the people who build
Your stack. Your rules. Our intelligence.
A clear integration path from your frontend to your backend. Structured results you can understand, inspect, and put to work in your own application.
Familiar interfaces
Readable SDK and API patterns.
Server-side verificationKeep secret keys on your backend.
Structured responsesSignals with explicit context.
Your existing workflowSigned webhooks into your risk logic.
Web, mobile and serverOne integration path across every surface.
Free test environmentsDevelopment and staging keys cost nothing.
Explainable resultsEvery score lists the signals behind it.
Data residencyOne API, one database, in the EU.
SDK packages are not on public registries yet. Talk to the team for access.
Fit the way
you already build.
you already build.
Illustrative integration targets. Confirm supported SDKs before launch.
[ 06 / 10 ]Your signals. Your next move.
Good security is not one-size-fits-all.
Your signup flow is different from your checkout. Choose the signals that matter, set the conditions, and decide how your application should respond.
Inspect the sessionContext beats blanket blocking. A customer on a VPN is not the same as a bot running a device farm. Your policies should know the difference.
Session protection policySANDBOX
WHEN ANY enabled condition matches
Device farm detectedtrue
Tor exit node detectedtrue
Suspect score is at least30
Interactive policy sandbox. No real sessions are blocked or altered.
[ 07 / 10 ]Build trust into the implementation
Device intelligence belongs inside a responsible data strategy. Define what you collect, who can access it, and how long you keep it, before the first production request.
Purpose-led collection
Collect the context your use case actually needs.
Intentional retention
Set a retention policy that fits your obligations.
Protected access
Keep server secrets private and permissions scoped.
Clear visitor notices
Make your data practices understandable.
Implementation principles, not certification claims. Production controls and jurisdiction-specific requirements must be reviewed before launch.
[ 08 / 10 ]Pricing that follows your traffic
Pay for identifications. Not possibilities.
Prepaid and pay as you go. No plans, no seats, no monthly fee: add funds once, and each request spends from the balance.
Identification
$0.0025
per identification, falling with volume
A visitor ID, the suspect score and every signal, in one response. No detection is held back for a higher plan, and the price drops as the month grows.
Network lookup
$0.0005
per request we can’t identify
When a browser gives too little away to identify, you still get the network picture, at a sixth of the price.
Free
$0
always
Development and staging keys, retries of the same request, lookups that fail, and reading results from your server.
Signup credit
$1
free · 400 identifications
Every new account starts with it, and no card is needed to spend it. Add funds from $5 when you are ready.
Estimate a month
USD · EXCL. TAXUsually a small share. These are charged $0.0005 instead of $0.0025.
Estimated month
$246.00/ month
≈ $8.20 a day$0.00246 per request
| Identifications | 98,000 × $0.0025 | $245.00 |
|---|---|---|
| Network lookups | 2,000 × $0.0005 | $1.00 |
| Development, staging & retries | free | $0.00 |
| Month | $246.00 |
Start with $1 free
No card needed. 400 identifications before you add funds.
- First month, after the $1 credit
- $245.00
- Funded with
- One top-up of $250
Prices in USD, excluding taxes. Only production traffic is charged, at the price in effect when each request is made. The calculator is an estimate, not a quotation.
[ 09 / 10 ]A little more context
[ 10 / 10 ]The details matter
Good questions. Clear answers.
Getting to know your next intelligence layer? Start here.
See every question Talk through your use caseWhat counts as an identification?
An identification is a request to evaluate a browser or device session and return its identifier and available signals. It is a usage event, not a monthly active user or a dashboard seat. Repeated identification calls count separately. Define which moments need a check, such as signup, login, or checkout, rather than identifying on every page render.
Do I need a credit card to get started?
No. Every new account starts with $1 of credit, enough for 400 identifications, and no card is needed to spend it. Add funds from $5 when you are ready. Development and staging keys are never charged, so building and testing costs nothing.
Does a VPN or incognito session mean fraud?
No. Privacy tools have legitimate uses. Treat these signals as context alongside account behavior, device history, and transaction risk. A single signal should not automatically result in a blocked customer. In the demo, the VPN check says so: on its own, a tunnelled connection is context, not a verdict.
Can I try the detection on this page?
Yes. The session inspector opens empty, and its identify button runs a real identification of the browser you are reading this in: the same SDK, the same matching, the same score. Nothing is collected until you press it, nothing about the answer is stored on our side, and the visitor ID it shows is genuinely yours, which is why pressing it twice says returning visitor. Your address is placed and checked for a VPN, proxy or Tor the same way a customer’s visitor would be, in our own IP database, and the inspector shows the network and a map of where it was placed. The map tiles come from an open OpenStreetMap service. A few checks need to know what a device has done across many requests, and the demo keeps no such history, so it marks those as not answered rather than showing you a clear result nobody computed.
How do I connect this to my application?
Identify with the client SDK at a moment that matters, send the request ID to your backend, and read the stored result there with a secret key before you decide. The quickstart walks through it in six steps. SDK packages are not on public registries yet, so talk to the team for access.
How should we handle privacy and consent?
Set your collection scope, retention period, access policies, and visitor notices before going live. Requirements depend on your use case and jurisdiction. The privacy section describes design considerations, not a legal assessment or a certification. Have your privacy and legal teams review the production implementation.
What happens as our identification volume grows?
Only the total. An identification starts at $0.0025 and falls as the month grows: $0.002 past 250,000 and $0.0015 past a million, with each band pricing the requests inside it. There is no plan to move up to and nothing to negotiate, and the discount applies itself. Billing is prepaid: turn on auto top-up and the balance refills before it runs out. Requests that cannot be identified cost $0.0005, and retries of the same request are not charged twice.
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.