Menu

Post image 1
Post image 2
Post image 3
1 / 3
0

Weekend Experiment: Free Qwen as a Personal API. Here Is What Actually Happened.

DEV Community·Mikhail Sapunov·23 days ago
#Yt6JV4Bv
#pitfall#webdev#python#fullscreen#kaggle#qwen
Reading 0:00
15s threshold

Found a cool service - Kaggle . Gives 30 free GPU hours per week. And I had this idea: what if I run Qwen3-8B there and expose it through an API on Cloudflare Workers? Honestly not sure what this is useful for. Just wanted to know if I could pull it off. Planned to finish in a couple of hours. Finished over the weekend. So Why Bother? As I was figuring things out, I realized this could work as a free replacement for a paid AI API - for example in R-Searcher , my Chrome extension for reading articles. Or just as a personal AI backend with no subscription and no token limits. But honestly - the idea came first, the reason came later. Not the other way around. So the task: a client sends a request, Qwen on Kaggle processes it, the response comes back. For free. The first problem showed up five minutes in. The Problem: Kaggle Has No Inbound Traffic Kaggle is a Jupyter notebook on a cloud GPU. No public IP. No incoming connections. You can't just spin up a Flask server and hand out a URL. First idea: ngrok.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More