fidra — every scroll is a round. A playable feed layer for licensed casino operators.
fidra adds a vertical entertainment feed to your app: real clips of big rounds, live streams, playable moments, and your slot catalogue surfaced like content. Players scroll, watch, laugh, learn and join with one tap. Inside your product, on your licence, through your wallet — pointed, first, at the players who pay you nothing today.
Three classes of content, and a composition engine that reads behaviour: slots stay first, what a player watches shapes what they are offered next — and a losing streak slows the feed down, not up.
Your catalogue, surfaced like content
Live tables enter the feed as cards, not as a lobby tile.
A tap opens the full, certified game, unchanged.
Slots lead: premiere cards for new releases, big-win clips, a taste of the reels in the feed itself. Composition quotas are enforced by the engine, crash-family capped, and every pick is logged.
Games born for the feed
Play together. Could not exist in a lobby grid.
Ours. The reason a copied feed stays a copied feed.
Original mechanics where the gesture is the game. They could not exist in a lobby grid, they are ours, and they are the reason a copied feed stays a copied feed.
The content between the games
RTP, the honest way.
Retention without wagering. What makes it a feed people watch.
Creator-style clips shipped as real video files, live streams, trust cards that explain RTP the honest way, daily rituals, and a written humour layer.
Zero content-ops on your side. The feed's raw material is machine-readable: rounds are data, and data renders into content.
The machine
Every round across your player base is a potential clip. Detection rules find the moments, big wins, near-misses, comebacks, and render them in the feed's video grammar automatically. No editors, no uploads.
Your people
Your streamers' footage drops in as video files, and their live streams embed directly: a config entry, not an integration. The ambassadors you already pay finally have a surface inside the product.
The crowd, plus a small pack
Prediction and quiz cards write themselves from live rounds and crowd answers. On top sits a small authored layer, humour, myth-busting, honest RTP explainers, that we ship and refresh as part of the service.
The network
Deployments can share anonymised, brand-stripped clips and ghosts with each other — opt-in, with money and identity stripped by construction. A new operator's feed is not empty on day one.
Colour, type and corner radius come from a per-operator config. The format stays the same; the skin is yours.
The same feed, four operator configs. No code changes, config only.
We do not want your active player — we want the one paying you nothing today. You cannot redistribute zero. Growth here is incremental by construction, and the pilot runs on these segments alone.
Proof, not a dashboard.
Vendor dashboards always look good. Our measurement is built to show a zero as plainly as a lift — so if the feed is not working on your players, you are the first to know.
Randomised holdout
Eligible players are split before the feed is shown, and the assignment is immutable for the experiment window.
Total revenue, not feed revenue
The headline number is 30-day NGR per eligible player across every surface, with the cannibalisation view shown plainly.
Novelty, tracked weekly
A weekly effect curve rather than a cumulative one, so a fading lift is visible instead of hidden.
An auditable decision log
Every card the feed chose and why: hash-chained, exportable, readable by your compliance team.
Three steps, and the first two are free.
Feasibility check — free, no call
Send eight weeks of anonymised per-user revenue: one column of numbers, no identities. We tell you whether a pilot at your size can statistically detect an effect at all — and if it can't, we tell you that too.
90-day pilot — €0
One zero-revenue segment, a randomised holdout, integration in one evening, weekly written reports. The success metrics and the rollout price are signed before launch.
Rollout — on terms you already agreed
A setup fee, a monthly minimum and a small share of feed-attributed GGR. The minimum credits against the share — you pay whichever is greater, never both.
No platform migration, no catalogue rebuild, no change to your certified games.
Drop in the iframe
The feed appears as a tab or a screen inside your app, themed to your brand from config.
Connect your wallet and launch API
Bets are placed and settled in your systems. We never hold a balance. A sandbox wallet is provided so your team can test before anything touches production.
Listen to the event stream
Watch, play, session and outcome events arrive in your analytics on a documented, versioned schema.
<!-- 1 · the feed --> <iframe src="{FIDRA_EMBED_URL}?operator={YOUR_ID}" allow="autoplay"></iframe> // 2 · the listener window.addEventListener('message', (event) => { if (event.origin !== FIDRA_ORIGIN) return; const { type, payload } = event.data; // card_view · round_start · bet_intent · round_settled if (type === 'bet_intent') { wallet.placeBet(payload); // your wallet, your rules } });
Illustrative. The full event schema and a sandbox wallet ship with the integration docs.
Regulators are moving toward scrutiny of design, not just of odds. The layer is built for that conversation.
A break after losses
The feed offers a pause card automatically, and honours an operator-side risk state that can only tighten it, never loosen it.
A guaranteed non-betting share
A fixed proportion of the feed never asks for a stake. That proportion is configurable upward only, and every decision is logged.
An honest close
Sessions end with a plain summary that includes the net position, not with another offer to keep going.
Limits the player owns
Stake caps, loss limits and session timers set in two taps. Tightening applies instantly; loosening takes 24 hours, by design.
Won't this just redistribute revenue we already have?
The pilot runs only on segments that produce nothing today: registered-never-played, sportsbook-only, lapsed 30+ days, browse-never-open. The headline metric is total 30-day NGR per eligible player across every surface, against a randomised holdout, with the cannibalisation view shown plainly.
Why not build this ourselves?
You could — the container is deliberately simple. The question is whether it deserves a slot on your roadmap before anyone has proved the format lifts revenue on your players. That is what the pilot answers, in 90 days, at no engineering cost beyond one evening of integration. The parts that are hard to copy — the feed-born original games and the shared content network — come with us.
Does this change our licence position?
No. The feed runs inside your app, on your licence. Games are your certified games, unchanged. Bets are placed and settled in your systems.
Who holds the money?
You do. We never hold a balance. The feed emits a bet intent; your wallet decides. A sandbox wallet ships for integration testing.
Will it slow the app down?
The player bundle is ~92 kB gzipped and loads in an iframe, isolated from your app. Cross-origin embed is proven in CI.
Can we brand it?
Colour, type and corner radius come from a per-operator config. The format stays the same; the skin is yours. No code changes.
Is the feed personalised?
Yes — at session level, by rules rather than a black box. What a player watches shapes what they are offered next, composition quotas keep the mix balanced, and behaviour moves the feed in both directions: a losing streak triggers a pause card and non-betting content, and the operator's risk state can only tighten it. Every selection is logged in the auditable decision log. We do not build cross-session taste profiles today — if pilot data shows a smarter ranker adds lift, it ships behind the same audit log.
What currencies does it work in?
Multi-currency with 8-decimal precision, including crypto stake sets and currency switching mid-session.
What does it cost?
The feasibility check is free. The pilot is free: €0 setup, €0 licence for 90 days. A rollout is a setup fee, a monthly minimum and a small share of feed-attributed GGR — the minimum credits against the share, and the exact numbers are fixed in writing before the pilot starts.
What if the pilot shows no lift?
Then the system has done its job: it told you. The success metrics and the post-pilot price are agreed in writing before the pilot starts.
Three links, no sign-up. Open them on a phone if you can.
Three things make a pilot straightforward.
Test us on one segment.
A 90-day pilot on a single lobby segment, with the success metrics and the post-pilot price agreed in writing before it starts. The first step is free and needs no call: send eight weeks of anonymised per-user revenue and we send back what a pilot could realistically add — before you commit to anything.