JSON Web Token VS LDAP
As of 30 October 2026, LDAP is named by 1,008 companies and JSON Web Token by 1,323; JSON Web Token skews to companies under 200 people (43% vs 36%), LDAP to companies over 1,000 (42% vs 32%).
As of 30 October 2026 · refreshed daily · counts move as websites, DNS and career sites are re-read.
The website-and-DNS footprint is not comparable between a marketing suite and a CRM: JSON Web Token's script and mail records show on hundreds of thousands of small sites, LDAP rarely leaves a trace outside its own apps. Compare on the job-posting numbers; use the footprint for reach.
- JSON Web Token: 2–200 employees
- 43%
- LDAP: 2–200 employees
- 36%
- JSON Web Token: 1,000+ employees
- 32%
- LDAP: 1,000+ employees
- 42%
- Postings per company, 90 days
- 2.4 · 3.2
- Website or DNS footprint
- 0 · 0
Who chooses which
Share of each tool's companies in every segment. "Leans" marks a gap of more than two points.
| Segment | JSON Web Token | share | LDAP | share | Leans |
|---|---|---|---|---|---|
| Self-employed | 19 | 1% | 7 | 1% | even |
| 2-10 employees | 89 | 7% | 55 | 5% | even |
| 11-50 employees | 214 | 16% | 136 | 13% | JSON Web Token |
| 51-200 employees | 265 | 20% | 167 | 17% | JSON Web Token |
| 201-500 employees | 179 | 14% | 125 | 12% | even |
| 501-1000 employees | 128 | 10% | 96 | 10% | even |
| 1001-5000 employees | 192 | 15% | 176 | 17% | LDAP |
| 5001-10000 employees | 67 | 5% | 75 | 7% | LDAP |
| 10,001+ employees | 170 | 13% | 171 | 17% | LDAP |
| Segment | JSON Web Token | share | LDAP | share | Leans |
|---|---|---|---|---|---|
| Technology & software | 755 | 57% | 533 | 53% | JSON Web Token |
| Business & finance services | 284 | 21% | 200 | 20% | even |
| Manufacturing & industry | 76 | 6% | 90 | 9% | LDAP |
| Media & content | 38 | 3% | 25 | 2% | even |
| Consumer services & leisure | 36 | 3% | 17 | 2% | even |
| Health care | 26 | 2% | 19 | 2% | even |
| Commerce & trade | 21 | 2% | 23 | 2% | even |
| Utilities & infrastructure | 21 | 2% | 35 | 3% | even |
| Transport, logistics & rental | 19 | 1% | 18 | 2% | even |
| Property & construction | 14 | 1% | 9 | 1% | even |
| Hospitality & travel | 12 | 1% | – | – | outside top 12 |
| Public, community & associations | 10 | 1% | 29 | 3% | LDAP |
| Automotive | – | – | 5 | 0% | outside top 12 |
| Segment | JSON Web Token | share | LDAP | share | Leans |
|---|---|---|---|---|---|
| United States | 787 | 59% | 650 | 64% | LDAP |
| India | 97 | 7% | 23 | 2% | JSON Web Token |
| United Kingdom | 72 | 5% | 53 | 5% | even |
| France | 43 | 3% | 44 | 4% | even |
| Germany | 39 | 3% | 51 | 5% | LDAP |
| Brazil | 30 | 2% | – | – | outside top 12 |
| Canada | 29 | 2% | 27 | 3% | even |
| Australia | 20 | 2% | – | – | outside top 12 |
| Singapore | 20 | 2% | 11 | 1% | even |
| United Arab Emirates | 15 | 1% | – | – | outside top 12 |
| Belgium | 13 | 1% | – | – | outside top 12 |
| Spain | 13 | 1% | 10 | 1% | even |
| Netherlands | – | – | 11 | 1% | outside top 12 |
| Switzerland | – | – | 10 | 1% | outside top 12 |
| Italy | – | – | 10 | 1% | outside top 12 |
| Poland | – | – | 10 | 1% | outside top 12 |
| Segment | JSON Web Token | share | LDAP | share | Leans |
|---|---|---|---|---|---|
| Software engineering | 3,113 | 73% | 937 | 20% | JSON Web Token |
| IT operations & business systems | 452 | 11% | 2,450 | 51% | LDAP |
| Data & AI | 160 | 4% | 60 | 1% | JSON Web Token |
| Engineering (non-software) | 82 | 2% | 127 | 3% | even |
| Product, program & project management | 30 | 1% | 53 | 1% | even |
| Customer service & success | 24 | 1% | 190 | 4% | LDAP |
| Sales | 20 | 0% | 110 | 2% | even |
| Education & training | 5 | 0% | – | – | outside top 12 |
| General management & consulting | 3 | 0% | 21 | 0% | even |
| Unclassified | 3 | 0% | – | – | outside top 12 |
| Construction and civil | 2 | 0% | 6 | 0% | even |
| Quality, safety & environment | 2 | 0% | 15 | 0% | even |
| Administration & office | – | – | 8 | 0% | outside top 12 |
| Arts media and entertainment | – | – | 6 | 0% | outside top 12 |
The companies behind each column
Companies using JSON Web Token →
Companies using LDAP →
Identity ranked →
Quote the sentence with the date and the link. The numbers change daily; the link always shows the current ones.
LDAP is named by 1,008 companies in job postings and JSON Web Token by 1,323; 0 name both. (Breaknorm, 30 October 2026, https://breaknorm.co/compare/json-web-token-vs-ldap)
Read from the source, not self-reported
Every number on this page can be traced to a page we crawled or a posting we read. Full methodology →
- Job postingsRead hourly from career sites. A tool counts when the employer's own text names it as the team's system; both tools can count for one company.
- Website and DNSScripts and embeds on the company's pages, plus SPF, DKIM, MX and CNAME records of its domain that point at the vendor.
- SegmentsCountry, size and industry from the company profile built from its website.
- Not a reviewNo ratings, prices or feature claims. For those, read the vendors.
JSON Web Token vs LDAP: questions
Which is more used, JSON Web Token or LDAP?
By companies naming it in their own job postings, JSON Web Token (1,323) over LDAP (1,008). By website-and-DNS footprint, LDAP (0 vs 0), because its scripts and mail records sit on many small company sites.
Who chooses JSON Web Token?
43% of JSON Web Token companies have 2 to 200 employees, against 36% for LDAP. 32% of JSON Web Token companies have over 1,000 employees, against 42% for LDAP.
Do companies run both?
0 companies name both in their postings, usually JSON Web Token in marketing and LDAP in sales, or during a migration.
Where do these numbers come from?
From the employer's own text in job postings read hourly from career sites, and from scripts found on company websites in our crawl. No vendor data, no surveys.
Get either list your way
The same data as a search, over MCP and the API, as bulk files, or pushed to you as it changes.
Every company on either tool,
with the person who owns it
Filter on JSON Web Token or LDAP. Start free, no card.