Lukka

• Name: Lukka
• URL: https://lukka.tech/
• Category: enterprise digital-asset data-infrastructure company / pricing-and-reference-data operator / blockchain-analytics and compliance workflow company
• Summary: Lukka belongs in companies/ because the useful analytical boundary is the named operator that packages enterprise data management, reference-data normalization, pricing and benchmark publication, and blockchain-analytics / AML workflow for institutions. The practical leverage is not a neutral Lukka protocol; it is Lukka’s company-run role in deciding how crypto assets, venues, entities, risk indicators, benchmarks, and middle- / back-office data products are assembled, delivered, and represented to banks, funds, accountants, regulators, and compliance teams.
• What it does:
  • Packages enterprise data-management software for crypto middle- and back-office, reporting, valuation, and operational-control workflows
  • Publishes reference-data products spanning classification standards, terms and conditions, crypto actions, venue scoring, marketplace and custodian data, mapping and standardization, and sustainability-oriented scoring
  • Operates pricing, market-data, benchmark, and quantitative-risk product lines intended for institutional accounting and market workflows
  • Provides blockchain analytics and compliance tooling for transaction tracing, wallet and entity monitoring, sanctions screening, risk assessments, and case-support workflows
  • Wraps those products in an explicit institutional-assurance shell built around SOC-style audits, ISO coverage, and customer access governed by Lukka’s own product and service agreements
• Key claims:
  • The homepage currently frames Lukka as The Global Leader in Enterprise Data Management for Digital Assets and says it provides Enterprise Data, Software and Blockchain Analytics that streamline the middle and back-office and power the future of global finance
  • The homepage and reference-data page jointly show Lukka selling not just analytics but a broad company-authored data layer covering reference data, pricing and market data, benchmarks, quantitative risk, and operational SaaS for institutions
  • The blockchain-analytics page says Lukka Blockchain Analytics is a web-based SaaS product supporting blockchain data analytics, AML risk monitoring, and risk assessments across 1.8 million+ crypto assets, 50,000+ monitored entities, and 100+ blockchain protocols
  • That same page says Lukka provides up to 380 risk indicators, up to 400 traced transaction hops, sanctions checks, and MiCA-licensed-entity / broker / Forex-trader flags, which makes Lukka’s classification and monitoring methodology part of the practical compliance control surface
  • The trust center says Lukka conducts annual SOC 1 Type II and SOC 2 Type II audits, highlights ISO/IEC 27001 coverage, and explicitly treats Lukka as a service-organization vendor whose controls matter to customer financial-reporting and security-assurance workflows
  • The Terms of Use define the Company as Lukka, Inc., together with its subsidiaries, affiliates, and other group companies and say only customers operating under separate agreements may access the products and services, which reinforces that the real boundary is a company-controlled service shell rather than an open protocol surface
• Whitepaper: No standalone Lukka protocol whitepaper is the important artifact here. The clearest company-level source of truth is the current homepage, reference-data and blockchain-analytics pages, trust center, and Terms of Use; see ../whitepapers/lukka-company-primary-sources-2026-08-09.md.
• Sources:
  • https://lukka.tech/
  • https://lukka.tech/lukka-reference-data/
  • https://lukka.tech/solutions/blockchain-analytics/
  • https://lukka.tech/trust-center/
  • https://lukka.tech/terms-of-use/

Internal linkages

• Project-layer alias: lukka.
• Adjacent company-layer comparisons for institutional crypto data and compliance truth surfaces: coin-metrics, kaiko, chainalysis, and scorechain.
• Reusable lens: when downstream institutions rely on one vendor’s normalized asset data, benchmark or pricing outputs, entity classifications, and monitored-risk workflow, the company boundary often matters more than any generic data infrastructure label.

Protocol / company boundary

• There is no especially useful standalone Lukka protocol boundary doing most of the analytical work here.
• The meaningful surface is the company-run workflow that decides what data is covered, how assets and venues are standardized, how benchmarks and valuations are packaged, how entity and risk classifications are authored, and which customers receive access to those outputs under Lukka-controlled terms.
• That is why this note belongs in companies/: the practical question is who authors and operates the data, pricing, benchmark, and compliance shell institutions may start treating as workflow truth.

Control surface

• Practical leverage sits in dataset construction, mapping and normalization choices, benchmark and pricing methodology, risk-indicator authorship, monitored-entity coverage, alert/report packaging, and the customer-access shell around Lukka’s SaaS products.

• The trust-center and service-agreement posture matter because institutions are not just consuming public blockchain data; they are inheriting Lukka’s service-organization controls, assurance claims, and delivery workflow as part of their own operational stack.

• Read Lukka as a company-run institutional data, valuation, benchmark, and compliance control plane rather than as a neutral protocol primitive or one isolated analytics product.

• Last reviewed: 2026-08-09 UTC