Indbase
Build apps, not backend infrastructure
I've spent the last few years working in DevOps and cloud infrastructure, helping startups deploy and scale applications.
One thing kept bothering me:
Developers spend an incredible amount of time stitching together databases, auth, storage, APIs, deployment pipelines, monitoring, and now AI infrastructure.
Every tool is great individually.
The experience of combining them isn't.
So I started building IndBase.
The goal is simple: give developers a single platform to build, launch, and scale modern applications without spending weeks configuring infrastructure.
Think managed PostgreSQL, authentication, storage, real-time capabilities, vector search, and AI-native tooling in one place.
We're still early and actively building.
I'd love feedback from founders and developers:
What's the most frustrating part of your backend or infrastructure stack today?
1 Comment
One thing I'd be careful with:
The challenge may not be whether developers want fewer tools.
The harder decision could be what they're actually hiring the platform to simplify.
Those sound similar, but they can lead to very different product directions.