Skip to studio content
ProjectOpening projects…On this device

Drafts and selected assets stay in this browser. Export a copy before clearing site data. Imported projects never resume paid requests. Large provider-hosted media may need downloading separately before its link expires.

Project & assets ↗

One-pager · Studio operating decision

Build vs. buy

Every AI studio faces this stack decision three ways at once. The answer is knowing which layer each kind of work belongs on, and keeping the freedom to move as the market shifts monthly.

Put the assumptions on the table

What does an accepted asset cost?

Compare a suite workflow with an API workflow, including the attempts that do not make the cut. Defaults are illustrative planning inputs, not vendor quotes or measured savings.

Seats, generation and maintenance assumptions

Monthly scenario · 200.0 attempts

Suite workflow

$10.90/ accepted asset

$1,090.00 per month

API workflow

$14.00/ accepted asset

$1,400.00 per month

Under these assumptions, the suite workflow costs less. Review labour alone accounts for $800.00 in either workflow.

API cost crosses below suite cost at approximately 876 accepted assets per month, if these per-attempt assumptions remain unchanged.

Both scenarios use the same review effort. Enter incremental suite credit cost after included allowances. Taxes, negotiated discounts, storage and external finishing are not automatically included.

The call

Buy

Suites for exploration

A few seats so creatives touch every new model the week it ships. R&D spend, not production infrastructure.

Build

APIs for production

This studio uses Gemini and Recraft directly, plus fal for additional image, video and audio routes. Local browser tools handle package previews and project organization.

Neither, forever

Re-evaluate monthly

Keep source assets and decisions portable. A new model still needs an adapter, capability validation and a test against the work.

The stack

01Creative suitesHiggsfield · Freepik · Krea$15–150 / seat / moExploration
02API aggregatorsfal.ai · ReplicateUsage-pricedProduction
03Direct model APIsGemini · Black Forest Labs · RunwayUsage-priced, negotiableAnchor

Each layer sits closer to the model than the one above it and gives up convenience for control as you descend.

Head to head

CriterionCreative suitesAPI aggregatorsDirect APIs
Pricing modelPer seat + creditsPer generation✦ edgePer generation, negotiable at scale
Access to new modelsDay one, across vendors✦ edgeDays to weeksDay one, that vendor only
Workflow integrationVaries by suite and planFull API✦ edgeFull API
Rights & indemnityVendor terms, variesPassed through from the model ownerFirst-party, negotiable✦ edge
Cost at high volumeBreaks downLinear and predictableLinear, improves with commitment✦ edge
Switching costExport work, review terms, cancel seatsShared transport; endpoint schemas still differ✦ edgePer-vendor adapters and validation
Where it breaksVolume scalesYou need a first-party SLA✦ edgeThe leaderboard flips

“Edge” marks the layer that wins that row outright. No layer wins across the board.

The layers in detail

01

Creative suites

Higgsfield · Freepik · Krea

Subscription UIs wrapping 15+ third-party models. They still own no frontier models, but calling them a convenience layer is now only half right: the leaders ship into the tools a team already uses. Higgsfield has a Blender add-on that prompts an editable blockout and animates a camera rig, an MCP bridge so an agent can build in the open scene, plus Premiere, After Effects and Figma plugins and a REST API of its own. What you are buying is the integration, not the model.

Wins when

  • Creatives explore and iterate hands-on, daily
  • Day-one access to every new model
  • The tool plugs into an existing craft app and saves real hours there
  • Small team, modest volume

Fails when

  • At scale, per-seat fees plus credits add up
  • You need workflow integration, QA gates, audit trails
  • The headline unlimited plan does not extend to the API or MCP, so an automated pipeline is back on credits
  • Rights and data-governance terms need enterprise review
02

API aggregators

fal.ai · Replicate

One key, ~1,000 curated production endpoints (fal) or 50k+ community models (Replicate). The pragmatic middle: model diversity without one integration per vendor.

Wins when

  • Repeatable versioning, adaptation and batch pipelines
  • You swap models often as leaders change
  • Cost maps linearly to output

Fails when

  • You need a first-party enterprise contract and SLA
  • A model exists only on its vendor's own API
03

Direct model APIs

Gemini · Black Forest Labs · Runway

First-party access: newest capabilities first, best rate limits, enterprise terms negotiated with the model owner. Gemini is the standout for retail, with reasoning, vision, stills and video behind one key.

Wins when

  • The workload anchors on one vendor's ecosystem
  • Legal needs first-party rights and indemnity
  • Scale justifies negotiated pricing

Fails when

  • You over-commit and the leaderboard flips (see Sora 2's API sunset)
  • Every extra vendor is another integration to maintain

Own the workflow.
Rent the models.

Workflows, prompt systems, quality gates and brand knowledge compound. Models are commodities that change quarterly. Build the first, rent the second, and never let the second dictate the first.

Three questions that settle it

Who indemnifies the output?
Rights and data-governance answers only exist at the suite-contract or first-party-API level. If a brand ships it, someone has to stand behind it.
What does this cost at 500 assets a week?
Per-seat suites are flat until volume turns credits into the real bill. APIs are linear from day one, and model routing (draft cheap, finish premium) is where the savings actually live.
Could we leave in a week?
The market leader has changed roughly quarterly since 2024. Any layer you can't exit in a week is a liability, not a partnership.

What this demo actually runs on

Gemini direct for reasoning, vision, Nano Banana stills and Veo video; fal.ai for additional stills, Kling, Seedance, Runway and ElevenLabs music, voice and effects; Recraft directly for its image and finishing tools. Model configuration is centralized, while provider-specific adapters validate different payloads. Three.js, Canvas and browser storage support the local package, rehearsal and project workflows.

See the routing table →