Features · Workflows
Chain models into pipelines.
A visual canvas where prompts and files go in one side and finished, post-processed assets come out the other. Mix any models across text, image, audio, and video in a single graph, fan edits over batches, merge tracks — then re-run the whole thing whenever the inputs change.
Build
Six node types, any pipeline.
Inputs hold your prompts and files, Models generate, Edits transform, Combine merges, Files save the result — and Notes document the graph for later. Drop nodes with single-key shortcuts, wire them with edges, undo freely. The canvas is the whole programming model: if you can draw it, you can run it.
Mix
Any model, at any step.
Every Model node picks its own modality, provider, and model — a local Gemma can write the prompt that a cloud Flux renders and a Veo clip animates, all in one graph. The node's connection points adapt to what the model accepts: video models with start- and end-frame support grow image handles for them, and vision-capable local models accept images too.
Assemble
Fan out, then merge.
Edit nodes fan across their inputs — ten images in, ten crops out, processed in parallel on your machine. Combine nodes do the opposite: overlay tracks in parallel mode (a Lyria music bed under a Veo clip, mixed audio) or concatenate files in series. Between the two, one graph can turn raw generations into a finished deliverable.
Run
Run it all — or just one step.
Independent branches execute concurrently, with live status on every node. Iterating on one stage? Run from that node and execution stops at the next model boundary, so you never re-pay for the upstream steps that already worked. A Stop button aborts the run the moment you click it.
Share
Start from a template, share as a file.
Your first workflow arrives pre-built so you see the shape before building your own, templates give running starts, and any graph exports as a plain JSON file — share it with a teammate, publish it, or keep versions in git. Importing it recreates the pipeline, nodes and wiring intact.
Catalog
Every model is a node.
Workflows draw on the entire catalog — every text, image, audio, and video model, local or cloud, is available to any Model node. Browse them all, with real sample outputs, in the models catalog.
FAQ
Workflow questions, answered.
How the node pipeline engine works in CSuite — node types, model mixing, parallel runs, sharing, and costs.
A visual graph you build on a canvas: Input nodes hold prompts or files, Model nodes run an AI model, Edit nodes apply deterministic operations, Combine nodes merge files, and File nodes save results into your project folder. Connect them with edges and press Run — plus Note nodes to annotate the canvas for future you.
Any model in the catalog, in any combination. Each Model node picks its own modality, provider, and model — so one graph can have a local Gemma writing a prompt, Flux 2 Pro rendering it, and Veo 3.1 animating the result. New nodes pre-fill with your globally selected model for that modality.
Independent branches run concurrently — only a node's direct predecessors serialize it. You can also run just a segment: start from any node and execution steps to the next model boundary, so you can iterate on one stage without re-running (and re-paying for) everything upstream.
Image resize and crop, audio trim and convert, and video resize, crop, and transcode — all running locally. An Edit node fans out: feed it ten images and one crop setting, and it processes all ten in parallel.
It merges multiple files into one: in parallel mode tracks play simultaneously — lay a music bed under a video clip, or mix audio tracks together — and in series mode files concatenate in order. It grows an extra input slot whenever you fill the last one.
Yes — workflows export and import as plain JSON files, so you can share a pipeline or keep versions in git. Ready-made templates give you running starts, and your very first workflow arrives pre-built (Input → Model → File) so you see the shape before building your own.
Intermediate results live in a scratch space; only what a File node claims is saved into your project folder, with sensible naming and collision handling. That keeps experiments cheap and your folder clean — and File nodes holding text are editable inline, right on the canvas.
Each Model node is billed like any other generation — by the platform, directly to your account, at that model's rates; local models cost nothing. Edit and Combine nodes are free: they run on your machine. There is no extra charge for the workflow engine itself.