LAUNCH
Pricing
Set and discover
Brand
Set the rules once, in one place
Scan
See what is already live
Plan and approve
Preflight
Catch mistakes before customers do
Launches
One decision, fully recorded
Record and report
Audit log
Every change has a history
Integrations
Connect what you already run
Product

A release process for marketing, finally.

Software engineering has had this for twenty years: a shared repository, a review step before code ships, an automated test suite, a clear rollback path. Marketing campaigns touch just as many systems and carry just as much risk, but they’ve never had the equivalent. Launch is that equivalent.

The mapping
RepositoryCampaign workspace
Pull requestLaunch request
Automated testsPreflight checks
Code reviewBrand, legal, and analytics approval
DeployLaunches
RollbackRevert

This isn’t a metaphor for its own sake.

It’s the actual shape of the problem: multiple people touching a shared asset, changes that need review before they’re live, and the ability to undo a mistake instead of chasing it across four dashboards.

Scan — see what’s already in motion

Most teams don’t have a clean, current inventory of every campaign, page, and tracking pixel that’s live. Scan builds one automatically, continuously, without needing an integration project to start.

Learn more about Scan — see what’s already in motion
Preflight — catch mistakes before customers do

Before anything ships, Preflight runs the checks a careful team would run by hand: pricing, tracking, sign-off. If a check fails, Launch calls it a blocker and holds the launch until someone resolves it.

Learn more about Preflight — catch mistakes before customers do
In practice
“2 blockers: ad says $129, page says $149; legal has not seen the final version.” No partial-credit launches.
Launches — go or no-go, with a full record

Launch only arms when every blocker clears and every required approval is in. Once it ships, that moment is on the record, and revert is a real, first-class action.

Learn more about Launches — go or no-go, with a full record
In practice
Asked what happened and why, you answer in seconds from the record rather than reconstructing it from screenshots.
Why this compounds

The value isn’t the scan. It’s the history.

Every launch Launch touches becomes part of a record: what changed, who approved it, what happened after. After a hundred launches, "what breaks if we change this?" and "what worked last time?" aren’t guesses — they’re answered with your own evidence, not a best practice from someone else’s company.

Start where the risk is: what is already live.