The lesson
Open a competitor comparison by saying plainly when the rival is the better choice, so your own claims read as a fair verdict.
The hero, tagged "The Runway alternative," reads "Krea vs Runway" with "Generate with Runway Gen-4.5 and every other frontier video model, then finish the work in the same studio," two buttons, and a logo row under "Krea powers 40M+ creatives, enterprises, and everyday people." Next, "Krea or Runway? Both are excellent" splits into "Choose Krea when you" and "Choose Runway when you," and the Runway column credits Aleph 2.0, Act-Two and Ruby. A five-row "Key differences" table and a "Made in Krea" image grid follow, then three "Why creators choose Krea" feature blocks and a longer "Full comparison" table. The page ends with a teams section that includes a Superside quote, a developer section showing an MCP config snippet, related links, and FAQs.
Don't copy Krea's specific claims about Runway's plans, API or training features unless you can verify the competitor's current offer. Keep the order: an honest when-to-choose-each split, a short table, proof, then a full table and sections for each buyer type.
Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.