03 Dec 2025 · 10:41document
Brand A logo kit · 2026
12 pages · lockups kept
AI creative workspace
AI generators are stateless. Your brand isn't.
Zenflow is the state layer between them. It remembers what your brand approved, retrieves it into whichever model is best this month, repairs what's wrong from your real assets, and gets better with every yes.
Free to start. Pay the provider's price plus a visible 12%. No credits that expire.
Prompt · Brief
Christmas 2025 · hero
the dog from last year's cultural campaign, same pose, but for Christmas @rex
@rex77 charsReady
Reference · Memory
@rex · Cultural 2025
instance matchCultural 2025approved 19 Oct
Image · Generator
Nano Banana 2
Nano Banana 2
1024 × 1536×4
ready1024×1536$0.035 + 12%4 outputs
Verify · Meters
Identity & brand checks
identity0.97
pose0.94
collar#C8471C
paletteΔE 1.2
stored with asset passes brand rules
Approval · Chain
Christmas 2025
Art director09:41
Creative director10:05
Brand11:20
Clientpending
waiting on client · share link
The main context — why a state layer
Swap the model. The memory stays.
Every image and video model on the market forgets you the moment the session ends. The character it held so well dies when the tab closes. The references you dragged in have to be dragged in again tomorrow, in the next tool, for the next campaign. The brand book was never read. The two hundred assets your client approved last quarter were never seen. The thirty-seven rejections taught it nothing.
That is fine for one person making one picture. It is not fine for a team producing two hundred on-brand assets for six client brands by Friday, across models that change every month.
Zenflow sits above the models and holds the state they can't. Every prompt, generation, approval and rejection is stored with time. When you ask for "the dog from last year's cultural campaign, same pose, but for Christmas", Zenflow finds that exact dog, shows you it remembered, and loads it into the model you choose. When a render is ninety percent right, it repairs the ten from your real logo, your real ambassador, your real product. And every approval your creative director gives makes the next run more on-brand, for that brand only.
Brand memory
Northwind
@talentSocial set · Summer 2026same expressionuniform · navyglasses on
unchanged across 0 model swaps
1,284 approvals48 rules
Image · Generator
Nano Banana 2
Nano Banana 2
keptidentity 0.98
Image · Generator
FLUX.2
FLUX.2
keptidentity 0.98
Verify · Across models
On-brand first pass
with memory 94% avgwithout · 40%
Brand memory
Everything your brand approved, stored with time.
Zenflow keeps the whole record, not a folder of files. Each prompt, each generation with the exact model that made it, each approval and rejection with the note the reviewer wrote, each brand rule, each direction document. Every item is embedded and timestamped, so "the summer ambassador shots" and "what the client rejected in May" are questions the workspace can answer.
03 Dec 2025 · 11:02generation
Brand A · sofa · logo held
Nano Banana 2 · 1174×1174
03 Dec 2025 · 16:20approval
Creative director · approved
note: the chest logo sits square
09 Dec 2025 · 09:30rule
the chest logo never crops at the seam
evidence · 11 approvals
19 Oct 2025 · 09:14generation
@rex · cultural hero · frame 04
Nano Banana 2 · 1024×1536
14 Nov 2025 · 15:36prompt
the dog from last year's cultural campaign, for Christmas
resolved → @rex · Cultural 2025
14 Nov 2025 · 15:41generation
@rex · Christmas hero · 02
Nano Banana 2 · identity 0.97
18 Nov 2025 · 12:11approval
Client · approved
note: same dog, new season
07 Jan 2026 · 11:18prompt
@shoe, one step, plain floor
resolved → @shoe · 6 references
07 Jan 2026 · 11:22generation
@shoe · walk · start frame
Seedream 5 · start frame
07 Jan 2026 · 11:45generation
@shoe · walk · 4 s
Veo 3.1 · 720×1280 · 4 s
08 Jan 2026 · 09:26approval
Brand · approved
note: the colourway holds in motion
04 Jun 2026 · 10:07generation
@talent · Social set · hero frame
Seedream 5 · Summer 2026
04 Jun 2026 · 10:31generation
@talent · same expression · the clothes rail
Seedream 5 · identity 0.98
04 Jun 2026 · 10:52generation
@talent · same expression · a second model
Seedream 5 · identity 0.98
04 Jun 2026 · 17:40approval
Creative director · approved
note: all three, one face
24 Nov 2025 · 17:31rejection
Art director · rejected
note: the wordmark is garbled
24 Nov 2025 · 17:40generation
@logo · wordmark restored · v3
Muse Image · 18/18 glyphs
25 Nov 2025 · 09:15approval
Brand · approved
note: v3 from here on
26 Nov 2025 · 09:40rule
the wordmark never gets text over it
evidence · 3 rejections
09 Feb 2026 · 14:12fact
@headphones registered · product
cutout · 937×1000 · transparent
12 Feb 2026 · 11:26generation
@headphones · Mascot 2026 · brand type behind
FLUX.2 · product unchanged
14 Feb 2026 · 10:05approval
Creative director · approved
note: brand type behind, product unchanged
16 Feb 2026 · 09:40rule
the headphones keep their exact blue
evidence · 7 approvals
One memory per brand. Nothing leaks between them.
Memory is scoped to the brand workspace. An agency running six client brands runs six memories that never see each other, enforced in the database, not by convention. Each one gets sharper on its own.
Explicit when you want it, inferred when you don't.
Register the things that matter as Context Variables: @rex the mascot, @ambassador, @logo, @hero-bottle, each with up to ten reference images. Tag one in a prompt and exactly those references go to the model. Describe something without a tag and the retrieval engine finds it for you.
Portable and auditable.
Your memory is yours. Every asset carries its full lineage, and the whole graph can be exported. Memory that lives inside one vendor's stack is a lock; memory you can take with you is an asset.
The retrieval engine
Finds the exact thing, not something like it.
Most search finds "a golden retriever." Zenflow's retrieval is built to find your golden retriever, from that campaign, in that pose. It runs four kinds of index over everything in the brand memory: instance retrieval for "is this the same product, logo or mascot"; identity retrieval for the faces of your registered ambassadors; language-to-image retrieval for "approved cozy fireplace scenes"; and document retrieval over briefs, decks and direction docs that keeps layout and typography intact instead of flattening them to text.
“the suitcase from the spring launch, hero angle”@hero-case
Image · Approved reference
@hero-case · Launch 2026
instance match- campaign
- Launch 2026
- generated
- 04 Mar 2026
- model
- Nano Banana 2
- approved
- 06 Mar 2026 · Brand
Resolution
- Context Variable match@hero-case · 8 references
- campaign scopeLaunch 2026 · 02–16 Mar
- visual search1 of 148 · ranked by approval
Index
- instance
- identity
- language-to-image
- document
Zenflow retrieves @hero-case
Time is part of the query.
"Last year's cultural campaign" is a date range, not a keyword. The engine resolves campaign and festival references against your project calendar, scopes the search to that window, and ranks what it finds by what was actually approved. Facts carry validity windows too, so "the primary logo" can mean v2 in February and v3 in April, correctly.
Resolution in three steps.
First it looks for a registered Context Variable that matches what you said. Then it scopes to the campaign you named. Only if neither exists does it fall back to visual search over the scoped pool, cluster the results, and surface the dominant subject, and it offers to save that subject as a Context Variable so next time it's one tap.
Ranking that learns from you.
Every time you confirm or dismiss a candidate, the ranker learns which was right. Retrieval gets better in the same way generation does: from your decisions, per brand.
Under the hood
Under the hood: retrieval runs on Postgres with vector indexes, so memory, generations and approvals are one system of record, not three. Frozen state-of-the-art embedding models do the encoding; all learning happens in a small, reversible ranking layer, never in the embedders, so nothing drifts and nothing needs re-indexing when you approve something.
How context is shown
Nothing is injected silently.
When Zenflow retrieves something, you see it before it's used. A confirmation card shows the candidate with its provenance: the campaign it came from, the date it was generated, the model that made it, its approval and the reviewer's note. One question: Is this the one you meant? Use it or dismiss it. Retrieved context never goes to a model without a person seeing it.
Prompt · Brief
Prompt
the cat from the tiger shoot, wearing the @headphones, brand type behind it.
@headphones75 charsReady
Context
FLUX.2
2/4 slots
@headphonesproduct
The brand's over-ear headphones. The product is never altered and the blue stays exact.
- campaign
- Mascot 2026
- generated
- 12 Feb 2026
- model
- FLUX.2
- approved
- 14 Feb 2026 · Creative director
- note
- “brand type behind, product unchanged”
Is this the one you meant?
Retrieved context never goes to a model without a person seeing it.
Image · Generator
FLUX.2
FLUX.2
product kept · #11024×1536$0.040 + 12%
A reference node on the canvas, visible to the whole team.
Confirm a retrieval and it becomes a labelled node, @headphones, Mascot 2026, product kept, wired into the generator. Everyone in the multiplayer canvas sees what the memory supplied, in real time, as a real object they can move, inspect or disconnect.
Every asset has a Memory tab.
Open any generated asset and see exactly what it was conditioned on: which references, in which roles, which brand rules applied, which model and version, what the verification meters scored, and the retrieval trace that led there. Approve it, and the tab shows that too.
A memory graph for admins.
Zoom out and see the brand's memory as a graph: which assets and entities are used the most, by whom, feeding which campaigns, and the full ancestry of any single generation. What memory is doing is never a black box.
Real-time retrieval
It resolves as you type.
Referential phrases, "the dog we used", "that logo", "the ambassador from the summer shoot", light up in the composer as you write them. Retrieval runs in the background, under a third of a second, and the candidates are waiting by the time you finish the sentence.
Northwind · canvas · 2 people
composer · Northwindlistening
@rex · Cultural 2025Christmas 2025retrieval runs in the background
Memory · Candidate
@rex · Cultural 2025
instance match 0.99Christmas 2025 · 48 assets284 msapproved 19 Oct 2025
Memory answers anywhere
Zenflow connected to Claude, ChatGPT or Gemini. The brand memory answers in the tool the question was asked in.
Claude · connected to Zenflowtoken · northwind-read
What does this client keep rejecting?
Text placed over the wordmark — three rejections between 24 Nov 2025 and 06 Mar 2026 — and hero shots taken off the approved angle (two). Both are playbook rules now.
asset 0419 · rejected 24 Nov 2025asset 0442 · rejected 06 Mar 2026rule · keep the wordmark clean
answered 14:02:11 · 268 ms · 3 citations@-mentions from memory.
Type @ and the brand's Context Variables autocomplete: mascots, ambassadors, products, logos, scenes, styles. The same grammar works in the chat composer and on the canvas.
Live across the room.
Zenflow's canvas is multiplayer. A retrieval one person confirms appears for everyone at once, so an art director in London and a client in New York are looking at the same reference in the same second.
Memory answers anywhere.
Connect Zenflow to Claude, ChatGPT or Gemini and ask the brand memory directly: What does this client keep rejecting? What did we approve for the beach campaign? Answers come back timestamped and cited, with links to the assets. Decisions made in those conversations can be saved back into Zenflow as drafts for the team to accept.
Fixing the ten percent
Repair from your real assets. Not from a guess.
Every image model treats every part of a picture as negotiable, including the parts that aren't: the spelling of your wordmark, the face of your contracted ambassador, the shape of your product. When a render is ninety percent right, most tools make you roll again. Zenflow repairs the region that failed and leaves every other pixel untouched.
beforegarbledidenticalafter18/18 glyphs0 px changed
One asset, all the way through: the wordmark render is detected, checked against the brand kit, restored from logo.svg and re-checked — and the loop runs on its own.
repair loop · @logo · product-logo · v3auto · runs on every render
Repair · Detect
Locate the defect
wordmark1 region0.91 confidence
Repair · Validate
Check the brand kit
Northwind brand kit
18 glyphs6 swatchesshape lock
no pixels touched0.2s
Repair · Restore
Restore from the real asset
Rigid overlay
garbledoutside region locked
Verify · Re-run
Re-run the same checks
glyphs restored0/18
- wordmark · 18/18 glyphs
- palette · ΔE 1.2
- outside region · 0 px changed
kept · beats originalstored with the asset
Detect. Validate. Repair. Verify.
Zenflow locates the defect, checks it against your brand kit without touching a pixel, restores it from the brand's real asset, the actual vector logo, the ambassador's identity references, the true product shots, and re-runs the same checks on the result. A repair that doesn't strictly beat the original is discarded. The system can even reject its own refinement when the refinement makes legibility worse.
Different failures, different engines.
A wordmark is rigid and belongs to the brand. A face is deformable and has to be modelled. A product has to be reconstructed from reference. Zenflow uses a different repair path for each, because collapsing all three into one inpainting model is how teams ship the pasted look.
A meter, not a vibe.
Identity is measured, not eyeballed. The identity meter scores how close the repaired face is to the ambassador's references and shows you the number. Wordmarks are checked character by character. Colours are checked against the palette. Every score is stored with the asset, so "identity retained: 0.94" is a fact in the lineage, not a claim in a deck.
Video, honestly staged.
Image repair ships as a product. Video repair runs as an experimental feature in pilots: the same memory, the same references, the same lineage, while frame-exact identity across a full spot is still maturing in the underlying models.
Learns with every yes▲
Approvals are training data. Zenflow is the first tool that captures them.
A creative director's yes and no are the richest signal about what on-brand means, and in every other tool they move a card on a board and disappear. In Zenflow every approval and rejection, with its note, becomes part of the brand's memory.
Approval queue · Northwind3 pending
Approval · Candidate
@shoe · Spring 2026
Seedream 5
shoe unchangednotestart frame · Spring 2026 · shoe drop
3 of 4 · 00:07pending
Approval · Candidate
@headphones · Mascot 2026
FLUX.2
product placednoteproduct placed · brand type behind the subject
2 of 4 · 00:06pending
Approval · Candidate
@talent · Social set
Seedream 5
identity 0.98noteSocial set · Summer 2026 · all three, one face
1 of 4 · 00:05pending
drag right for yes · left for no
Brand memory · Northwindappend-only
- Fact
the primary logo changed — v3 from here on
- Rule
the chest logo never crops at the seam
- Signal
retrieved candidate confirmed · 9×
- Fact
Launch 2026 runs 02–16 Mar 2026
- Fact
one face carried the whole social set
app A
app B
app C
app D
too many apps · one scattered brand — other toolsyour brand stays consistent — Zenflow
Day 1
drag the yearDay 1Day 365
Three kinds of learning, all visible.
Facts with dates: the primary logo changed in March; this client rejects purple backgrounds; @rex appeared in last year's cultural campaign. Playbook rules per brand and per model, each with evidence: keep the mascot at 35–45% of frame height, never put text on the dog, collar is #C8471C. And ranking signals: which retrieved candidates were confirmed, which generated options were chosen. You can read every rule, see what it's based on, and retire it.
Nothing is rewritten, nothing is hidden.
Rules are added, reinforced, decayed or retired one at a time with an audit trail. Learning lives in prompts, rules and ranking, never inside the model weights, so it is bounded, reversible and portable across every model in the registry.
Day one versus day three-sixty-five.
Other tools are the same product on day one and day 365. Zenflow, by day 365, has become your brand.
Templates
Start from a workflow that already knows the job.
Every template is a canvas you can run as-is or rebuild. Each one is wired to the brand memory, so the first run already uses your Context Variables, rules and approved references.
Prompt · Brief
Product hero
the headphones on the hero, brand font and brand text behind the subject @headphones
@headphones84 charsReady
Product · Reference
@headphones
cut outthe product itself
Image · Input
Start frame
inputthe frame we started from
Image · Generator
FLUX.2
FLUX.2
brand font behind the subject1024×1536
Verify · Brand kit
Verification
product unchangedbrand fontcolour
every score stored
wired to brand memory · Northwind
Workflows
A visual pipeline where every step is explicit.
Zenflow's canvas is node-based. Prompts, references, generators, editors, verifiers and approvals are nodes; the edges show exactly what feeds what. You can see how an asset was made, change one step, and run it again.
WorkflowChat
Prompt · Brief
Christmas 2025
the dog from last year's cultural campaign, same pose, but for Christmas @rex
@rex77 charsReady
Reference · Memory
@rex · Cultural 2025
approved 19 Oct 2025
Image · Generator
Nano Banana 2
Nano Banana 2
same dog · new season1024×15364 outputs
Verify · Brand kit
Verification
collar #C8471C pose palette
identity 0.97
Approval · Chain
Christmas 2025
Art director Creative director Brand Client
14 Nov 2025 · notes at each stage
the dog from last year's cultural campaign, same pose, but for Christmas @rex
Zenflow
Found @rex · Cultural 2025 in brand memory — approved 19 Oct 2025, pose carried. Generated with Nano Banana 2:
Verified against the brand kit — identity 0.97 · collar #C8471C · palette ΔE 1.2.
Sent to the approval chain: Art director ✓ · Creative director ✓ · Brand ✓ · Client pending.
09:42Ask anything, or type @ to attach a model and generate...
Asking is free. Attach a model when you want to make something.
drag a node — every step is explicitNorthwind · @rex
Branch, batch, and sub-canvas.
Fork a workflow to try three directions from the same references. Run one workflow over a whole list of inputs. Nest a workflow inside another as a sub-canvas so a complex pipeline reads like one step.
Approval chains inside the workflow.
Art director → creative director → brand → client, as stages on the canvas, with notes captured at each one. Nothing ships without the chain, and every decision in the chain becomes memory.
Share a workflow as a tool.
Build the pipeline once, then share a simplified interface. Teammates add the inputs, a brief, a product image, a campaign name, and get on-brand results without touching the full canvas.
Multiplayer by default.
Cursors, presence, comments and live changes. The canvas is a room, not a file.
Models
Any of 420+ models. Pick per step.
Image, video and text models from every major provider, in one registry, with the same prompt grammar in front of them. Use one model for the hero, another for the variations, a third for the repair. Zenflow keeps the references, rules and memory identical across all of them.
Muse Image
Nano Banana 2 and Pro
FLUX.2
Seedream 5
GPT Image 2
Qwen Image 3
Ideogram 4
Kling 3.0
Seedance 2.5
Veo 3.1
Wan 3.0
LTX 2.3
MiniMax H3
Create your own Brand Models.
A Brand Model is a base model plus your memory plus your rules, saved as one thing: "Northwind · product hero · FLUX.2" or "Northwind · mascot · Nano Banana 2". Create as many as you need per brand, per format, per client. Run them like any other model. When a better base model arrives, upgrade the Brand Model without losing anything it learned.
Bring your own.
Agency and Enterprise plans connect your own model endpoints and private deployments. They sit in the same registry, behind the same memory, with the same verification.
Compare before you commit.
Run the same brief through several models side by side and let the meters score them. Zenflow tracks which models your brand approves most often for each kind of job, and recommends accordingly.
When a model disappears, your work doesn't.
Models get renamed, repriced and withdrawn without notice. Because Zenflow's memory sits above the models, a workflow built on one model runs on the next.
Model registry highlights this month: Muse Image, Nano Banana 2 and Pro, FLUX.2, Seedream 5, GPT Image 2, Qwen Image 3, Ideogram 4, Kling 3.0, Seedance 2.5, Veo 3.1, Wan 3.0, LTX 2.3, MiniMax H3, and more. The list changes monthly; the memory doesn't.
Built for agencies
Built for agencies
Organisation
Agency
6 brand workspaces
34 membersroles & permissions
Brand workspace
Northwind
brand memory
9 members
Brand workspace
Aster Foods
brand memory
4 members
Brand workspace
Halden Motors
brand memory
6 members
Brand workspace
Juno Skincare
brand memory
5 members
Brand workspace
Kestrel Telecom
brand memory
7 members
Brand workspace
Solace Hotels
brand memory
3 members
Project
Spring 2026 · shoe drop
final · with the client24 assets3 approvals
Approval · Chain
Final · Spring 2026
Art director17 FebCreative director18 FebBrand18 FebClientpending
3 of 4 decidedshare link · no account
One workspace per client brand.
Organisation → brand workspace → project → approval chain. Members, roles and permissions per workspace. Six client brands, six isolated memories, one team.
Approval chains that match how you actually work.
Concept, draft and final approvals, each with request and decision notes, each with a decider on record. Clients can approve from a share link without an account.
Itemised dollars, ready to rebill.
Every run is a line: model, duration, provider price, Zenflow's 12%. Export per brand and drop it into the client invoice. Credits are unbillable; dollars are.
Born in production.
Zenflow was built as an internal tool inside an Omnicom agency and used on live brand work for a year before it was a product. It was pulled out because the agency asked to white-label it.
A wallet you can read
A wallet you can read
| Model | Run | Provider price | Zenflow fee | Line total |
|---|---|---|---|---|
| Nano Banana 2 | 4 images | $0.140 | $0.017 | $0.157 |
| FLUX.2 | 6 images | $0.240 | $0.029 | $0.269 |
| Kling 3.0 | 4 s video | $0.840 | $0.101 | $0.941 |
| Veo 3.1failed · not charged | 4 s video | $0.00 | $0.00 | $0.00 |
| Seedream 5 | 2 images | $0.056 | $0.007 | $0.063 |
| total · 12 Mar | 5 runs | $1.276 | $0.154 | $1.430 |
Clear transactions. Every run is one line — what ran, what the provider charged, what Zenflow charged, and the total. Nothing is hidden in a credit rate.
Price shown before every run.
You see the provider's price and our fee before you press generate.
No credits. No expiry.
Top up in dollars. Unused balance stays yours.
Failed runs are free.
If the provider fails, you pay nothing.
Visible 12%.
Our fee is a line you can read, not a markup hidden in a credit rate.
Itemised per brand.
Export any brand's spend for any period and rebill it to the client.
Everything on record
Everything on record
Asset
Mascot 2026 · hero
@headphones · product kept1024×153612 Feb 2026
Lineage · Conditioned on
2 references
@headphones@@logo2 referencesfrom brand memory
Lineage · Rules applied
3 rules
brand font behind the subjectproduct unchangedthe headphones keep their exact blue
3 ruleslearned from decisions
Lineage · Model
FLUX.2
FLUX.2
the cat from the tiger shoot, with the headphones and the brand type behind @headphones
4 outputs$0.040 + 12%
Lineage · Scores
Verified
product0.99wordmark18/18paletteΔE 1.2
0.99 productstored with the asset
Lineage · Approvals
Creative director
“brand type behind, product unchanged”
14 Feb 2026decider on record
Export
Client hand-off
Content Credentials
retrievalconditioningapproval
4 filesNorthwind
Lineage on every asset.
What it was conditioned on, which rules applied, which model, which scores, who approved it and when.
Provenance on every export.
Client exports carry Content Credentials that chain the model's own signature to Zenflow's record of retrieval, conditioning and approval.
Audit for the connector.
Every question asked of the brand memory from an outside assistant is logged, scoped by token, and fenced so retrieved text is data, never instructions.
Export the memory.
The whole graph, yours to take.
Six steps
How to build a workflow that remembers
- 01
Create a brand workspace.
Import the brand book, the logos and the last two or three campaigns' approved finals. Zenflow embeds them and registers the obvious Context Variables: mascot, ambassador, logo, hero product.
- 02
Write the brief in the composer.
Refer to what you already have in plain language, or tag it with @. Watch the referential phrases resolve as you type.
- 03
Confirm the retrieval.
Check the candidate card, its date, model and approval. Use it, and it becomes a node on the canvas. Click the context icon on the node to see exactly what was retrieved and what is passed to the model.
- 04
Pick a model, or a Brand Model.
Generate four, keep two. The meters score identity, pose, wordmark and palette before you look.
- 05
Repair the ten percent.
Anything the meters flag goes through the repair pass, from your real assets. Keep only what beats the original.
- 06
Run the approval chain.
Every yes and no, with its note, goes into the brand memory. Next run starts further ahead.
context variables registered on import
Document
Document
Brief
This year’s set with last year’s approved mascot, in the approved pose, in a new setting.
Objectives
- 1Hold the mascot’s identity across every placement.
- 2Ship the set in one week, on one approval chain.
Deliverables
Image6qtyhero + five placements, 1024×1536
Video2qty4s loop, 1280×720
References
Prompt · Brief
Prompt
the cat from the tiger shoot, wearing the @headphones, brand type behind it.
@headphones75 charsReady
Context
FLUX.2
2/4 slots
@headphonesproduct
The brand's over-ear headphones. The product is never altered and the blue stays exact.
#1@headphones#2start frame- campaign
- Mascot 2026
- generated
- 12 Feb 2026
- model
- FLUX.2
- approved
- 14 Feb 2026 · Creative director
- note
- “brand type behind, product unchanged”
Is this the one you meant?
Retrieved context never goes to a model without a person seeing it.
Image · Generator
FLUX.2
FLUX.2
product kept · #11024×1536$0.040 + 12%
Filter models…Brand modelsImage modelsVideo models
keptkept
identity0.98pose0.96wordmark18/18paletteΔE 1.2
4 outputs2 keptscored before you look
before
afterverified0.71 → 0.96
kept · beats originalrepaired from your real assetsregion only
“same dog, new season — approved”
shoe-drop-start.jpg@shoe 1
mascot-christmas-2025.jpg@rex 3
ambassador-shoot-v1.jpg@ambassador 2lighting and face wrong
product-wordmark-v2.jpg@logo 1the wordmark is garbled
mascot-cultural-2025.jpg@rex
Use cases
Product photography at catalogue scale.
The real product, the real label, every angle, across thousands of SKUs.
OpenSocial content for multiple brands.
Six brands, six memories, one team, one Friday.
OpenCultural and seasonal campaigns.
This year's set with last year's approved mascot, in the approved pose, in a new setting.
OpenAmbassador and talent content.
Identity that holds, measured, with the contracted person's references as ground truth.
Open
From our research
Zenflow is a research-led product. The brand repair loop, the identity meter, the retrieval schema for brand corpora, preference-based prompt optimisation, and multi-model routing are all open problems we work on in the open. Read the research, the reading list and the questions we can't answer yet, and talk to us if they are your obsession too.
Read the researchWhat teams say
Quality strong enough to be showcased for Mars-owned global brands and a large Indian conglomerate.
The way it was able to retain and apply context without having to repeatedly re-reference the same information really stood out to me.
It was evident that the team had spent time understanding how users actually interact with the product and translated that into a clean and thoughtful experience.
Three plans
Plans
Studio.
$29 per seat per month, or $290 a year.
One seat, one brand workspace, 420+ models, explicit Context Variables.
Start with your brandAgency.
$149 a month plus $39 per additional brand workspace.
Five seats, three brand workspaces, deep retrieval, approval chains, rebilling export, bring-your-own models.
Start with your brandEnterprise.
Custom, annual.
Unlimited workspaces, SSO, security review, onboarding, private model deployments, memory export SLAs.
Start with your brandAll plans pay the provider's price plus a visible 12% for generation. No credits that expire. Failed runs are free.
13 questions
FAQ
Zenflow is an AI creative workspace for agencies and brand teams. It sits above 420+ image and video models and holds the state they can't: what your brand approved, which references define it, which rules it follows. You generate, approve, repair and ship on a multiplayer canvas, and the brand memory gets sharper with every approval.
No. Retrieval-augmented generation fetches text to help a language model answer. Zenflow's retrieval is built for brand assets: instance-level "is this the same product", identity-level "is this the same person", time-scoped "which campaign", and document-level "which page of the brief". It shows you what it found before using it, conditions the model with role-typed references, verifies the output against your real assets, and learns from your approvals. RAG does none of that.
Their memory learns a user's preferences inside their stack, with their models. Zenflow's memory retrieves specific prior generations with time, shows its work, is scoped per client brand with agency approval chains, runs on any model, and can be exported. It also repairs from real assets with a measured gate, which neither offers.
No. Learning happens in the retrieval ranking, the facts and the playbook rules, never in model weights. That keeps it portable across every model, reversible, and auditable. Private per-brand models are something we research, not something we ship silently.
No. Memory is isolated per brand workspace, enforced at the database level. Cross-workspace access is not a setting that can be misconfigured.
Your workflows, references, rules and memory are model-agnostic. Point the Brand Model at the next base model and run.
Image, video and text models from every major provider, 420+ in the registry, updated monthly. Agency and Enterprise plans can connect their own endpoints.
That the repaired region is restored from the brand's real asset, that everything outside the region is untouched, and that a repair which doesn't beat the original on the same checks is discarded. It doesn't claim prettier images than the frontier models; it claims brand-exact ones, measured.
No.
Provider price plus a visible 12%, shown before every run. Top-ups in dollars, no expiry, failed runs free, itemised per brand for rebilling.
Yes, from a share link, with their decision and note recorded in the approval chain.
Yes. The connector lets you search the brand memory, read the prompt playbook and save decisions back, with every call logged and scoped by token.
You can start free. Advanced retrieval, approval chains and rebilling are on paid plans.
The workspace that remembers.
Add your brand book, your logos and last year's approved campaign. Then ask for the dog from last year's cultural campaign.