Aexo Positioning Intelligence
Independent founder review for SaaS positioning, onboarding,
Most founders aren't ignoring problems.
They're too close to see them.
A pattern keeps showing up:
Teams know their product too well
Buyers don't
Important questions go unanswered
Trust gaps become invisible internally
One example:
A company spends months building a powerful feature.
The homepage mentions it.
But never explains why a buyer should care.
Internally it feels obvious.
Externally it feels confusing.
The product isn't weak.
The perspective is missing.
That's the idea behind Aexo.
Not another SEO audit.
Not another analytics dashboard.
Just an independent founder review focused on:
positioning
onboarding
trust signals
documentation
buyer perception
I've started publishing some public findings from real SaaS products.
Curious:
What's the biggest blind spot you've discovered in your own product after talking to users?
Hello IndieHackers 👋
I'm Dinesh, a developer who got tired of one specific frustration:
Every time I needed a free or open-source tool, I'd spend 2-3 hours jumping between GitHub lists, Reddit threads, and random blog posts — only to forget where I found something useful a week later.
There was no single place that felt like home for this kind of discovery. So I built one.
🌧️ What is The Cloud Rain?
It's a free, open-source platform where developers can discover:
- Hidden open-source tools that most people haven't heard of
- Free developer resources, UI kits, and utilities
- Curated articles I write personally about each tool — not just a link dump
The "mystery box" twist: instead of showing everything at once, there's a discovery layer. You unlock tools and hidden content for free just by engaging — no subscriptions, no credit card, no ads.
Everything is self-hosted and open source. The repo is public on GitHub.
📰 The Article Museum
This is the part I'm most proud of.
I write detailed articles about tools most developers have never heard of — things like:
- Uptime Kuma (the self-hosted monitoring tool that replaces paid services)
- Litestream (SQLite backups that feel like magic)
- Plausible (privacy-first analytics that doesn't need a cookie banner)
- ZincSearch (Elasticsearch alternative that runs on a Raspberry Pi)
These aren't SEO-stuffed listicles. Each article is a proper deep dive into why the tool exists, who it's for, and when you'd actually reach for it.
🛠️ What I built it with
- Next.js 14 App Router (fully serverless)
- Supabase (database + auth)
- Vercel (deployment)
- GitHub Actions (automated scraper that keeps listings fresh)
No separate backend. One core folder. Deployed in minutes.
😅 Honest status
Launched 2 weeks ago. Zero marketing budget. Traffic is basically just bots and me refreshing the page.
I've fixed security issues (RLS policies, server-side rendering for SEO), cleaned up the sitemap, and made it properly crawlable. The technical foundation is solid now.
What I genuinely need: real developers to tell me what's missing, what's confusing, or what would make them actually bookmark this.
If you've ever wasted an afternoon trying to find a free alternative to some expensive SaaS — this is built for you.
Would love brutal honest feedback. What's your first impression?
#open-source, #developer-tools,#side-project,
#building-in-public, #free-tools
Title: Why I’m building a "Museum" for 1MB tools in a 1GB world
Body:
The modern web is suffering from "Digital Obesity."
We’ve reached a point where a simple "Hello World" app requires a 500MB Docker image and consumes 200MB of RAM. As a student developer, I found myself increasingly frustrated with this bloat. I missed the era where tools were fast, focused, and followed the Unix philosophy: Do one thing, and do it well.
So, I decided to build The Cloud Rain.
It’s not just a directory. It’s a curated "Article Museum" where I document hidden-gem open-source tools that are written in C, Go, or Rust—tools that solve massive problems with almost zero overhead.
What I’m showcasing in the Museum:
Iodine: Bypassing firewalls via DNS tunneling (Pure engineering magic from 2004).
ZincSearch: A Go-based alternative to Elasticsearch that runs on a fraction of the RAM.
Fossil: An SCM that is a single SQLite file. No complexity, just pure efficiency.
The Mission: I’ve stripped away all ads and tracking from the platform. I want this to be a sanctuary for engineers who are tired of the hype and want to rediscover the beauty of "Lean Code."
I’m looking for two things from this community:
Feedback: Is the "Future-Minimalist" aesthetic of the site working, or is it too much?
Suggestions: What are your favorite "hidden gems"? I want to document tools that deserve more than just a GitHub star.
Check out the Museum: https://thecloudrain.site
Let’s stop building bloated software and start appreciating the art of efficiency again.
-
1
Subject: Quick question — how do you manage context across AI tools?
Hey,,
I'm researching a problem I'm facing myself: juggling multiple AI tools
(Claude, ChatGPT, Perplexity) for my startup and losing context every
time I switch between them I have to tell every ai every time.
Quick question: Do you find yourself copy-pasting context between different.??
AI tools during your workday? Or does each AI tool live in its own bubble?
Would love 10 minutes of your time if you're open to it. Not selling
anything — just trying to understand how other founders handle this.
Best,
[Kanishk Wankhede]
-
1
Hey Kanishk, thanks for checking out the post!
To answer your question: Yes, I face this 'Context Fragmentation' daily. Since I work with very specific minimalist tools (Go/Rust/C), I often have to feed the same documentation to Claude or ChatGPT to get accurate results. Each AI definitely lives in its own bubble right now.
I usually solve this by maintaining Markdown 'Context Files' that I quickly drop into whichever AI I'm using. It’s manual, but it keeps things lean.
Would love to hear if you’ve found a more 'minimalist' way to handle this without adding more bloat to the workflow! Also, any feedback on the Museum's UI?
Best, Dinesh
-
Comment