Skip to main content
Fleack sits between your mobile app and your backend. By pointing one DNS record at Fleack, your team can test prices, ad frequencies, reward amounts, copy, and feature toggles on every live app version — instantly, without touching client code or waiting for a store release.

Quick Start

Get your first A/B test live in 5 minutes. One DNS record is all it takes.

Core Concepts

Learn about endpoints, levers, tests, segments, and the results engine.

Integration

Understand how Fleack intercepts traffic and what the fail-open guarantee means.

Recipes

Step-by-step guides for the most common mobile growth tests.

​
How Fleack works

Fleack intercepts every API call your app makes through a single CNAME on the hostname you already use. It forwards requests unchanged to your real backend, and on the way back it rewrites the targeted JSON value for each user’s assigned variant. When no test is running, the response is byte-identical to what your backend sent.
1

Point DNS at Fleack

Add a CNAME on api.your-game.com pointing to your Fleack tenant hostname. No code changes in the app.
2

Traffic flows through the edge

Fleack captures request/response samples and automatically classifies which endpoints are safe to test.
3

Pick a lever and launch a test

Choose a parameter from the Levers catalog — AI finds them automatically. Set variants, allocations, and a segment, then click Launch.
4

Read results and promote the winner

The Bayesian results engine shows win probability per variant. Promote the winner with one click — no engineering required.
Fleack is designed to be fail-open: if anything goes wrong on Fleack’s side, your end users always see the original backend response. Fleack never breaks your app.