Lightweight A/B testing workspace

Your A/B test results in minutes

Upload a dataset and get a complete statistical analysis — no SDK, warehouse integration, or engineering setup required.

No credit card · No integration required · Free for individual analysts

AB-Labz experiment analysis — effects, confidence intervals, and conclusions

Product tour

See the complete experimentation workflow in one workspace.

Follow an experiment from uploaded data and statistical analysis to hypotheses, decisions, calendar planning, and the searchable knowledge base.

Click the video to watch the guided walkthrough.

Your experiment should not live across five different tools

The hypothesis starts in Jira. The sample size lives in a spreadsheet. The analysis runs in Python. The conclusion ends up in a presentation — and six months later, nobody remembers what was actually shipped.

AB-Labz keeps the full experiment context together without forcing you to rebuild your testing infrastructure.

The fragmented way
Jira / Notion
Hypotheses and requests from stakeholders
Excel / Google Sheets
Experiment calendar and sample size estimates
Python / R scripts
One-off analysis, results buried in notebooks
Confluence / Docs
Manually written conclusions. Lost after 3 months.
No portfolio view
Nobody knows the actual win rate or program impact
With AB-Labz
Upload a prepared dataset
CSV from SQL IDE, DataGrip, or DBeaver. Analyze in minutes.
Complete statistical analysis
Auto method selection, preprocessing, Monte Carlo, FDR — no notebook rebuild.
One continuous experiment record
Hypothesis, design, result, conclusion, and decision in the same card.
Export or share
Markdown for Confluence, Notion, or Git. Shareable link — no login required.
Grow into a workflow
Backlog, calendar, team tools, and portfolio analytics — when you need them.

Start with one test. Build a system over time.

Analyze the dataset you already have. Then add context, export the result, and keep it in a growing experiment archive.

1 · Entry

Analyze immediately

Create an account, upload a prepared dataset, and run the analysis. No SDK, data warehouse integration, or engineering support required.

How to prepare the file format
2 · Keep it

Keep the result

Save the analysis as an experiment record together with its hypothesis, metrics, design, conclusion, and decision. Export to Markdown or share a link.

3 · Grow

Grow into a workflow

Add backlog management, scheduling, team collaboration, and portfolio analytics when spreadsheets and isolated calculations stop being enough.

One calculation becomes a full experimentation workflow

From an idea backlog and a testing calendar, through analysis and decisions, to an archive — and a clear view of how the whole experiment program performs.

AB-Labz workbench — backlog, calendar, archive, and program overview in one workflow
Idea backlog
Hypotheses waiting to be tested
Testing calendar
Schedule and capacity planning
Experiment archive
Results, decisions, and learnings
Program effectiveness
Win rate, signal rate, impact
Portfolio Analytics

Know what the experimentation
program actually delivers

Because plans, results, and decisions live in connected experiment records, AB-Labz can evaluate the program as a whole — velocity, signal rate, win rate, capacity, conversion impact, and financial contribution across teams and periods.

1
Operational
Capacity, SRM Health Rate, Sample Sufficiency — is the machine running well?
2
Product
Win rate, signal rate, tag-level breakdown — what areas of the product actually respond?
Consistency
Signal rate in trend — shows whether the team is improving hypothesis quality over time, or running the same experiments in circles
3
Business
Revenue impact and business contribution — the numbers you bring to the quarterly review
See Portfolio Analytics →
Level 1 · Operational Last 90 days
80%
Capacity
94%
SRM Health Rate
87%
Sample Sufficiency
Level 2 · Product 50 experiments
Win Rate 28%
Signal Rate 61%
Consistency (trend) ↑ improving
Level 3 · Business Q2 2026
Revenue impact
+€342k
Conversion impact
+2.4 pp
14
Winners
6
Losers
30
Inconclusive

No changes to your traffic assignment stack

AB-Labz does not split traffic or replace your feature flag system.

Use GrowthBook, Statsig, PostHog, an internal platform, or any other assignment method. Upload a prepared dataset today, then connect an API or local runner only if automation becomes useful.

No SDK installation. No mandatory warehouse connection. No engineering project required to get started.

Need a split system?

Open-source options like GrowthBook work well underneath AB-Labz. We have a setup guide if you are starting from zero.

Read the setup guide

GrowthBook

Statsig

LaunchDarkly

Unleash

PostHog

Firebase A/B

Amplitude

Optimizely

Your own

One experiment. One continuous record.

A hypothesis does not disappear when the experiment starts. The same record moves through planning, analysis, decision, and archive.

1

Hypothesis

Capture the idea, metric, MDE, and audience in the same card that will later hold the result.

2

Design

Sample size, variants, and guardrails stay attached to the experiment — not buried in a spreadsheet.

3

Schedule

Park the test on the calendar or Gantt so overlaps and free traffic are clear.

4

Analyze

Upload the dataset and run the full analysis. Results land on the same experiment record.

5

Decide

Record the conclusion, business decision, and what ships — not just the p-value.

6

Learn

Cards accumulate into a searchable archive and feed Portfolio Analytics for the whole program.

Start with the experiment you are analyzing today

Create a free account, upload your dataset, and get the result — no integration or team rollout required. When you are ready, keep the calculation as part of a connected experimentation workflow.

Analyze your first experiment

FAQ

Can product managers use AB-Labz without a statistician?

Yes. The system automatically selects methods and identifies data issues, and the AI assistant helps understand the tables. A statistician still helps in complex cases — but is not required to run a standard analysis.

How is it different from Google Optimize / VWO?

AB-Labz starts with a prepared dataset, so you can run an analysis without installing an SDK, connecting a warehouse, or changing your traffic assignment stack. Planning, decisions, and portfolio analytics can be added around the result when needed.

Do I need statistical skills?

No. The system automatically selects methods and prepares data. But we provide detailed documentation so you can correctly interpret results.

Does it work with our splitting system?

Yes. AB-Labz does not split traffic — your system does that. Start by uploading a prepared CSV dataset. Connect an API or local runner later if you want recurring updates.

What metrics can be analyzed?

Conversion, numeric, and ratio metrics, including revenue, LTV, CTR, and average order value. The system automatically selects the right test and data preprocessing for each metric type.

What if we have low traffic?

Monte Carlo resampling and Bayesian forecasting support analysis in lower-traffic settings, while the interface clearly surfaces uncertainty and sample limitations.

How is data protected?

AB-Labz offers two data handling options. Via API: data is transmitted encrypted, stored during the experiment, and deleted after analysis completion. Via Runner: raw data never leaves your infrastructure — computations happen locally, only aggregated results without user_id are sent to the cloud. API uses Bearer tokens for authentication. Each organization is isolated.

Are A/B/C tests supported?

Yes. You can analyze experiments with any number of groups. The system automatically determines group count and applies appropriate test classes and data preprocessing.