| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Crypto accounting | Accounting and close | 0% | 16 of 54 | 14% | 7 | under 10 labels · led by Bitwave at 27% |
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 0 | 0 | 0 | 0 | 0 |
| GPT-5.4 mini | 0 | 1 | 0 | 0 | 1 |
| Gemini 3.5 Flash | 0 | 0 | 0 | 0 | 0 |
| Perplexity Sonar | 0 | 0 | 0 | 1 | 1 |
| Grok 4.1 Fast | 0 | 1 | 0 | 0 | 1 |
| Mistral Small | 0 | 0 | 0 | 0 | 0 |
| DeepSeek V4 Flash | 0 | 1 | 0 | 0 | 1 |
| Llama 4 Maverick | 0 | 0 | 0 | 0 | 0 |
| Qwen 3.7 Flash | 0 | 0 | 0 | 0 | 0 |
| Kimi K2 | 0 | 1 | 0 | 0 | 1 |
| GLM 4.7 FlashX | 0 | 0 | 0 | 0 | 0 |
| MiniMax M2.5 | 0 | 0 | 0 | 0 | 0 |
| GPT-6 Luna | 0 | 0 | 0 | 0 | 0 |
| Muse Glimmer 30B | 0 | 1 | 1 | 0 | 2 |
Verbatim evidence the judge attached to positive labels.
“Lukka is best suited for enterprises and institutional crypto businesses needing high-integrity, audit-focused data management” Muse Glimmer 30B · Crypto accounting · comparative prompt · alternative
“If you need institutional-grade data infrastructure more than a user-facing tax app: Lukka.” GPT-5.4 mini · Crypto accounting · comparative prompt · alternative
“Consolidation across sources | Major | Custom ERP | Funds/corporates” Grok 4.1 Fast · Crypto accounting · scale prompt · alternative
“Lukka – Institutional focus, high-integrity data management” Kimi K2 · Crypto accounting · scale prompt · alternative
Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.
“Bitwave or Lukka may be better if your business is heavily BTC-focused ... more specialized than a budget-first choice” Perplexity Sonar · Crypto accounting · budget prompt · soft negative
Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 24 of the 24 answers that named Lukka and are not a share of its labels.
119 of the 119 domain citations in answers naming Lukka came from somebody else's page.
Pages are listed as the models cited them.
Search figures are US estimates from DataForSEO, read October 5, 2026; AI search demand is its modeled, directional estimate, not a count of queries to any assistant. The answers are this edition's. Two measurements side by side: neither is read as the cause of the other.
| Kind | Pages | Last 90 days | 2025-11 to 2026-10 | Latest | Categories named |
|---|---|---|---|---|---|
| Blog | 99 | 17 | 2026-10-01 | Crypto accounting | |
| Conference or event | 3 | 3 | 2026-08-14 | ||
| News or press | 3 | 0 | 2026-06-18 | ||
| Case study | 1 | 1 | 2026-07-08 | ||
| Report or ebook | 1 | 0 | 2026-06-16 |
Every page lukka.tech exposes, subdomains included. Kind is read from the address and title. The last 90 days, the latest date and the twelve months count pages by when they were published, from the site's feeds, a date in the address, or the page's own publication date, read from up to a hundred of its most recently changed pages; a page that says only when it last changed is counted in its kind but not in when, so the recent counts are a floor, and a kind none of whose pages gives a publication date reads undated. An event counts as online when its address or title says so (webinar, on demand, virtual or online summit); a conference, summit, trade show, expo or roadshow that does not say so is counted as a conference or event, which on a vendor's site is mostly in person. Read October 5, 2026.
An email the morning each edition publishes: where this product moved, where it held, and by how much against the noise floor. One address, confirmed by a click; a stop link in every email.
Already following? Everything you follow, with a stop for each.
What Lukka's own pages state, read October 5, 2026: lukka.tech, lukka.tech/pricing-market-data, lukka.tech/case-studies. A claimed page can correct any of them.
Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when Lukka's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as Lukka, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.
A new claim receives the current edition's vendor brief for Lukka by email, built from the raw record of the edition. It shows: