FLORA at $18, $50 or $200 a seat vs Sume's flat $40 and $120

FLORA prices by seat: its pricing page lists Starter at $18 per seat, Pro at $50 and Max at $200, with Enterprise custom from 9 seats. Sume prices the plan, not the person: Pro is $40 a month and Startup, the shared team workspace, is $120 a month, with generation billed at each model's published USD rate. For a team of three the listed plan fees are $54 on FLORA Starter against $120 on Sume Startup, but the two bills are not the same thing, as the sections below show.

This post compares only what both vendors print on their plan pages. It does not compare output quality, and it does not price a month of generation, because FLORA does not list the size of its pool.

What does FLORA charge per seat?

FLORA's page lists a Free plan for one seat, with 3 active projects and up to 17 free generations on text and image models. Starter ($18 per seat) adds unlimited projects, all models, API and MCP access and real-time collaboration. Pro ($50 per seat) adds shared team assets, shared elements, per-member usage caps and usage analytics. Max ($200 per seat) adds three custom voices per organization.

The page also lists a 10% discount for quarterly billing and 20% for annual billing. Usage is described as a shared dollar pool that scales with your seats, metered at published model rates. The page does not say how many dollars each seat adds to the pool.

What does Sume charge instead?

Sume's plan grid is flat per workspace. Pro is $40 a month with 100+ video models, full Sume Agent access, API, CLI and MCP access, a team wallet and 4 concurrent jobs. Startup is $120 a month and adds a shared team workspace with 8 concurrent jobs. Scale is $400 with 20 concurrent jobs and priority support. Free is image generation only with 1 concurrent job.

Usage is billed separately at each model's published USD rate, funded from a wallet you top up in amounts from $10 to $1000. The API pricing page lists the rates, for example text to speech at $0.0475 per 1,000 characters and timeline render at $0.10 per output minute.

What do the plan fees add up to for 3 and 7 seats?

The table multiplies FLORA's listed monthly seat price by the team size and sets it beside Sume's flat plans. It is the subscription line only. On FLORA part of that money funds the shared pool, while on Sume generation is a separate wallet charge.

Where does the comparison break down?

Three things keep this from being a clean price ranking. First, FLORA's pool size is unlisted, so a seat price cannot be turned into a cost per clip. Second, Sume's Pro and Startup pages list concurrency (4 and 8 jobs) rather than seats, so the seat count a Startup workspace allows is not on the pricing page. Third, FLORA's Starter plan already includes API and MCP access, while on Sume that starts at Pro, so a developer-only team may need nothing above $40.

A practical way to decide: count how many people need their own logged-in seat, then estimate your monthly generation spend from the Sume API rate table. If the seat count is the main driver, FLORA's per-seat model scales with headcount. If the job count is the main driver, Sume's concurrency tiers are the number to watch.

How do I check Sume's numbers for my own mix?

Open the API pricing page for the models you use, multiply by your expected seconds, images or characters, and add the plan fee. The same balance and usage figures are available from the API at GET /v1/balance and GET /v1/usage, so you can watch real spend after a first week rather than trusting an estimate.