Skip to content
Cupcake-DRCP for Enterprise · Linux console walkthrough · Example dataLooking for the Mac app? →

Where the morning starts

MySQL replication dashboard

Open one project, and the rest of the console follows it everywhere.

It's the page you land on after sign-in. Every connection, plan, snapshot, run, comparison, CDC stream, and schedule lives under the project you pick on the left — so wherever you click next, Cupcake already knows which database move you're inside.

788drift to chase · example
3jobs in flight · example
1/4license in use · example
CupcakeProjects
Projects

1 replication project

ops-warehouse 5/22/2026
● ACTIVE

ID

ops-warehouse 24a41c

UPDATED

5/22/2026

Analytics

Account-wide rollup across 1 project · last 7 days

ACTIVE PROJECTS
1

0 inactive

ACTIVE JOBS
1

5 run last 7d

DRIFT DETECTED
788

across 6 runs

SCHEDULE RUNS (24H)
1

all clean

LICENSE HEADROOM

Active jobs

1/4

Jobs by status · last 7d

5
FriSatSunMonTueWedThu
completed running failed stopped

Drift trend · by project

1 series
6/13/20266/18/2026

ops-warehouse 788

Throughput by project · last 7d

top 0

No completed jobs in window

Most active projects · last 7d

1 ops-warehouse 24a41c
3

License headroom watch

Active jobs 1 / 4
LICENSEvalid WORKERhealthy JOBS3 active build 2.7.81 · Web v2.7.81 · Built Jun 18, 2026, 04:09 PM CDT · API v2.7.81

Illustrative Enterprise interface with example data. Controls are shown for reference; operations run in your installed application.

Product details

What you're actually looking at

The mockup above is the screen the team opens first every morning. Below is a walk through what's on it, what the colors mean, and which corners of the page are doing the most work.

The page you land on

Sign in and this is what's waiting. The card at the top is the project itself — its name, the small green ACTIVE pill, the date it was last touched, and a tidy little ID chip you can copy when someone in Slack asks. The block underneath is the seven-day story of every project in the account, so the morning's first scan is one screen instead of seven.

What the analytics actually show you

Five tiles run across the top. Active Projects and Active Jobs answer 'is anybody working?' — and the small green dot on Active Jobs means a live job is producing heartbeats right now. Drift Detected is the loud one — when comparisons turn up rows that disagree, the count lands here in amber, and 788 is loud enough to be the reason someone opens this tab. Schedule Runs (24h) is the quiet honest one: did the overnight cron fire? License Headroom is the runway — the bar fills as you spin jobs up, and you find out you're capped before the next job fails to start, not after.

What the charts dig into

Jobs by status breaks the week down by day so a Tuesday spike in 'failed' stops being a vague impression. Drift trend draws the comparison results across the week — the line is calm until it isn't, and the spike has a date next to it. Throughput is the empty state in the screenshot above; in a real account, it ranks the projects by rows moved, so you know who's eating the most of the worker pool. The bottom row is the leaderboard of the week and a second look at license use, side by side.

How a team actually moves through it

The usual morning is: glance at the rollup, find the project the KPIs are pointing at, click into it. The left rail then locks to that one project — Overview, Connections, Plans, Snapshots, Runs, Compare, Reconcile, CDC, Schedule — and every tool you click next is still aimed at the same database move. Administration (Activity, Users, Assignments, Licensing) is its own section below because it cuts across projects, not into one.

Why this layout, and not a list

Database work has a long blast radius and a short attention span. The day a staging job ends up pointed at production is the day someone updates their resume. Projects keep each environment in its own lane and the analytics block is the early-warning system: amber drift means a comparison found rows that shouldn't disagree, a flat throughput chart on a workday means a stream stalled, a license bar creeping toward 4/4 means tomorrow's schedule is about to refuse to run.

The three things worth glancing at every morning

Drift Detected (is anything diverging right now?), the Drift trend chart (is it getting worse?), and the License headroom watch (do we still have room to spin up the day?). When all three are quiet, the rest of the page can be browsed at coffee speed. When one is loud, it tells you which sidebar item to open first.

Feature highlights

What this page gives back

The morning view

Sign in and the day is already laid out for you — which project is humming along, which one needs eyes on it before standup, and what the overnight schedule actually got done.

A week of work in one scroll

Drift detected, jobs by status, drift trend, throughput, the most-active projects, license pressure — all rolled up for the last seven days. Nobody finds out from a Friday ticket what was already true on Monday.

One project, one workspace

Click a project and the left rail locks to it. Overview, Connections, Plans, Snapshots, Runs, Compare, Reconcile, CDC, Schedule — every tool aimed at the same database move. Cross-project mix-ups stop being a thing you can do by accident.