01 / Produce
Campaign Matrix workspace
Each cell can be generated, reviewed, revised, approved, exported, or sent to delivery.
Campaign Matrix
Campaign Matrix turns one approved asset into a production grid.
Generate the first strong social asset or creative recipe, then use Campaign Matrix to review, approve, export, and automate every required variant across brands, formats, audiences, locales, products, and data rows.
The production model
Approved social asset x brand x format x data becomes a reviewable launch pack.
Campaign Matrix is the scaling layer after AI image generation, Image FX, and Studio refinement. The columns and rows carry real production meaning: channel sizes, client brands, audiences, locales, SKU rows, offer variants, and approval states.
Templatexbrandxformatxdata=reviewable campaign matrix
1approved structure from Studio, Templates as Code, or a campaign recipe
Manyreviewable cells for every audience, channel, locale, brand, or product row
Product proof
The grid is a real operator surface, not a slogan.
Campaign Matrix gives teams a place to see what exists, what failed, what needs review, what is approved, and what is ready to leave the system.
Use the previous and next buttons, select a chapter, or press the left and right arrow keys to browse.
02 / Review
Review share
Stakeholders can approve or request changes without entering the full app.
03 / Deliver
Delivery portal
Approved files can move into a controlled handoff surface with metadata and provenance.
Captured seeded product UI. The campaign, review decisions, and delivery metadata shown here are sample data, not customer activity. Open any frame to inspect the full capture.
Who uses it
Growth marketersTurn one offer into channel, audience, lifecycle, and locale variants while keeping approvals visible.
Agency producersReuse the same campaign structure across client brands without mixing brand systems or handoff folders.
Ecommerce teamsCross product rows with promotional formats, seasonal angles, and review states.
Marketing engineersPromote a proven grid into YAML, API, Python, or CLI automation for future launches.
Brand managersReview consistency cell by cell before assets reach delivery portals, schedules, or external systems.
Agent ownersLet trusted local MCP agents prepare matrix work while final approval and publishing stay human-controlled.
Different teams use the same grid for different jobs.
Workflow spine
Campaign Matrix connects creation, review, delivery, and automation.
The matrix sits after creative direction is good enough to repeat and before assets are allowed to ship. It is the control point where AI output becomes campaign production.
CreateGenerate source images, refine in Image FX, or compose a reusable Studio document.
SystemizeCapture variables, brand tokens, formats, copy rows, and conditions in a template or recipe.
MatrixRender reviewable cells across every campaign dimension.
ApproveCompare cells, request changes, retry failures, and keep comments attached.
DeliverExport approved work, create review shares, delivery portals, schedules, or webhooks.
API recipe
Developers can wire the matrix into launch systems.
Use the UI for daily production, then automate the same durable shape through recipes and APIs when a campaign pattern proves itself.
GET /openapi.jsonInspect the generated local API contract.POST /api/renderRender a reusable template with variables.POST /api/campaign-matrix/{id}/exportPackage approved Campaign Matrix outputs.One workflow, two ways to work
Campaign teams build and review the grid in the UI. Developers connect the same campaign structure to existing systems through the API once the process is ready to repeat.
Local-first ownership
Run the campaign system where your team can inspect it.
Keep campaign assets, review decisions, and exports in an environment your team controls. Move from a single campaign to repeatable production without handing off every iteration to another platform.
Image generation requires a configured model and compatible hardware; the review and production workflow remains visible either way.
- Own the workflow.Templates, data, jobs, assets, approvals, exports, and evidence stay visible to operators.
- Control costs.Use local or selected model backends instead of sending every production iteration through a hosted creative SaaS.
- Keep approval explicit.Agents and APIs can prepare work, but review and publishing remain bounded by team policy.
Make the matrix your campaign operating surface.
Start with a use case, prove the workflow in the UI, then automate the repeatable parts once the team trusts the recipe.