krea

# Krea Krea ships two completely separate things under one brand, and picking the wrong one wastes the job. **The fork, decide it first.** - **Hosted API.** Nodes `Krea2ImageNode` and `Krea2StyleReferenceNode`, category `partner/image/Krea`, billed per image, capped at **1K output**, and the only path that reads a **Krea moodboard** from the website. - **Open weights.** Krea 2 Raw and Turbo run locally on core nodes, free, any resolution, no moodboard. **Who owns what, so you open one file, not three.** THIS file owns the fork, the hosted graph, the FLUX.1 Krea Dev graph and the ecosystem map. `reference.md` next to it owns full node I/O, the price matrix, weight files with measured sizes, and the custom-node packs. **The kit's `MODELS.md` already owns the local Krea 2 graph in depth** (Raw vs Turbo settings, the `qwen3vl_4b` encoder and its `krea2` CLIP type, the Ostris edit method, the style-reference LoRA on core nodes, the nine official style LoRAs, the abliterated-encoder swap, licence). Do not restate it here, route to it. ## Which Krea for which job | Job | Path | Why this one | |---|---|---| | A look you already built on krea.ai as a **moodboard** | hosted `Krea2ImageNode` | moodboard UUIDs exist only on their service | | Style from 1 to 10 **reference images**, no local weights | hosted, chain `Krea2StyleReferenceNode` | up to 10 refs, each with its own strength | | Same style locally, one reference | local Krea 2 Turbo + `krea2_style_reference` LoRA | free, n...