Don't compete. Complete.
Crucible is a Developer Experience infrastructure platform — a collection of focused open-source tools that eliminate friction developers face with AI assistant configuration management across tools, repos, and teams.
The metallurgy metaphor
A crucible is the vessel where raw materials are refined under pressure into something useful. Every product name maps to a stage in the metalworking process.
Founding principles
Don't compete, complete
Build the cross-tool coordination layer that no single AI vendor will build. Complement every tool, compete with none.
DX is the whole product
If it's not delightful to use, it doesn't ship. Developer experience isn't a feature — it's the product itself.
Build for the final vision from day one
Architecture supports the endgame even when shipping an MVP. No throwaway scaffolding.
Speed over completeness
Ship narrow, iterate fast. A working tool today beats a perfect tool next quarter.
Community is the moat
Open source. MIT license. Community contributions outscale any solo effort.
Cross-tool is the structural advantage
No AI vendor will solve the multi-tool problem. The value is in the space between tools.
Platform outlasts any individual tool
AI tools will come and go. The coordination infrastructure persists.
Product roadmap
| Product | Type | Purpose | Status |
|---|---|---|---|
| Forge | CLI | AI environment config sync | Shipped |
| Ember | Collector | AI assistant observability | Researched |
| Smelt | Library | Shared plugin engine | Designed |
| Anvil | SDK | Plugin development SDK | Designed |
| Lathe | MCP Server | Forge commands as MCP tools | Designed |
| Foundry | Web + API | Plugin registry/marketplace | Designed |
| Cast | CLI | Frontend/embed scaffolding | Designed |
Architecture: platform of focused CLIs sharing @crucibledx/smelt. See platform architecture.
Path C: Platform of CLIs
Three architecture paths were evaluated: a god-mode universal CLI, separate CLIs with no shared code, or a platform of focused CLIs sharing a plugin infrastructure library. Path C won.
Each product is independent enough to be useful alone, but shares infrastructure for engineering leverage, community cohesion, and a defensible moat.