Ion 2.0: the workspace rebuild

Why we threw it all away

In March, we looked at our usage data and admitted what we'd been avoiding: v1 wasn't working. People signed up, connected their tools, asked one question, and never came back. The activation funnel had a cliff at day 2.

We talked to 40 users who churned. The pattern was the same: Ion was useful for one-off questions, but it wasn't where they worked. It was a fancy search box bolted onto their existing stack — not a replacement for it.

So we decided to start over. Not a redesign — a rebuild. A single surface where you could actually do your work, with an AI that knew what you were working on.

The three principles

Everything in v2 traces back to three decisions we made in week one:

1. One surface, not many

v1 had separate views for docs, tickets, chats, and insights. You had to know which one to look in. v2 has one workspace surface — everything you care about, in one keyboard-driven place. Hit ⌘K and you're anywhere in 2 keystrokes.

2. The AI has to know your context

A chatbot that doesn't know your work is just a slower Google. v2's AI reads your docs, tickets, and threads — so when you ask "what's blocking the launch?", it answers with citations from your actual work, not the open internet.

3. Automations have to be reliable

v1 automations broke constantly. A GitHub API change, a renamed Slack channel, a rate limit — and the whole thing fell over silently. v2 has per-step audit logs, automatic retries with exponential backoff, and one-click rollback to the last known good state. It's boring engineering, but it's the difference between trusting an automation and dreading it.

What we shipped

Four months, 28 people, zero feature freezes. Here's what's new in v2:

• The unified workspace surface with command palette (⌘K).
• Context-aware AI with citations.
• Visual automation builder with branching and error paths.
• Live dashboards rebuilt on a streaming metrics engine.
• Native Anthropic integration with per-workspace model routing.

What's next

We're already working on v2.1 — native desktop apps, a public API for automations, and a bunch of quality-of-life improvements our users have been asking for. Shipping weekly, as always.

If you've been away from Ion for a while, now's a good time to come back. The product you remember is gone. We think you'll like what replaced it.