I kept seeing the same question over and over:
"Can my laptop run this model?"
Not "is this model good?"
Not "how do I fine-tune it?"
Just: can I run it without setting my machine on fire?
So I built this:
It checks your hardware in the browser, pulls model info from Hugging Face, estimates memory needs, and gives you a simple answer: looks good, maybe tight, or probably not happening.
That was the idea anyway.
The problem
A lot of model pages tell you parameter count, context length, quantization options, maybe a few benchmark numbers.
What they do not tell normal people is:
"Will this run on my machine?"
And that is the part most people actually need first.
If you are not deep into local AI already, the jump from "7B model" to "works on my laptop" is weirdly annoying. You end up opening five tabs, reading Reddit threads, guessing VRAM requirements, and hoping someone with similar hardware already tried it.
I wanted something faster than that.
What the site does
The flow is simple:
- Detect your device hardware in the browser
- Fetch model metadata from Hugging Face
- Estimate VRAM and RAM requirements
- Tell you whether running it locally looks realistic
So instead of reading specs like you're decoding a secret message, you get a plain answer.
That was the goal: less "AI infrastructure puzzle", more "yes/no/maybe".
Why I made it in the browser
I like tools that do one job fast.
Also, hardware detection feels better when the site can just inspect what is already there instead of making users fill out a form like:
- GPU?
- VRAM?
- RAM?
- Browser?
- OS?
- Did you quantize it?
- Are you feeling lucky?
The browser already knows a surprising amount. Not everything, obviously, but enough to make a useful call.
That makes the tool feel instant, which matters a lot for something this small.
The annoying part
The hard part was not making a pretty page.
The hard part was making the answer useful without pretending to be magically exact.
Because this stuff is messy.
A model might technically run, but only if:
- you use a smaller quantized version
- your context length is low
- you are patient
- you do not mind your laptop sounding like it is about to leave Earth
So I did not want the site to act overconfident. "Yes" is easy to say. "Yes, but this is going to be tight" is more honest.
That honesty is the whole product.
What I like about it
My favorite part is that it saves people from fake optimism.
A lot of AI tools make everything sound possible. Then you try it locally and discover "possible" means "after 40 minutes of fighting memory errors."
This one tries to be more useful than exciting.
If your machine can handle it, great.
If not, I would rather tell you early.
Try it
- Live: canirunaimodel.vercel.app
- More of my projects: milliyin.dev/projects
If you like small practical AI tools, the projects page has the rest of the stuff I've been building too:
https://www.milliyin.dev/projects
If you test the site on your machine, I genuinely want to know where it gets it right and where it gets humbled.