Skip to main content
New: mintBlue wins Dutch Ministry of Justice fraud verification projectRead the story

Decentralized Kafka. Built for Business.

Enterprise event streaming with cross-company superpowers. 50M+ events per day. Sub-100ms latency. 3,000+ pre-built connectors. Processing 6M invoices annually. Battle-tested at government scale.

Decentralized Kafka. Built for Business.

Trusted by enterprises and governments across Europe

Belastingdienst
Ministry of Justice and Security
National Office for Identity Data
VISMA
Yuki
Dockflow
NOWATCH
Sheltersuit
Intersolve
KvK
mintBlue turned our nightmare of invoice exchanges into a dream of automation. Now we strive to make taxation less of a headache for everyone involved.

Claire Arens

Innovation & Strategy, Netherlands Tax Administration

Netherlands Tax Administration
6 million invoices annually validated and processed automatically. No manual reconciliation. No disputes over what was agreed.

Sebastian Toet

Solutions Architect, VISMA | Yuki

VISMA | Yuki
Real-time, verifiable carbon tracking across our entire supply chain without exposing sensitive supplier data.

Pauline Van Ostaeyen

Cofounder, Dockflow

Dockflow

Event Streaming Stops at Company Boundaries

You have built event-driven architecture inside your company. Kafka streams connect your microservices. Events flow in real time. Then you need to share events with suppliers, customers, regulators. Suddenly: API polling. File transfers. Batch jobs. The real-time advantage ends at your firewall.

Event streaming that crosses organizational boundaries. No central authority.

Current Reality

  • Internal: real-time streaming. External: batch processing.
  • Each partner integration is custom point-to-point
  • No shared event log across company boundaries
  • Compliance events arrive days after they happen

Cross-Company Event Streams

  • Real-time pub-sub across organisations
  • 3,000+ pre-built ERP connectors
  • Cryptographic event ordering and verification
  • Guaranteed delivery with deduplication

Event Streaming with Cross-Company Capabilities

Think Kafka. Add cryptographic verification. Remove central operator.

01

Cross-Company Reach

Kafka-style pub-sub extended across organizational boundaries. Same event delivered to internal microservices and external partners simultaneously. No API polling. No batch transfers.

02

Cryptographic Event Ordering

Every event timestamped and ordered cryptographically. Disputes about what happened first are mathematically impossible. Court-admissible proof of event sequence.

03

Guaranteed Delivery

Three redundant delivery paths: P2P connections, overlay networks, full network listening. Built-in deduplication ensures same event processed exactly once.

04

Three-Layer Performance

Hot layer (Redis): microsecond latency. Warm layer (distributed): millisecond queries. Cold layer (blockchain): permanent archive. Events age automatically from hot to cold.

Cross-Company Invoice Processing

See It in Action

From invoice issued to payment scheduled across four organisations in sub-100ms.

Event Published
Read the full case study
  • 01

    Event Published

    Supplier accounting system issues invoice. Event published via pre-built connector (SAP, Oracle, Salesforce). No custom integration code. Event cryptographically signed.

  • 02

    Multi-Path Distribution

    Event distributed via three redundant methods: direct P2P to subscribers, overlay network broadcast, full network listening. Subscriber receives via fastest path.

  • 03

    Cryptographic Ordering

    Event recorded in distributed ledger with cryptographic timestamp and sequence proof. Immutable ordering establishes what happened first across all parties.

  • 04

    Processing and Automation

    Event deduplicated and processed exactly once. State machine validates format, verifies vendor, calculates tax. Payment scheduled. All parties updated. New events generated.

  • From invoice issued to payment scheduled: sub-100ms

    60%

    Working capital improvement

    Zero

    Manual reconciliation

    Real-time

    Compliance reporting

    <100ms

    End-to-end processing

Batch Processing vs Kafka vs mintBlue Event Streams

CapabilityBatch ProcessingKafka (Internal)mintBlue Event Streams
Latency12-24 hoursMilliseconds (internal)<100ms (internal + external)
Cross-company eventsFile transfers, FTPAPI polling requiredReal-time pub-sub across companies
ThroughputLimited by batch windowHigh (single company)50M+ events/day (multi-party)
Event ordering proofNo ordering guaranteeWithin partition onlyCryptographic ordering across parties
Audit trailLogs can be alteredRetention limits applyImmutable complete history
ERP integrationCustom scripts per ERPCustom connectors needed3,000+ pre-built connectors

Frequently Asked Questions

Architecture

Integration

mintBlue platform illustration

Cross-company streaming

Ready for Cross-Company Event Streaming?

From architecture assessment to production deployment. Our engineers help you extend event-driven architecture beyond company boundaries.