A public plan, written so customers and partners know exactly what they're buying into. We update this page when the plan moves.
Nordic Data is the data layer that joins every public Norwegian (and soon Nordic) registry on the organisation number. One REST API, one MCP server, one drop-in widget, one browser extension — same data underneath. We compete on real-time freshness, depth of registry joins, transparent pricing, and being the data product that AI agents call directly rather than the data product that humans book demos for. The buyers are technical: developers building KYB / onboarding UIs, KYB platforms missing Norway coverage, sales teams running outbound into the Nordics, AI agent builders.
No sales calls to get an API key. No annual contracts. Pricing on the website. Cancel anytime. If a customer can't onboard themselves, we have a product problem, not a sales problem.
Every vs-X page lists categories where the competitor wins. The benchmark page lists five segments where we explicitly recommend a different vendor. Lying about competitors gets ignored in Norway.
5,000 requests per month, no card, no expiry. The free tier funds itself: a fraction of users upgrade, the rest are free advertising every time they call the API.
All processing in Vultr Amsterdam. No US data transfer. No CDNs that resolve through US PoPs. Compliance posture is a product feature for our buyer.
Every REST endpoint has an MCP tool wrapper. Every new feature ships with its MCP tool annotation at the same time. We assume the consumer is a Claude/Cursor/Continue agent unless they tell us otherwise.
What's already in production, what's being built right now, and the next 12 months. We ship things before they're polished; the polish lands in the second pass.
Same architecture, four new countries. Each has its own primary registry (Bolagsverket / CVR / PRH), shareholder registry, and procurement source (TED for above-threshold; national portals for below). Most schema work is reusable; the per-country adapters are 1-2 weeks each.
The biggest gap our current AML offering has versus dedicated KYB platforms like Strise. Adds a media screening tool (`screen_adverse_media`) and a PEP database integration. Reuses our existing 4-layer enrichment infrastructure; the new layer is media indexing.
The browser extension is the bridge product. The real distribution is the platform-specific OAuth integrations in each Nordic accounting/ERP marketplace, with native install UX.
Larger markets, same playbook. EUID (European Unique Identifier) becomes the cross-border join key. We continue to index national-language news archives for the adverse media layer.
27 EU members + UK as the long-term aspiration. The technical model is the same as Norway; the per-country effort is the registry adapter, the language model for press archives, and the procurement adapter. The economic question is whether each country pays back the per-country engineering cost.
Customer pull determines priority. If you need Nordic Data to cover a specific country and have real volume, the conversation moves the roadmap.
Email support@nordicdata.cloud →