Show HN: A decent text-to-image model trained for ~$20K (Apache 2.0 Weights)
Posted by schopra909 2 days ago
My brother and I run a 2-person lab that trains our own generative video models from scratch. The ultimate goal is a set of creative tools that make it easier for anyone to make animation.
Video models today are too slow/expensive and lack sufficient controls. Creativity is an iterative process. You make, you tweak, you get better. In our opinion, they're not usable yet for storytelling.
When we set out to build Linum v3 (our next video model) earlier this year, the primary goal was to bring the cost envelope of inference down significantly. If our model is fast and cheap, it's the first step (of many) towards useful creative tools.
Typically, you see "latent diffusion models". A VAE (Variational Autoencoder) compresses the input data into a smaller "latent space" and the diffusion model learns how to generate within this subspace.
Over the past few months, we've been publishing our work on efficient pixel-space diffusion models. These throw away the VAE, having the diffusion model learn a latent-space optimized for its exact task.
This serves 3 purposes: 1) Simplify Architecture (no 2-stage model training) 2) Faster Convergence (11x faster convergence vs. our latent diffusion counterpart) 3) Cheaper Inference (4x more aggressive token reduction in attention context-windows, without significant loss in quality)
This past month we were pressure testing our latest architecture (Pyramid-JiT) by training a text-to-image model longer than the typical one-off experiment. Specifically, we trained it for ~$20K on 660M samples.
We were surprised by the quality of results, so we thought we'd release it as open weights for the community (Apache 2.0). The research itself is already public, on our website.
For us, it's a big stepping stone towards cheaper video models, since pretty much all video models start as image models. We like to say these models have to learn nouns before they learn verbs.
Comments
Comment by tensor 22 hours ago
Really happy to see a small shop like yours doing this sort of work!
Comment by blueblazin 14 hours ago
Comment by darkwater 10 hours ago
Comment by andai 11 hours ago
Are pictures easier than English, or did the methods advance so much?
Edit: I guess I should have said, are pictures plus English easier than English!
>The text representation comes from a frozen Qwen3.5-4B model, which we read at layers 7, 15 and 27 (its three full-attention layers). We concatenate and project these representations into the text refiner.
Still, as a layperson I would have expected text to be simpler than images, so I'm still amazed by this.
Comment by wongarsu 5 hours ago
Comment by andai 2 hours ago
I'm sure Moore's Law for GPUs helped a little, but I'm really curious about the savings on the methodology side. (The repo mentions "hyperparameters")
Comment by mkl 19 hours ago
Comment by fzysingularity 19 hours ago
Have you thought about setting up auto-research on this for smaller experiments? What's the minimum-viable budget for these types of workloads?
Comment by whythismatters 23 hours ago
Comment by Valk3_ 1 day ago
Also I'm a little intrigued on looking into efficiency techniques for video gen. What are current research directions in that field and promising directions you are particularly interested in? Any pointers for beginners?
Comment by yhjc2692 20 hours ago
CVPR 2026 paper list (after filtering on video generation) might be a good start - asking LLMs to take a look and filter relevant papers sound even better.
[1] https://arxiv.org/abs/2609.15810 [2] https://arxiv.org/abs/2602.13515 [3] https://arxiv.org/abs/2605.23381
Comment by Valk3_ 7 hours ago
Comment by jjcm 13 hours ago
Any chance you'll release your training recipe as well? I know the model code is public, but I'd love to dive into the full process.
Comment by yhjc2692 20 hours ago
Reminds me of this great paper where they trained a LLM that beats LLaMA2-13B from scratch with < $0.1M: https://arxiv.org/abs/2404.07413
Comment by Tarq0n 2 hours ago
Comment by jcattle 3 hours ago
Comment by gunalx 23 hours ago
Comment by dvh 23 hours ago
Comment by Robin_Message 21 hours ago
Comment by jcattle 3 hours ago
Comment by robotswantdata 21 hours ago
Comment by micw 21 hours ago
Comment by sebion7125 18 hours ago
Comment by pruthvishetty 8 hours ago
Comment by gigel82 1 day ago
If you swap the text encoder for something like T5-small or CLIP, this could be <2.5Gb at INT4; doable on a lot of machines.
Comment by apishare_api 17 hours ago
Comment by yajan2 5 hours ago
Comment by vancekai 6 hours ago
Comment by Atlas-Compiler 13 hours ago
Comment by looplilt 15 hours ago
Comment by Upbiddr 19 hours ago