CONCEPT · ARCHITECTURE
Build a capability once. Any AI can use it.
A workbench is a self-contained space for one kind of work: its tools, the knowledge it builds up as you work, and the ways you can run it. Run one in its MCP mode and any AI tool can use it.
build once: surface it as MCP, API, or UI
WHAT IT IS
One domain of work, self-contained.
A workbench carries everything one domain of work needs: tools (the capabilities it exposes); vaults (the knowledge it accumulates); and modes (how it's hosted, from your terminal to your team's cloud). Drop it into a workshop and it keeps working exactly as it did on its own.
USE OURS, OR BUILD YOUR OWN
Yours to make, yours to keep.
Your own, custom
Build a workbench for your purpose: your incident response, your support triage, your release process, your SCADA monitoring, your compliance reporting.
Hostable
Host it as an MCP server and it's instantly usable by any AI tool your team runs.
Fathym-provided
Connections, queries, dashboards, access: the set OpenX comes with, ready to use.
Portable
Yours, and it travels: fire us, keep running.
HOST IT
One command to bring a workbench to any AI.
Run a workbench in its MCP mode and any AI tool can connect: Claude Code, Cursor, whatever you run. The same command hosts it anywhere, from your laptop to a container in your team's cloud.
THE PRODUCT
fAI is a workbench you use every day.
fAI is a workbench: your personal AI workbench, where your context, tools, and prompts live in one place you own, and compound every session.
See fAI →WHERE IT FITS
The unit everything else composes.
Compose them in a workshop
Workbenches snap together into a shared space your team builds in. The Workshop →
The architecture underneath
Why composition is safe: every workbench is a holon. Holonic →
Build & host your own
Guides for building a workbench and hosting it for your team. Docs →