AINave

The OS for AI Builders

[Ramit Koul @ramitkoul]

🚀 Day 74 of Building in Public

🔥 Going live with a custom-made lightweight blog platform.

- I will be using this to post weekly newsletters and other thoughts for AI builders and enthusiasts.

- Initially, I thought of using any existing platform like ghost but I feel this was a lot easier to setup without any extra cost involved since I already had the solid base setup in my codebase for my usecase.

#buildinpublic

[Ramit Koul @ramitkoul]

🚀 Day 73 of Building in Public

Tech News v3 is live now on https://t.co/Qp5gDY0uNm - The Regular Tech News from the perspective of AI founders and builders.

- enabled SSR in all relevant public pages.
- built a keyword research agent for writing better SEO articles.

Next items:

- A blog platform for articles and newsletters.
- Product testimonials collector

#buildinpublic

[Ramit Koul @ramitkoul]

Hey everyone!

it's been too long since I posted anything here (almost 18 days)

So, here's the update:

1. Launched a niche job board on @huntyourtribe. Directly getting jobs from company career pages. These are handpicked startups and companies which usually don't post jobs on linkedin or indeed. Also got a good amount of feedback on reddit and various communities.

2. The new Tech News Engine on @ainavehq was broken. On it, so will be fixed by tmr hopefully.

3. Got busy with few personal errands which were important to resolve.

So, now, will be resuming the build in public journey again from tmr onwards.

Happy building :)

#buildinpublic

links:
https://t.co/r0oP0KjTfF
https://t.co/e9iRjYLpsW

[Ramit Koul @ramitkoul]

just watched this 33 minute video and feels like it ended too soon.

kudos to @marclou for making such an engaging video and being a great inspiration to everyone who is building here.

https://t.co/9FTJrXTfEW

[Ramit Koul @ramitkoul]

🚀 Day 71 of Building in Public

New version of tech news is almost ready to ship.

> This time, it's all about getting more signal from the noise.

> All the news articles will be researched and written from the builders, product founders, solopreneur etc's perspective only.

#buildinpublic

[Ramit Koul @ramitkoul]

I architected and discussed everything with codex and now it is implementing my plan with /goal

We are in a new paradigm now.

for me, coding has transitioned like this:

> 2008-09: chatrooms and coding forum discussions and PHP scripts exploration

> 2010s: building multiple websites with LAMP stack.

> 2014-16: exploring github and python projects

> 2016-20: running projects for my college to solve management problems and winning multiple hackathons with teams. explored a bunch of technologies and frameworks like node, django, flask, postgres, mongodb, redis, graphql, react, rails and what not.

> 2021-24: worked in a high growth startup. worked mostly on Rails + MySQL and learned best industry practices while coding.

> 2024: started my founder journey and was developing everything by hand till early this year

now, i hardly write code anymore and just break down problems into smaller problems, devise solutions and architect the whole systems. then, AI does the translation to the code. and then I review and refine the implementation.

how has been your journey so far?

[Ramit Koul @ramitkoul]

🚀 Day 70 of Building in Public

✅ Built a simple and yet powerful SEO keyword research agent.

This will be powering everything to write better content aligned with SEO/GEO with proper citations.

Starting with Tech News v3 now.

#buildinpublic

[Ramit Koul @ramitkoul]

🚀 Day 69 of Building in Public

yesterday, analysed few problems in current approach.

- earlier, the tech news articles were getting indexed and sending traffic from bing even while explicitly having noindex tag in pages.
- google is still not indexing any page other than homepage :(
- but, i felt page quality was bland and not good enough.
- now, in this revamp, the agent will first research with the context, build SEO terms and faqs and then write the articles.
- i will also change the base model from gpt-4o-mini to deepseek v4 flash.

will be sharing here once done.

#buildinpublic

[Ramit Koul @ramitkoul]

🚀 Day 68 of Building in Public

Sometimes, unexpected things happens in life which creates more clarity than ever. Last week was all about that.

Last Week Summary:

1. Earned $135 from ImgNave and AINave combined last week.
2. Tried to build BIP feed. Only issue was nitter scraping had a lot of issues. so, paused this for now.
3. Faced some personal problems which took a lot of time to resolve.
4. Got inactive here on X. Earlier, was more focused on number of replies (hit 300+/day mark). But, that is exhausting. will mostly engage with my following tab now.

Next items for this week:

1. Tech News fixes (inactive from last 1 month)
2. Build reviews in AINave

#buildinpublic

[Ramit Koul @ramitkoul]

🚀 Day 67 of Building in Public

not a big product update today, but an honest one.

sometimes unexpected things happen in life and you lose focus for a bit.

it happens. we are humans first.

the past 2 days, I got caught up with some personal things and went inactive here.

not ideal, but also not the end of the world.

what matters is coming back, picking things from where you left, and moving again.

back now.

resuming the build in public feed from where I left it.

slowly getting back into the flow.

#buildinpublic

[Ramit Koul @ramitkoul]

ImgNave is now live on Orynth 🚀

Really liking what the Orynth team is building here.
Fast setup, real attention, real community energy around products.

If you are tired of paying unpredictable money to Vercel/Netlify etc for using image transformations on your Next.js app, you should check out ImgNave

- No image transformations costs (unlimited transformations)
- $5/month fixed rate which includes 10GB bandwidth/month
- $0.07 per GB of bandwidth usage after 10GB
- Ultrafast CDN distributed accross the world powered by @BunnyCDN

Curious to see where this goes over the next few weeks as I start pushing distribution harder.

ca: HHyN7koHMZxNZPHxZ8Yv587UjdMromUsxSfCUo9gpory

[Ramit Koul @ramitkoul]

🔥 shipping soon: Build in Public feed.

i will be adding some of my favorite builders here from the community to this universal feed.

idea:
- post regularly in different platforms (for now only X supported) related to build in public.
- will pick best post of each builder everyday and add it to the timeline (if it follows the current buildinpublic community guidelines)
- get a clean and one timeline of high quality builders building in public.
- gives boost and visibility to builders irrespective of the platform they are using.

anyone wants to join this feed, DM me or join the waitlist: https://t.co/mUlJnZCOmL

#buildinpublic

[Ramit Koul @ramitkoul]

Solo builders don’t lose because they can’t build.

They lose because everything after building is broken.

If you have little to no distribution, the whole product journey feels like patchwork.

Build in public?
Getting harder. X communities are going away and most builders don’t already have a big audience.

Product Hunt?
Very hard to crack unless you already have distribution, a network, or VC funding-backed momentum.

Customer journey?
Even worse.

Featurebase: what users want
Linear/Jira: what the team builds
Changelog: what shipped
Senja: what happy users say later
Marketing site: where proof is displayed

You pay for all of this.

And still, the loop is not complete.

One simple workflow should look like this:

1. mark a major feature request as shipped
2. notify everyone who asked for it
3. ask them how it’s working
4. collect video/text feedback
5. turn good responses into proof
6. show that proof where future users can see it

This should not need 5 different tools and manual stitching.

That’s the direction I’m trying to take AINave in.

An OS for AI builders.

Starting small:
a build-in-public timeline where builders can keep posting on X, but get extra visibility from people actually interested in product progress.

Basically, you don’t leave X.
You just get another surface where your building journey can be discovered.

If this sounds useful, I’m opening the early waitlist.

link in first reply 👇

[Ramit Koul @ramitkoul]

Late night build in public update.

✅ Done with the DB schema for the v0 version.

Not the most exciting screenshot, but this is the part where the product starts becoming real.

💡 Small tip / Framework:

=> Ask Codex to turn your discussion/plan into a HTML page.
=> it gets way easier to understand, review, and collaborate with.

my flow today:
- discuss the plan
- convert it into HTML
- review it visually
- lock the DB schema

it helped me catch:
- missing tables
- weak relations
- confusing fields
- removing over optimisations
- gaps before code

Small result: the db schema is much clearer and scalable before writing a single line of code.

do you also turn plans into something visual before building?
or do you keep everything in docs/text?

will continue tomorrow.

now time for sleep.
Good Night everyone 😴

#buildinpublic

[Ramit Koul @ramitkoul]

most builders already have social proof.
it’s just buried everywhere.

🚀 Day 64 of Building in Public

product reviews are cooking up for AINave.

1 place to collect, manage, and show reviews from:
- X
- LinkedIn
- Product Hunt
- Reddit
- Slack

small workflow I’m building:
- capture review
- tag product
- reuse as proof
- show it on the product page

> so basically, something like Senja, but only for products.
> at a much cheaper price, and inside one AINave subscription.

this is just one solution.
more useful product-growth solutions will keep getting bundled in over time.

will share the demo video soon.

where does your best product feedback usually get lost?
X, LinkedIn, Product Hunt, Reddit, Slack, or somewhere else?

things are accelerating fast now 🔥

#buildinpublic

[Ramit Koul @ramitkoul]

All this for approx $150 worth of credits (actual cost = $20 subscription) and a few hours with /goal.

Codex is awesome!! 🔥

Skills used
- Karpathy Guidelines
- Next Best Practices

Thank you Codex team! @thsottiaux @sama

[Ramit Koul @ramitkoul]

🚀 Day 63 of Building in Public

AINave got a serious upgrade today.

✅ Codex, with some help from me, migrated the whole codebase from:

JavaScript → TypeScript
Next.js 14 → Next.js 16
Pages Router → App Router

and honestly, this is exactly where AI agents are starting to feel almost perfect.

not in a "do everything blindly" way.

but when paired with /goal, Karpathy Guidelines, and the Next.js MCP server, it actually sticks to the standards pretty well.

now I’m working on the new products page and fixing bugs that were pending for a long time.

one step closer to making AINave cleaner and stronger 🚀

#buildinpublic

[Ramit Koul @ramitkoul]

what’s the 2026 version of building websites in the 90s, mobile apps in 2010s, SaaS in the cloud era?

not the obvious AI wrapper stuff.

what will look completely obvious in hindsight but is still mostly unbuilt today?

[Ramit Koul @ramitkoul]

🚀 Day 62 of Building in Public

started marketing ImgNave on reddit.

very subtly. no spamming.
just trying to find places where the problem is actually relevant.

idk how, but my reddit karma is growing way faster now.

2 days ago: 138
today: 162

and 1 month ago, it was literally 4 🥹

still no new customer onboarded yet, but that’s fine.

distribution is not a one-day thing.
will keep doing this daily and see what compounds.

on the AINave side:
started working on the product page revamp + some new things.

slowly moving both products forward 🔥

#buildinpublic

[Ramit Koul @ramitkoul]

@buildinpublic Recently shipped https://t.co/Utm9ktnUGU - A cheaper and reliable alternative to Vercel Image Optimisation for Next.js

Now, will be distributing this