Revenue rank on Toolify.
← AI Revenue Radar · Toolify Top 300
Onfido
AI-powered digital identity solution for trust, onboarding, and compliance.
Read the market signal first
Traffic and channel data use SimilarWeb methodology; keyword metrics come from DataForSEO; ranking and revenue signals come from Toolify. Evidence snapshot 2026-07-06.Estimated monthly traffic (directional, not audited revenue).
Primary market category.
Non-brand search share indicates how much task-led discovery may exist.
Channel mix share of visits
Top countries traffic share
Competitor traffic three-month visits
No structured competitor comparison is available.
Task-keyword opportunity table
Score is Shipsite's opportunity score, blending the metrics on the left. Auditable inputs are Volume, KD, CPC, allintitle and KGR.| Keyword | Volume | KD | CPC | KGR | Score |
|---|---|---|---|---|---|
| identity verification api | 320 | 34 | $39.6 | — | 44.6 |
| onfido vs jumio | 10 | 47 | — | — | 9.5 |
| kyc provider comparison | — | — | — | — | 0 |
| idv pricing per check | — | — | — | — | 0 |
| age verification requirements | 40 | 29 | $2.63 | — | 24.6 |
KGR is shown once allintitle sampling lands for a keyword; Volume, KD and CPC are already auditable.
Business canvases and strategic analysis
Thirteen grounded views aligned with the site-building strategy desk: Business Model Canvas, Value Proposition Canvas, JTBD, ICP, Empathy Map, Customer Journey, SWOT, PESTAL, Porter's Five Forces, 3C, STP, 4P and AIDMA — opened by the insight brief.One-line positioning
Onfido is an identity verification API—document scan, liveness check, fraud signals—billed per verification.
Target user
End users are the consumers being verified; the buyer is compliance/engineering teams at finance, rental, and sharing-economy firms.
Category role
Positioned as a vertical KYC/IDV API vendor, now operating as compliance infrastructure under Entrust.
The verdictOnfido is driven by regulatory necessity and sales relationships with almost no SEO acquisition — growth is capped by sales capacity, not virality.
Non-obvious insights
- 77.5% direct traffic plus Canada leading geography suggests traffic reflects specific customer deployments, not broad demand.
- 'identity verification api' pulls 320 searches at low competition, yet organic search is only 6.1% — an SEO gap rivals could exploit.
- 1.0M visits yet only rank #154, combined with quote-based pricing, suggests the sales-led model caps traffic-to-revenue conversion.
Mechanisms worth studying
- Proves a compliance-mandated B2B category can survive on direct/referral channels — demand is regulation-pulled, not searched.
- Opaque quote pricing suits enterprise sales but leaves 'vs/comparison' keywords as a content gap for rivals to exploit.
01 · Business Model Canvas
Business Model Canvas
- Uses Paddle to process payments, a key technology supplier.
- Channel or ecosystem partners (e.g., system integrators) are not detailed in evidence.
- Entrust, as acquirer and strategic parent, provides capital and business-integration support.
- Using Paddle means relying on its merchant-of-record model for global tax, not in-house billing.
- Ongoing maintenance of document recognition and liveness algorithms to counter evolving fraud.
- No evidence describing specific operations/QA processes such as accuracy SLAs.
- Sales and compliance-content operations (vendor selection, compliance explainers) targeting regulated industries.
- 77.5% direct traffic plus an 'onfido vs jumio' query points to sales outreach, not content marketing.
- High France/UK traffic share requires ongoing GDPR biometric-data compliance review.
- Provides a bundled API combining document recognition, liveness detection, and anti-fraud signals.
- Pay-per-verification instead of flat subscription aligns cost with usage; exact price requires a sales quote.
- No evidence of emotional/social value; identity checks are a compliance obligation, not a voluntary experience.
- The Entrust acquisition signals stability, but post-acquisition support levels are unknown.
- No evidence of an open ecosystem or developer community; only API integration capability is mentioned.
- An enterprise API partnership with high post-integration switching costs, not a one-time transaction.
- No evidence detailing the specific customer success or support model.
- Retention mechanics unknown; no renewal-rate or churn data available.
- Trust rests on compliance credentials and the Entrust acquisition; specific certifications are not in evidence.
- End users must complete a one-off identity check (e.g., onboarding, age verification) with no say in vendor choice.
- The buyer is the compliance/risk team at a regulated enterprise; the admin is the engineering team integrating the API.
- Purchase is triggered by a compliance obligation (onboarding, market entry, regulatory review), not routine shopping.
- Pain is regulatory risk and fraud loss; gain is lower compliance cost and faster user onboarding.
- Tiered per-verification pricing (~$1-3/check, undisclosed) scales with enterprise volume.
- Document recognition, liveness detection, and anti-fraud signal tech stack form the core API capability.
- Entrust acquisition provides brand endorsement, plus roughly 1M monthly visits already in place.
- Team size and financial capacity are unknown; post-acquisition resource investment level is unclear.
- 1.0M visits/mo, rank #154 on Toolify — mid-tier compliance brand, not a category leader.
- Canada 21%, France 11%, UK 10% traffic requires document-template coverage and human review across formats.
- Direct traffic (77.5%) plus referrals (12%) show sales/partner-led acquisition, not SEO.
- 77.5% of traffic is direct vs 6.1% search, implying purchases stem more from brand/sales than organic discovery.
- Pricing is undisclosed; the purchase path is inferred to be sales-led rather than self-serve.
- Service is delivered via API integration; specific delivery forms like SDKs are not detailed.
- Uses Paddle as payment infrastructure, implying a simplified billing flow; support channels are unknown.
- Ongoing R&D investment in document recognition and liveness detection algorithms.
- Variable costs scale with verification volume (data sources/compute), growing linearly with usage.
- No evidence detailing the specific customer support/operations cost structure.
- 77.5% direct traffic implies sales/brand-driven acquisition rather than paid marketing; exact acquisition cost unknown.
- Paddle's cut plus $1-3/check pricing could squeeze margin as volume scales.
- Charges per verification, tiered pricing roughly $1-3/check (undisclosed, subject to sales quote).
- No evidence of an upgrade/expansion path such as enterprise SLAs or dedicated account management.
- No evidence of licensing/subscription or other alternative revenue streams; only usage-based billing is confirmed.
- Post-Entrust acquisition, incremental revenue more plausibly comes from cross-selling its security suite than standalone price hikes.
02 · Value Proposition Canvas
Value Proposition Canvas
Product side · Value Map
- A document-recognition API endpoint parsing official ID formats by country.
- A liveness/biometric-check endpoint bundled with fraud-signal scoring.
- Automating document + liveness checks removes the manual-review bottleneck, relieving slow onboarding.
- Fraud-signal scoring flags forged documents before account creation, relieving fraud-loss pain.
- The per-call API returns pass/fail within the signup flow near-real-time.
- Structured verification logs themselves become the audit-trail record.
Customer side · Customer Profile
- Complete identity verification before a regulated transaction (account opening, rental, rideshare).
- The compliance officer wants to reduce personal and organizational audit risk.
- Manual verification is slow and drags down signup conversion.
- Fraudulent signups cause direct financial and reputational loss.
- Legitimate users complete onboarding faster.
- Retains a documented compliance trail for regulators and auditors.
03 · JTBD
Jobs To Be Done
- When End consumers undergoing identity verification stall on Complete identity verification before a regulated, they search 'identity verification api' or open onfido.com.
- Direct is 77.54% of observed visits, so 'identity verification api' is a repeatable Complete identity verification before a regulated situation rather than a one-off search.
- Measured demand for 'identity verification api' shows Onfido is needed because the current stack cannot finish Complete identity verification before a regulated in one pass.
- A procurement window and seat budget force Compliance/risk teams at finance, rental, and sharing-economy enterprises to choose Onfido for 'identity verification api' or an alternative now.
- The functional job is delivering usable Complete identity verification before a regulated in-session, not learning another full suite.
- Before paying, buyers still line up 'age verification requirements' quality, limits, and the observed Paddle checkout on one comparison sheet.
- End consumers undergoing identity verification want less panic after a failed Complete identity verification before a regulated pass, especially when 'identity verification api' misses the expected result.
- Budget owners want proof the Paddle bill for 'identity verification api' will not jump next cycle.
- End consumers undergoing identity verification want to look able to finish Complete identity verification before a regulated in front of peers, not still googling 'identity verification api'.
- Proving to management that picking Onfido for 'identity verification api' was not a random tool buy is the social job.
- Success is a pasteable, shareable, or editable Complete identity verification before a regulated result inside the same session.
- It also means holding 'age verification requirements' time, quality, and the observed Paddle checkout inside a range Compliance/risk teams at finance, rental, and sharing-economy enterprises can explain.
04 · ICP
Ideal Customer Profile
- The core profile is End consumers undergoing identity verification doing Complete identity verification before a regulated, in the Identity Verification / KYC API category.
- Compliance/risk teams at finance, rental, and sharing-economy enterprises pay for 'identity verification api', and administration may sit with Engineering teams integrating the verification API.
- The buying trigger often shows up as a search for 'identity verification api', already present in the audited keyword table.
- Canada is 21.45% of visits, so local work seasons can turn 'identity verification api' from latent need into a same-week must-solve.
- The primary pain is that Complete identity verification before a regulated is slow and error-prone, which is why 'age verification requirements' exists as a task query.
- Quota exhaustion and whether paying is worth it make Compliance/risk teams at finance, rental, and sharing-economy enterprises hesitate after the first 'identity verification api' result.
- Budget signal for 'identity verification api': the observed Paddle checkout; observed rail is Paddle.
- Self-serve subscription is the main path for 'identity verification api'; 1.0M traffic shows people already pay or keep trying.
- Decision criteria include 'identity verification api' sample quality, limits, and whether Paddle checkout is frictionless.
- The shortlist comes mainly from same-job 'identity verification api' search results, and trust hinges on whether official pricing is self-serve readable.
- The repeatable reach path for 'identity verification api' buyers is Direct (77.54%), not a one-off campaign.
- The task query 'identity verification api' plus onfido.com is the second touch, better for content pages than brand ads alone.
- Casual free-only users with no seat budget and no 'identity verification api' job are outside Onfido's primary ICP.
- Traffic-adjacent domains that are not the same 'identity verification api' job cannot be auto-included or excluded from the ICP.
05 · Empathy Map
Customer Empathy Map
Primary personaA compliance engineering lead at a fintech or sharing-economy startup selecting a KYC vendor.
- They keep seeing 'identity verification api' result pages, onfido.com, and same-job generation UIs.
- The old workflow, docs, and peer screens stay in view as 'identity verification api' substitutes.
- Peers talk in queries like 'identity verification api' and 'age verification requirements', not official handbook language.
- Users in Canada also hear whether 'identity verification api' is worth the Paddle quota, not brand slogans.
- 'identity verification api' — searching for integration capability and API fit.
- 'onfido vs jumio, which has a higher approval rate?' — directly comparing rivals.
- Runs parallel sandbox trials comparing Onfido's and Jumio's pass rates and response times.
- Contacts sales for a custom quote since tiered pricing isn't published.
- Picking the wrong vendor could leave the company non-compliant at audit, with liability falling on them.
- Worried opaque tiered pricing will produce surprise bills once volume scales.
- Blocked page loads and opaque pricing make evaluation feel effortful.
- Feels relief once integration is live, since verification liability shifts to a specialist.
- They fear having to redo a failed Complete identity verification before a regulated pass; searching 'identity verification api' is already a frustration signal.
- A sudden end to the free quota on 'identity verification api' makes lock-in to Onfido feel hard to admit.
- The ideal gain is finishing Complete identity verification before a regulated in-session and handing over an output that satisfies 'age verification requirements'.
- If Direct can find Onfido again for 'identity verification api' (77.54%), a successful reuse becomes habit instead of another bake-off.
06 · Journey Map
Customer Journey Map
Discover01
Evaluate02
Onboard03
Retain04
Advocate05
Emotion curve (inferred)
Key behavior
Most users discover Onfido via direct URL entry or peer referral rather than search engines.
Evaluates against comparison queries like 'onfido vs jumio' and requests sandbox access plus a quote.
Integrates the document + liveness API into signup, configuring per-country document rules.
Continuously monitors verification volume, unit cost, and fraud-catch rate against SLA.
Cites Onfido as an approved vendor in audit documentation and informally refers peers.
Friction / drop-off
With organic search at only 6.1%, teams unfamiliar with compliance tech are unlikely to find it via search.
Opaque pricing plus a blocked homepage slows self-serve evaluation and extends the sales cycle.
Coverage spanning Canadian, French, and UK formats adds integration configuration complexity.
Usage-based billing with undisclosed tiers makes cost forecasting hard as volume grows.
Referral traffic at only 12% suggests word-of-mouth remains a secondary growth engine.
Product lever
Relies on sales outreach and relationship-building to reach prospects, not inbound content.
The API form lets engineering teams trial the interface before negotiating commercial terms.
Per-verification pricing rather than a flat subscription lowers the threshold to start integrating.
Once compliance docs bind to a vendor, switching requires recertifying the flow, locking in retention.
Referrals are the second-largest channel (12%), indicating a functioning partner mechanism.
07 · SWOT
SWOT Matrix
- Bundles document, liveness, and fraud signals into one API call, reducing integration surface vs point solutions.
- Post-Entrust acquisition, it inherits a larger security company's balance sheet and sales network.
- Referrals are the second-largest channel at 12%, evidence of a working partner-sales motion.
- Pricing is completely opaque with undisclosed tiers, potentially lengthening the sales cycle.
- The official page screenshot could not be captured (browser challenge/loading block), suggesting presentation friction.
- Direct traffic is 77.5% while organic search is only 6.1%, indicating weak content/SEO acquisition capability.
- The "identity verification api" keyword has 320 monthly searches with LOW competition, leaving room for content acquisition.
- Age-verification keywords show real search demand; tightening regulation could expand this niche.
- The existence of "onfido vs jumio" queries shows buyers do vendor comparisons before purchase.
- The Entrust acquisition could weaken brand independence or trigger product-line consolidation.
- Missing search-volume data for "kyc provider comparison" suggests the independent review content ecosystem is immature.
- The comparison keyword has moderate difficulty (KD47), showing other KYC vendors contest the same decision window.
08 · PESTAL
PESTAL Macro Environment
- EU/UK GDPR's special-category biometric rules directly constrain how liveness-check data is processed.
- Mandatory KYC legislation in finance and gig economy is the demand root; regulatory easing would shrink the market.
- Usage-based billing ties revenue to customer growth, not independent pricing power.
- Undisclosed pricing enables negotiation but leaves no public price anchor against rivals like Jumio.
- Rising consumer wariness about biometric data can raise abandonment during verification steps.
- The 'age verification requirements' query signals age checks expanding into social/content platforms.
- Liveness/OCR tech is commoditizing, narrowing the moat to cross-country document coverage breadth.
- The homepage resists scraping via a browser challenge, ironically mirroring its own anti-fraud logic.
- Onfido still needs a cloud model to finish 'identity verification api'; 1.0M monthly visits write energy into unit cost.
- When Canada users return to onfido.com for 'identity verification api', repeat transfer of assets and generated results is a compressible environmental load.
- Operating 'identity verification api' for Canada (21.45%) puts local privacy, content, and consumer rules under Onfido.
- Collecting via Paddle for 'identity verification api' means tax, refund, and sanctions lists can limit where Onfido may sell.
09 · Five Forces
Porter's Five Forces
Open cloud OCR/face APIs lower the technical barrier, but multi-country document libraries remain a moat.
Payment depends on Paddle rather than an in-house stack, limiting leverage if fees or policy change.
Queries like 'kyc provider comparison' show enterprise buyers routinely comparison-shop with strong leverage.
Larger enterprises may build a lightweight verification pipeline on cloud APIs instead of buying the full package.
Though low-volume, the explicit 'onfido vs jumio' query shows the market treats the two as a standard pair.
10 · 3C
3C Analysis
- In-house document-recognition and liveness models covering multiple national ID formats form a moat.
- Usage-based revenue is tightly coupled to customer volume, scaling with growth but carrying concentration risk.
- As an Entrust subsidiary, pricing and roadmap decisions are no longer fully independent.
- End users must complete a one-off identity check (e.g., onboarding, age verification) with no say in vendor choice.
- Pain is regulatory risk and fraud loss; gain is lower compliance cost and faster user onboarding.
- Tiered per-verification pricing (~$1-3/check, undisclosed) scales with enterprise volume.
- Jumio — a comparable document + liveness KYC API vendor directly competing for the same purchase decision.
- No specific evidence names a substitute (e.g., outsourced manual review or in-house KYC build) in the same budget.
- No traffic-adjacent competitor data (e.g., similar-sites list) is available, so the true competitive boundary is unconfirmed.
11 · STP
STP Marketing Strategy
- Segment first by job: End consumers undergoing identity verification doing Complete identity verification before a regulated, versus evaluators who only search 'identity verification api' to compare.
- Then cut by who pays for 'identity verification api' and geography: Compliance/risk teams at finance, rental, and sharing-economy enterprises versus free riders, and Canada (21.45%) versus the rest.
- Target the layer that can be reached again via Direct and will pay for 'identity verification api', not every visitor.
- Win the single-player 'identity verification api' job first, then consider team features; see ICP exclusions.
- Positioned as a vertical KYC/IDV API vendor, now operating as compliance infrastructure under Entrust.; in the customer's mind it should mean 'identity verification api', not generic AI.
- The reason to believe 'identity verification api' is revenue rank #137 and about 1.0M monthly visits, framed against manual work or other Identity Verification / KYC API tools.
12 · 4P
4P Marketing Mix
- The product is an API-first verification bundle (document + liveness + fraud), not a consumer app.
- Coverage spans Canadian, French, and UK document systems, three distinct national ID formats.
- Tiered per-verification pricing ($1-3) is undisclosed and requires a sales quote, an enterprise-negotiated model.
- No published free tier or self-serve signup is evidenced, consistent with the direct-traffic-dominant channel mix.
- Primary distribution runs through the direct sales-relationship channel (77.5%), not an app-store listing.
- Secondary distribution comes via referral partnerships (12%), likely platform integrators embedding Onfido.
- The "identity verification api" keyword has a CPC as high as $39.6, showing strong commercial value in this category.
- Given long compliance decision cycles, promotion should emphasize vendor-selection guides over short-term performance ads.
13 · AIDMA
AIDMA Decision Journey
- Attention arrives through Direct (77.54%) and high-relevance entries like 'identity verification api', not broad brand noise.
- Referrals at 11.97% is the second attention surface for 'identity verification api'; onfido.com must make that job obvious to End consumers undergoing identity verification.
- Interest comes from translating 'identity verification api' into a readable Complete identity verification before a regulated demo, not a feature dump.
- 'age verification requirements' shows they also want limits, price, or usage detail — the next page has to answer those.
- Desire holds when Onfido finishes 'identity verification api' clearly faster than doing it by hand in one try.
- Published pricing lowers the cost of wanting 'identity verification api', otherwise desire dies in the bookmark bar.
- Heavy direct traffic means the brand can be recalled together with 'identity verification api', or they will search again next time.
- Revenue rank #137 and 1.0M visits become a memory hook only if people also recall 'identity verification api', not just the brand.
- Action is the first result on onfido.com plus Paddle checkout; an extra signup step drops 'identity verification api' traffic.
- Keep price, limits, and the buy button for 'identity verification api' on one screen to turn interest into payment.
Evidence boundariesExact tiered pricing rules and per-verification price are undisclosed, blocking precise revenue modeling.; Renewal rate, retention, and churn data are entirely absent, making customer stickiness impossible to assess.; Brand independence, roadmap integration, and team-size changes post-acquisition are unknown.; Lacking similar-sites traffic data, the true competitive boundary beyond Jumio cannot be confirmed.
Evidence boundaries
Official website: https://onfido.com
Ranking and revenue signals come from Toolify; traffic, channels and country distribution use SimilarWeb methodology; keyword Volume, KD and CPC come from DataForSEO. This is a research snapshot, not investment advice.
More in Other AI Product
Found your wedge? Ship the site.
Shipsite turns a validated keyword opening like this into a live, SEO-ready site — in days, not months.