for in-house creative teams

Every hook, cut, and static sits in one library instead of a shared drive, a chat thread, and three desktops. Versions stack on the same creative with their history intact, so v4 is the same asset moved forward rather than a new file with a hopeful name.

That is what stops the recurring in-house failure, where the wrong cut goes live because two similar files existed and nobody could tell which one the brand lead meant. Statuses show what is approved and what is still in flight, and publishing picks up the approved version, so the signed-off cut is the one that runs.

Ad account access is a blunt instrument. Letting an editor ship one approved video usually means giving them the whole account, so most teams funnel everything through one or two people who spend their Friday retyping other people’s work into Ads Manager.

Here the ad accounts connect once for the workspace and abilities are granted separately, so someone can create ads without being able to spend, or upload without being able to publish. Members can also be limited to specific folders and specific ad accounts, enforced on the server rather than hidden in the interface.

The links you send out stay under control too: password, expiry, whether downloads are allowed, and revocation whenever you want it closed. When a person changes teams or leaves, removing them revokes their API keys, disconnects their AI tools, and ends their sessions immediately, with no shared login to rotate.

It runs in the browser and as a desktop app, so editors can move large video without living inside an upload dialog. Automations handle the routine watching, like pausing an ad that has spent past a threshold with nothing to show for it.

Teams that script their pipeline get an API, a CLI, and an SDK, plus an MCP server for AI tools. Anything the app can do is available to a script, held to the same permissions as the person who authorized it.