Build 112 is approved for external testing. Join the public TestFlight beta and run one real workflow now. Draw Things currently goes further on breadth, training and release cadence. LumenForge is for creators who value a calmer linear workspace over maximum feature density or a node graph.
One-glance comparison
| Decision | LumenForge | Adobe Firefly |
|---|---|---|
| Where generation runs | On a compatible Apple-silicon Mac | Adobe’s cloud service |
| Models | User-managed compatible local files, including documented FLUX, Stable Diffusion and video workflows | Managed Adobe and partner models selected by the service |
| Prompt and reference data path | Stays on the Mac during local generation | Must reach the service for cloud processing; check Adobe’s current policy and feature terms |
| Setup and hardware | Model files, storage and capable hardware are required; 16 GB unified memory is documented minimum | Browser-first access; cloud capacity and plan govern premium use |
| Usage economics | No per-generation cloud credit meter in the local loop; local power, storage and time remain your cost | Plans include monthly generative credits for premium capabilities; allocations reset per billing cycle |
| Collaboration and suite work | Individual desktop workspace | Stronger connected Adobe workflow and managed sharing context |
What local generation changes
With LumenForge, the creative loop — prompt, settings, compatible model files, output and workspace history — runs on the Mac. The benefit is control over the local environment and no requirement to upload a reference image for inference. The cost is real: model downloads can be large, compatibility is specific rather than universal, video is computationally demanding, and speed depends on the machine.
Once compatible model files are present, generation, history, workspaces and the core UI can run without cloud inference. TestFlight needs Apple network access, and the optional starter-model download contacts Hugging Face when you explicitly request it.
What a cloud creative suite changes
Firefly’s current plans combine standard generative image features with credit-governed premium features such as video, audio and partner-model output. Adobe describes monthly credit allocations and regional, plan and feature availability on its own plan pages. That managed model can be a better fit for teams that value browser access and broader suite integration over local-model management.
It is not accurate to assume every cloud feature has the same data policy or every local model has the same licence. Read the provider’s current terms, the particular feature documentation and the model’s licence before a sensitive or commercial project.
Creative control without an “uncensored” claim
Once compatible model files are present, generation, history, workspaces and the core UI can run without cloud inference. TestFlight needs Apple network access, and the optional starter-model download contacts Hugging Face when you explicitly request it.
“No hosted prompt policy” is an architectural observation, not an invitation to evade law, model licences, third-party rights or platform rules. This is the accurate, App Store-compatible way to describe local creative control.
Which workflow fits?
LumenForge may fit an individual creator with a capable Mac, an existing model library and a reason to keep visual iteration local. Firefly may fit a creator or team who wants rapid browser access, managed infrastructure and Adobe-connected tools. A base-model laptop, a deadline-sensitive video project or a team handoff can make the cloud option more practical; sensitive references or long local batches can make the local option more practical.
FAQ
Sources and update policy
Competitor and platform facts link to first-party documentation checked on 30 August 2026. Services change: verify the current regional product, policy and plan pages before deciding. Trademarks belong to their owners; no affiliation or endorsement is implied.