File
SMF·LEONARDO-AI
Received on
31.07.2026
Reviewed on
28.09.2026
Exhibits annexed
3
Questions
4

SMF·LEONARDO-AI

Can a prompt replace Leonardo AI?

AI image generation — AI image and video generation

Not yet Verdict recorded on 28.09.2026 · Verified on 31.07.2026
Price
$12/moSource: leonardo.ai · Checked on July 31, 2026
Per year
$144
Build time
One sitting
Votes
0 votes
YesAlmostNot yet (checked)

Exhibit tracking slip

Exhibit A The prompt
Exhibit B What you lose
Exhibit C Why people still pay: frontier models, compute, and data
Exhibit Q Questions

Verdict

Training a small custom LoRA — a lightweight fine-tune — locally on a handful of your own images, then generating new images in that style, is a real weekend project using open tools already built for exactly this. What doesn't survive: Leonardo's large community library of pre-trained models, and managed training infrastructure that turns 'upload 10 photos' into a finished custom model in minutes without touching a training script.

Exhibit B — What you lose

Exhibit A — The prompt

Received on31.07.2026
Build a local custom-model training and generation tool, using LoRA fine-tuning — Leonardo's actual differentiator over a plain prompt box. Use an existing open training script (e.g. kohya_ss's LoRA trainer) run locally against a base checkpoint, SDXL or Flux, you already have. Build a simple wrapper UI: the user uploads 5-15 images of a subject or style, the wrapper kicks off the training script with sensible default hyperparameters — don't expose every training knob, that's not the point of a personal tool — and shows training progress. Once trained, let the user generate new images using that custom LoRA layered on the base checkpoint through your local ComfyUI or Automatic1111 instance, the same generation UI pattern as this catalogue's Ideogram entry. Save each trained LoRA with a name and thumbnail so multiple custom styles or subjects can be reused later. Do not build a community model-sharing library, managed cloud training, or content moderation — those are out of scope; this trains and stores models entirely on your own machine. No API key needed; a capable local GPU, or a rented one, is required for the training step specifically, which is more resource-intensive than generation alone.

Opening prefills the prompt — press enter to run it.

Exhibit B — What you lose

  • B.1 a large library of pre-trained community models
  • B.2 managed training infrastructure with no local GPU needed
  • B.3 instant model sharing within a community
  • B.4 moderation and content policy enforcement

Prior art

Exhibit C — Why people still pay: frontier models, compute, and data

Running a training script yourself works, but doing it without touching a command line, on infrastructure someone else keeps compatible with the latest base models, is the actual convenience being sold.

Questions

How long does training take?

Anywhere from 20 minutes to a couple of hours locally, depending on your GPU and image count — noticeably slower than Leonardo's managed training, which runs on dedicated infrastructure.

Can I share my trained model with the community, like on Leonardo?

Not in this build — there's no sharing platform. You'd need to manually upload the resulting LoRA file to a community site like Civitai yourself if you wanted that.

Do I need to understand machine learning to use this?

Not really — the wrapper hides most of the training script's complexity behind sensible defaults, though you'll need a capable GPU and some patience.

What does it cost to run?

Free if you own a capable GPU; renting one for the training step specifically costs more per hour than generation alone, since training is more resource-intensive.

Receipt

Already built this yourself?