What FlowArray is

FlowArray turns a one-off prompt into a repeatable, bulk operation. You describe the work once as a small chain of cards — take these products · generate a studio shot for each · review them — press Run, and it does the whole list at once instead of one at a time.

Three things make that more than a nice canvas.

It runs on your own keys, and it uses all of them

You bring the API keys. FlowArray groups them into a pool, and a run spreads its items across every key in that pool at the same time — so a batch of forty images finishes in roughly the time the slowest few take, not forty times one image. Add a second legitimate key (another project, another client's own key) and the same batch has more room to move.

This is capacity you already have, used properly. It is not a way around a provider's rate limits — see Pools and shared limits for the honest version, including why two keys do not always mean twice the throughput.

It knows what a rate limit is

Most tools discover a rate limit by failing. FlowArray tracks each key's limits centrally, holds items back before they turn into errors, cools a key down when a provider says to, and steps a spent key aside so the rest of the pool keeps working. A run finishes; it does not collapse.

It treats your money as real

Paid generation calls are not retried blindly. A call that cannot succeed twice is never sent twice. Every step's estimated cost is booked and visible per item, per run and per model, and you can set a daily spend limit that stops new steps rather than discovering the number on an invoice. Anything that runs unattended — a schedule, a webhook trigger — obeys the same ceilings.

What a workflow is made of

• Cards — a start, your items, one or more AI steps, and somewhere for results to land. Seventeen card types cover text, images, video, tool calls, branching and output. See the card reference.
• Items — the rows a run works through. One row per product, per SKU, per date window, per anything. Every item is tracked independently: one failure does not spoil the batch.
• Runs — the record of what happened, per item, with which key, how long it took and what it cost.

What it is not

• Not a chat window. It is built for the second, tenth and two-hundredth time you need the same job done.
• Not a model reseller. You pay your providers directly; FlowArray shows an estimate of what they will bill, never a charge of its own.
• Not a place your keys leak from. Credentials are encrypted at rest, masked in the interface, and never put into a prompt, a log, an export or a share.

Ready? Your first run takes about five minutes.