Sunith to Truevibecoder: My JioBase Moment

I did not start Truevibecoder after JioBase.

I started it before that, with the normal excitement of wanting to create content. I made an account with the truevibecoder username. I posted some videos. Maybe around 10 videos. I had around 300 followers.

But the process was heavy.

Shooting was one part. Editing was another. Scripting took time. Then came cuts, captions, overlays, music, exports, and all the small decisions that make content creation feel like a full production pipeline. I wanted to post more, but the editing friction was too high.

So the account existed. The intent was there. But I was not posting at the speed I wanted.

Then JioBase happened.

Before JioBase, content felt too expensive

The biggest problem was not ideas. I had things to share.

I had already built multiple projects before JioBase. Some of them reached their first users. Some did not go far. Some taught me what users actually care about. I was already building, breaking, learning, and moving to the next thing.

The problem was turning that journey into content.

I used to think each video needed to be properly scripted and edited. That made every post feel expensive. Even when the idea was simple, the process around it made me delay.

That is a bad place for a creator to be in. When every post feels like a production, you stop posting the small honest things that people actually connect with.

The problem that made JioBase necessary

On February 24, 2026, one of my Supabase-powered apps started failing in production. The dashboard still worked. The marketing site still opened. But the actual API endpoints that apps depend on were timing out on major Indian networks.

I wrote the detailed technical version in my Medium guide, Supabase Blocked in India: The Complete Guide to Fixing Your App. The short version is simple: many developers were not dealing with a normal bug. Their apps were breaking because access to Supabase API domains was failing on ISP networks.

That issue affected real product surfaces:

• REST requests failed.
• Auth stopped working correctly.
• Storage uploads or downloads broke.
• Edge Functions became unreliable.
• Realtime WebSockets did not connect.
• Some users saw a working app while others saw a broken one.

Changing DNS was not enough. Asking users to use a VPN was not a product answer. Moving every app away from Supabase was too much. Self-hosting Supabase was not realistic for many small teams.

The practical answer was a proxy.

My JioBase moment

I built the first version of JioBase because I needed my own app to work again.

It became my JioBase moment, one of those life-changing builder moments where a production problem turns into something much bigger than the original bug. At first, I was solving my own issue. Very quickly, I realized the same fix could help many other developers who were stuck in the same situation.

The idea was direct: route Supabase requests through a Cloudflare Workers based proxy, give developers a replacement URL, and make the fix simple enough that they could patch a broken app quickly.

JioBase became that temporary bridge:

• one URL change for many apps
• support for REST, Auth, Storage, Edge Functions, and Realtime
• no need for every developer to set up their own proxy immediately
• open-source code for people who wanted to inspect or self-host it

The managed service was not meant to be a forever platform. After the ISP issue was resolved, JioBase recommended moving apps back to direct Supabase usage. The goal was not lock-in. The goal was to solve the urgent problem in the smallest useful way.

The source code also stayed public on GitHub, because trust matters when a tool touches developer infrastructure.

JioBase changed how I posted

After JioBase, I stopped treating content like a polished production.

I had something real to talk about. So I just started talking.

No heavy editing. No perfect script. Mostly raw videos. Sometimes background music. Sometimes a simple image overlay. That was enough.

That small change removed the biggest friction: editing.

And once the friction was gone, I could post more. I could share the story while it was still happening. I could explain what broke, what I built, what people were asking, and what I was learning.

That helped the content reach more people because it felt alive. It was not a polished summary after everything was over. It was part of the build journey.

From 300 followers to 10k in one week

Before this phase, the account had around 300 followers.

After I started posting more raw JioBase and builder content, Instagram started pushing the videos to more people. The account reached 10k followers within a week, from around 300 to 10k.

And it is still going up.

That growth did not happen because I suddenly became better at editing. It happened because I removed the editing bottleneck and shared something people cared about.

The lesson was very clear to me: consistency becomes easier when the format is lighter.

For me, raw videos worked because the story was real. The product was real. The problem was real. People could feel that.

People started recognizing me

This was the first time I felt the online work turn into offline recognition.

People started recognizing me at events. Some knew me from the videos. Some knew me from JioBase. Some knew the truevibecoder handle before they knew my full name.

Maybe that makes me an influencer now. I do not mean that in a big celebrity way. Maybe micro influencer. Maybe nano influencer. But yes, people started recognizing me from the crowd, and that is new for me.

The important part is not the label. The important part is that the work created trust.

People did not follow only because I posted videos. They followed because I was building, sharing, helping, and staying visible while the work was happening.

Helping other builders get early traction

One of the best parts of this attention is that I can now support other builders.

People started getting inspired and building their own products. Some of them reached out. Some needed feedback. Some needed an initial push. I helped where I could, because I know how hard the first users are.

When I started Devb.io, I learned the pain of initial traction and marketing. Building the product is one hard part. Getting the first real users is another hard part. Many builders underestimate that second part.

So if I can help someone get a small push, I love doing that.

It is not only about posting my own wins. It is about creating a small builder loop: build, share, help others, learn from them, and build again.

JioBase was not my first product

JioBase got attention, but it was not my first product.

I had built multiple projects before it. Some reached first users. Some were experiments. Some failed quietly. Some taught me what to do next. That matters because a JioBase moment usually does not come from nowhere.

It comes after many small attempts.

I never quit building. Even now, I will keep working on projects I love. Some will become useful. Some will not. That is fine. The point is to stay in motion long enough for one project to meet the right problem at the right time.

JioBase was one of those projects.

Start with small problems

Do not wait for a world-changing idea.

Start with a small problem. Find a solution. Ship it. Talk to users. If it is not working, move on. If it has a signal, go deeper. Pivot if you need to. Keep talking to users.

You can see the same pattern in Kerala’s Undo Universe. Most of those projects are not trying to solve abstract billion-dollar problems. They are solving simple local problems:

• Is gas available?
• Is current gone?
• Is there a pothole here?
• Where can I find something near me?

Small problems are not small when the pain is real.

That is the builder lesson I keep coming back to. You do not need permission to start. You do not need a perfect idea. You do not need a perfect content setup. Start building. Start sharing. Reduce the friction. Learn in public.

Your JioBase moment may be one product away.

FAQ

Who is Truevibecoder?

Truevibecoder is Sunith VS, a product engineer from Kerala who builds developer tools and shares content about vibe coding, AI-assisted engineering, and product building.

Did JioBase start the Truevibecoder account?

No. I started the truevibecoder account before JioBase and posted some videos, but editing and scripting made it hard to post consistently. JioBase changed the way I created content because it gave me a real story to share in a simpler raw format.

What was your JioBase moment?

My JioBase moment was when a production problem in my own Supabase app became a tool that helped other developers. It changed both my product journey and my content journey.

What should builders learn from this story?

Start with small real problems. Ship a useful solution. Talk to users. Share the process. If it does not work, move on or pivot. If it works, go deeper. Your JioBase moment may be one product away.