2
2 Comments

I’m building The Tank — a “collective AI” that can chat + build in one place!

Hey Indie Hackers — I’m building thetank.io because I’m tired of the same loop:

• Ask AI for help → it generates code
• You paste it somewhere else → preview breaks / context is gone
• You bounce between 6 tools + 12 tabs → the “build” is fragmented
• You come back later → the code/preview/decisions are lost

What the Tank is
thetank.io is one product that does two things really well:

  1. Conversation — requirements, iteration, decisions, debugging
  2. Building — generates real code + shows a live split-pane preview (v0-style)

The core idea is “Collective AI”:
Instead of betting everything on one model, the Tank routes across multiple models (via Vercel AI Gateway) to pick the best brain for the job — planning, coding, debugging, and writing.

What it’s trying to feel like
If the best parts of chat AI and app builders had a baby:
• you describe what you want
• it scaffolds the app (front + back)
• it renders it live
• it remembers the build so you can return later and keep going

Where I want feedback (and eyes)
I’m currently focused on making the builder experience bulletproof:
• stable, interactive preview (no flaky fallbacks)
• persistent code + preview per chat (so revisiting a build actually works)
• clear “chat → build” behavior so it knows when to generate a real project structure

If you’ve built anything involving live previews / sandbox rendering / multi-file project execution:
What’s the cleanest architecture you’ve seen for reliable previews AND persistent builds?

If you want to poke at it (and roast it), here’s the link:
https://thetank.io

posted to Icon for group Product Launch
Product Launch
on February 14, 2026
  1. 1

    Strong framing on “chat → build” continuity. For persistent builds, the cleanest pattern I’ve seen is versioned project snapshots + deterministic preview: each chat step commits a build artifact (files + deps + env), preview spins from that snapshot, and you keep a lightweight intent log for replays. Helps avoid “flaky preview” drift. Are you storing a per‑chat project root + dependency lockfile to keep previews deterministic across sessions?

  2. 1

    I am a beginner in Saas just prepared a product and actively looking for ways to get customers, so my thought might not be valuble , but I will suggest to focus on this specific segment and keep the other opportunities into a seperate portal i.e front end alone , as the cutomer would love it if it focusses on thier problem rather than generic. :)

Trending on Indie Hackers
I built a tool that turns CSV exports into shareable dashboards User Avatar 82 comments Why Indie Founders Fail: The Uncomfortable Truths Beyond "Build in Public" User Avatar 69 comments $0 to $10K MRR in 12 Months: 3 Things That Actually Moved the Needle for My Design Agency User Avatar 68 comments The “Open → Do → Close” rule changed how I build tools User Avatar 52 comments I got tired of "opaque" flight pricing →built anonymous group demand →1,000+ users User Avatar 42 comments A tweet about my AI dev tool hit 250K views. I didn't even have a product yet. User Avatar 42 comments