# Dejta Broker · Dejta+

Dejta Broker streams enriched player, payment and game events in real time to partners, CRM and your own applications. Built on Kafka.

Source: https://www.dejta.ai/broker/

Dejta BrokerIn build

# Every event, streamed where it’s needed.

An event stream for your data. Dejta Broker sends enriched events in real time to your partners, your tools and your own applications, and takes in events from third parties for use across Dejta+.

[Book a demo](/contact/)
[Pricing](/pricing/)

Example event · Kafka topic

{
  "event": "deposit.completed",
  "at": "2026-11-12T14:02:07Z",
  "brand": "brand-01",
  "player": "p-48213",
  "amount": 50.00,
  "currency": "EUR",
  "first\_deposit": true
}

Consumed by affiliates · CRM · your apps · Illustration

**What it is**

A governed, real-time event stream built on Kafka, scoped to your brands.

**How you access it**

Kafka topics (named event streams that systems subscribe to), for your systems and approved partners to consume, and for third parties to produce to.

**Why you can trust it**

Events come from the same reconciled platform behind Reporting and Studio, with consistent names.

**Built for**

Integration and engineering teams, and the partners they work with.

## Every event, in and out, as it happens

Broker sits between the platform and everything around it. Events stream in seconds, to every system that needs them.

**Events in**

-   **Your platform**Player, payment and game events from your sources, as they happen.

-   **Approved third parties**Partners produce their events to Broker, so their data lands in Dejta+ alongside yours.


**Dejta Broker**Kafka topics

1.  14:02:05`player.registered`
2.  14:02:07`deposit.completed`
3.  14:02:09`bet.settled`
4.  14:02:11`withdrawal.requested`

**Events out**

-   **Affiliates**Registrations and first deposits as they happen, not in a nightly file.

-   **CRM**Journeys start from what players just did.

-   **Regulatory applications**The events real-time compliance applications consume.

-   **Your own applications**Real-time features on the same stream, with no extra feeds.


Illustration · event names are examples

## Events your teams can rely on

-   ### Enriched with context

    Player, brand and payment context added, so consumers don’t have to look it up.

-   ### Consistent names

    The same event names across brands and sources, so integrations don’t break.

-   ### Scoped to your brands

    Brand isolation, access control and audit, like the rest of the platform.


## Common questions about Broker

What technology does Broker use?

Apache Kafka. Your systems and partners consume events from Kafka topics with standard Kafka clients.

Can third parties send data in?

Yes. Approved third parties can produce events to Broker, so their data can be used across Dejta+.

Which events are available?

We agree the events and fields you need during onboarding.

Is Broker in every package?

Broker is an optional add-on on Pro and Enterprise.

## Tell us where your data needs to go.

Book a demo and we’ll walk through the events and integrations you need.

[Book a demo](/contact/)
[See how pricing works](/pricing/)
