Every scroll
is a round.
fidra adds a vertical, playable feed to your app. Players scroll, watch a round play itself, and join with one tap — inside your product, on your licence, through your wallet.
What sits in the feed
Two classes of content, and the difference is commercial, not cosmetic.
Your certified games
The crash and instant titles already in your catalogue appear as live round cards. A tap opens the full, unmodified game. We change the presentation, never the mechanic — so nothing in your certification changes.
Games born for the 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.
Your brand, our format
Colour, type and corner radius come from a per-operator config. The format stays the same; the skin is yours.
Where the new money comes from
The feed is pointed at players who produce nothing today. You cannot redistribute zero — growth here is incremental by construction, and the pilot runs on these segments alone.
Registered, never played
Often 30–50% of a base: an account, a deposit path, and not one casino round. Watching costs them nothing — that is what makes the first tap happen.
Sportsbook-only
They already trust you with money and have never opened the casino door. A feed between fixtures is a far lighter step than a lobby ever was.
Lapsed 30+ days
The re-activation email they ignore, replaced by a surface that is already mid-round the moment they wander back in.
Browse, never open
Lobby visitors who scroll the tiles and leave. In a feed the game is already playing — there is nothing left to open.
Our system tells you if we are not working.
Integration is one evening
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
}
});Safety that cannot be switched off
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.
Questions we get first
Won’t this just redistribute revenue we already have?
That is the right first question, and the pilot is built so the answer cannot hide. It runs only on segments that produce nothing today — registered-never-played, sportsbook-only, lapsed — where redistribution is structurally impossible: you cannot cannibalise zero. And the measurement reports total NGR per eligible player across every surface, cannibalisation view included, so if the feed merely moves existing spend sideways, our own dashboard says so.
Does this change our licence position?
The feed runs inside your app, on your licence. Bets are placed through your wallet against your certified games. Where a market raises a component-classification question, we work it through with your compliance team before launch rather than after.
Who holds the money?
You do. fidra never holds a balance. Every bet is placed and settled in your systems, through the wallet API you already run.
Will it slow the app down?
The feed loads as a separate surface, around 88 kB gzipped, and cards render as they come into view. It sits on top of your app rather than replacing anything in it.
Can we brand it?
Yes. Colours, typography and corner radius come from a per-operator config, so the feed reads as part of your product rather than a widget bolted onto it.
What currencies does it work in?
Any of yours. Currency arrives with the session rather than being fixed per operator, so one player can be in USDT and another in BTC inside the same casino, and a player can switch mid-session. Balances are held as integers to the currency’s own precision — eight decimals for BTC, two for fiat — so nothing is lost to rounding. Stake presets follow the currency automatically.
What happens to our existing games?
Nothing. They stay exactly as certified. The feed presents a live round as a card; a tap opens the unmodified game in full.
What if the pilot shows no lift?
Then the holdout will show it and we will say so. Commercial terms are agreed in writing before the pilot starts, so a null result costs you integration time and nothing else.
Nothing here is a mockup
Three links, no sign-up. Open them on a phone if you can.
The feed
Scroll it, watch a round run itself, play one.
fidra-pi.vercel.app/app?demo=1
The same feed, embedded
A mock operator app with the live event console beside it.
fidra-pi.vercel.app/embed-demo.html
The same feed, in BTC
Eight-decimal balances, a crypto stake set, and the currency switching mid-session — the way a dual-rail operator runs.
fidra-pi.vercel.app/embed-demo.html?crypto=1
Is this a fit?
Three things make a pilot straightforward. If one is missing, say so on the call — it usually changes the shape of the work rather than ruling it out.
You control your own front end
The feed drops into an app you can change. If your lobby is delivered by a turnkey platform, the conversation starts with them instead — we can help open it.
You already run crash or instant content
The format is built for round-based games. Slots-only catalogues work, but the first version of the feed leans on titles that resolve in seconds.
You can hold back a control group
Measurement needs a slice of eligible players who do not see the feed. Without a holdout we can still launch, but we cannot prove what it added — and proving it is the point.
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.
Start the conversationWhat you run today, and whether the feed fits it.
Your engineers and ours, on wallet, events and scope.
Segment, metrics, duration and price, agreed up front.