Ember — Updated Page Content

Reference doc for updating ember.astro. Reflects current state as of April 2026. Voice: same as existing page — direct, confident, no filler.

What’s changed since the last update

The current page frames Ember as a personal project still looking for a direction. That’s no longer accurate:

• 48 specialist agents (was “~40”), now organised into 6 named teams
• A CLI (ember new, ember init) that scaffolds full agent environments into new projects
• Skills — invocable structured workflows (like slash commands for multi-step procedures)
• MCP Integration Packs — live SaaS API connections any agent can call
• A commercial product roadmap with 7 phases in progress
• First commercial SaaS integration: Floways — Ember is embedded as the AI provider inside a church management platform, powering site generation, content editing, and SEO auditing at scale

The availability section needs the biggest change. “I’m still deciding what it becomes” is out of date.

Meta

Title: Ember — AI Agent Framework | Dave Bock Description: Ember is a commercial AI agent framework — 48 specialist agents, 6 teams, a CLI, skills, and MCP integrations. Now powering its first SaaS product.

Hero

Label: Project

Heading: Ember The AI brain behind your business.

Subheading: 48 specialist agents. 6 teams. One orchestrator that knows how to use all of them. Ember runs on Claude Code — you tell it what you want, it figures out who handles it and gets it done.

Badges: Active · In Production

How it works

Label: How it works

Heading: Built like a team. Works like one.

Body: Ember isn’t a single AI tool — it’s a structured team of specialists. Six named teams cover every function: Build, Quality, Infrastructure, Data & AI, Research, and Content. Each team has a lead agent. The Orchestrator routes your request to the right lead, who sub-delegates to the right specialists. Work that can run in parallel does.

You don’t prompt individual agents. You tell the Orchestrator what you want built, fixed, deployed, or written — and it handles the coordination. Skills compress multi-step procedures into a single command. MCP Integration Packs connect agents directly to live SaaS APIs — Stripe, Slack, Vercel, GitHub, and dozens more — so agents can take real action, not just generate code.

The result is something that feels less like a tool and more like having a competent team on call.

Feature Cards

Card 1 — heading: 48 specialists across 6 teams. Card 1 — body: Build. Quality. Infrastructure. Data & AI. Research. Content. Each team has a lead agent and a roster of domain specialists. The Orchestrator routes to the lead — the lead runs the team. You deal with outcomes, not agent management.

Card 2 — heading: Parallel by default. Card 2 — body: Multiple agents run concurrently. Frontend and backend can build at the same time. Multiple projects can run in parallel sessions. The trade-off is token spend — the payoff is speed and throughput that changes what’s possible in a day.

Card 3 — heading: Skills and MCP packs. Card 3 — body: Skills are structured workflows invoked as slash commands — /deploy, /security-audit, /session-end. MCP Integration Packs connect agents to live SaaS APIs so they can take real action: create a Stripe subscription, post to Slack, deploy to Vercel. One install command, live in every agent.

Card 4 — heading: It never forgets. Card 4 — body: Persistent memory across every session. Architecture decisions, context, and in-progress work carry forward. SESSION.md tracks what’s active. HISTORY.md keeps the record. You never re-explain yourself.

In the Wild

Label: In the wild

Heading: In production. In someone else’s product.

Body: Ember isn’t just running on my own infrastructure anymore. It’s embedded inside a commercial SaaS platform — powering AI features for real users at scale. Can’t name it yet, but the integration is live. That’s the shift from framework to platform.

Proof cards:

• A SaaS platform (NDA) — Ember is embedded inside a commercial SaaS product as the AI provider, powering site generation, content editing, and SEO auditing for real users. Can’t name it yet.
• This website — Built and maintained by Ember agents
• Sieno — AI-powered local SEO platform
• bible-study-automation — Automated weekly Bible study content pipeline, 12-phase system
• Snake Game → — Proof of concept, built in one session

Availability

Label: Where it’s heading

Heading: A commercial product. In production.

Body: Ember started as a private framework I built for my own work. That phase is over. The first commercial integration is live — Ember is embedded inside a SaaS platform as the AI provider, running real workflows for real users. The details aren’t public yet, but the build is in flight.

The product roadmap is moving: CLI, agent teams, skills, MCP integration packs, and Ember Cloud are all in progress. Early access conversations are open for teams who want to build with agent-first architecture — properly — before it’s widely available.

CTA: Let’s talk about it →

Quote (keep as-is)

“The best software isn’t written by AI. It’s written by humans and AI working in concert — with the right structure to make that actually work.” — Dave Bock

Notes for implementation

• Change badge from Private to In Production
• Update agent count from ~40 to 48 throughout
• The “Connects to anything” card can be retired — the Skills/MCP card is a more accurate representation of where Ember is now
• The “SaaS platform (NDA)” card in “In the Wild” is the most important addition — it’s the proof point that changes the page’s whole tone. Update when the partner goes public.
• Availability section: remove “I’m still deciding what it becomes” — replace with the commercial framing above
• Consider adding a second CTA alongside “Let’s talk”: “Follow the build” → links to GitHub or a newsletter (if/when that exists)