Like many tech enthusiasts these days, I spend a fair amount of time bouncing between different AI tools.
My current daily drivers are ChatGPT, Grok, and Claude Pro.
Each one has its strengths, and honestly, we’re already at a point where choosing an AI model feels a bit like choosing the right Linux distribution for a specific workload. π
For coding and writing tasks, Claude has become one of my favorites. The quality is impressive, especially when working through technical problems, reviewing code, or discussing architecture decisions.
There is, however, one thing that keeps pulling me back to ChatGPT:
π¨ The Image Generation Dilemma
For blog posts, technical documentation, architecture diagrams, and the occasional nerdy illustration, ChatGPT consistently produces some really nice visuals.
Claude, at least for my use cases, doesn’t quite hit the same level when it comes to generating images for technical content.
The problem is that whenever I’m in “content creation mode,” I tend to generate a lot of images in a very short period of time.
And that’s exactly when I run into rate limits.
Could I simply throw more money at the problem?
Sure.
Do I want to?
Not necessarily. π
π₯οΈ The Hardware Is Already Here
While thinking about alternatives, I looked around my office and realized something:
I already have enough spare hardware sitting on shelves.
- A few unused PCs
- An ASUS GeForce Dual RTX 3050 8GB OC Edition
- Plenty of RAM
- More SSD storage than I probably need
- And thanks to my photovoltaic system, excess power during the day βοΈ
The GPU I plan to use for this experiment is an ASUS GeForce Dual RTX 3050 8GB OC Edition. While it’s certainly not a flagship AI accelerator, it should be more than capable of handling image generation workloads with modern models such as Flux Schnell. More importantly, it’s hardware I already own, which makes this a perfect low-cost homelab project.
At that point, the obvious homelab question appeared:
Why am I renting AI cycles when I could be running my own?
π The Plan: Local Image Generation
After a bit of research, I’ve become increasingly interested in a simple setup consisting of:
- Debian 13
- NVIDIA GPU
- ComfyUI
- Flux
For anyone not familiar with the stack:
- Flux is the actual image generation model.
- ComfyUI is the workflow-based frontend that allows you to build generation pipelines and interact with the model.
In simplified form:
Prompt β ComfyUI β Flux β NVIDIA GPU β Image
Simple. Elegant. Nerd-approved. π€
π§ Why This Sounds Fun
The funny thing is that image generation isn’t even the primary motivation.
What really interests me is gaining hands-on experience operating AI software locally.
As homelab enthusiasts, we already run things like:
- Proxmox
- Docker
- Grafana
- Prometheus
- Home Assistant
- NAS systems
- Kubernetes clusters that probably didn’t need to exist π
Adding local AI to that list feels like the next logical step.
It’s one thing to consume AI services.
It’s another thing entirely to deploy, maintain, optimize, and understand them yourself.
π Privacy Is a Nice Bonus
Besides the technical challenge, there’s another reason why I find local AI so interesting: privacy.
When the model runs on your own hardware, your prompts stay on your own hardware. No API calls, no cloud dependency, no wondering where your data ends up.
For homelab enthusiasts that’s already pretty cool. For businesses, it could be even more interesting. Companies dealing with sensitive customer data, internal documentation, source code, or compliance requirements may not always be comfortable sending everything to large cloud-based AI providers.
Local AI won’t replace ChatGPT, Claude, or Grok anytime soon, but for certain use cases it could become a very compelling alternativeβespecially when privacy, data security, and data sovereignty are more important than having access to the biggest model on the planet.
And honestly, being able to tell your AI to generate an image while the entire workflow stays inside your own rack is pretty satisfying. π
β‘ Performance Expectations
My hardware isn’t exactly a datacenter-grade GPU monster.
The system will be powered by an ASUS GeForce Dual RTX 3050 8GB OC Edition, which places it somewhere in the “enthusiast homelab” category rather than the “AI startup burning venture capital” category. π
Still, based on everything I’ve read so far, the card should be perfectly capable of running ComfyUI and Flux Schnell for blog illustrations and technical graphics.
| Resolution | Estimated Generation Time |
|---|---|
| 512 Γ 512 | 5β15 seconds |
| 768 Γ 768 | 10β30 seconds |
| 1024 Γ 1024 | 20β60 seconds |
| 1536 Γ 1536 | 60β120 seconds |
For my blog, I’ll probably generate most images at around 1024Γ1024 and resize them as needed. If the average generation time stays below one minute per image, I’ll be more than happy.
After all, I’m not running a commercial image factory. I just need high-quality visuals for technical articles, architecture diagrams, homelab documentation, and the occasional nerdy illustration.
πΈ Phase One: Images Only
For now, I want to keep things simple.
Phase one is focused entirely on image generation.
No agents.
No RAG.
No autonomous AI managing my homelab.
No “Skynet Beta” experiments.
Just:
ComfyUI + Flux
And see what happens.
π» Phase Two: A Local LLM
Once the image stack is stable, I’ll probably start experimenting with a local LLM as well.
My use cases are fairly straightforward:
- Answering simple questions
- Helping with Linux administration
- Generating Bash scripts
- Assisting with Docker configurations
- Small coding tasks
- General technical troubleshooting
I don’t need a trillion-parameter monster model for that.
Modern local models have become surprisingly capable, especially for practical infrastructure and scripting work.
π What’s Next?
Right now I’m still reading documentation, watching tutorials, and comparing different approaches.
The installation itself will probably happen within the next few days.
Once everything is running, I’ll publish a detailed write-up including:
- Hardware specifications
- Debian setup
- NVIDIA driver installation
- ComfyUI deployment
- Flux configuration
- First impressions
- Performance benchmarks
- Lessons learned
The initial goal is simply to create images locally. If that works as expected, the next step will be running a lightweight local LLM for everyday tasks such as answering questions, generating small Bash scripts, helping with Docker configurations, or supporting smaller coding projects.
And let’s face it: there is something deeply satisfying about generating blog images on a GPU that was originally bought for gaming and now spends its days helping power a tiny AI lab running on solar energy. π
If all goes well, this might become another permanent service in my homelab.
Because let’s be honest:
If you’ve already got spare hardware, excess solar power, and a tendency to self-host absolutely everything…
Running your own AI infrastructure starts to feel less like a project and more like an inevitability. π
Stay tuned. The first experiments are coming soon… π
