CONCEPT · ARCHITECTURE

Your team's workbenches, working as one.

Your workbenches compose into one shared space your team builds in: connect your information, turn your team's work into shared tools, and build together.

IntegrationsAnalyticsDeploymentsMonitoringOne workshopone shared context

different workbenches, different domains, one shared workshop

HOW WORKBENCHES COMPOSE

Your team's workbenches, one shared context.

Each workbench covers one domain of work: connections, queries, analytics, hosting. The workshop is where they compose, a shared space where the team connects its information and builds on it together. And each hosted workbench keeps its own endpoint, so nothing gets trapped behind one shared server.

WORKBENCH VS WORKSHOP

The unit, and where units come together.

Workbench

  • ·One domain of work, self-contained
  • ·Tools, vaults, and modes: whole on its own
  • ·Hosts as MCP today; API mode next
  • ·fAI is one you use every day

Workshop

  • ·Many workbenches, composed
  • ·One shared space, one shared context
  • ·The team connects, reviews, and builds together
  • ·OpenX is one your team can use today

IN ACTION

OpenX is a workshop your team can use today.

OpenX is a workshop, where your team's workbenches come together: connect real data, turn the work that matters into shared tools, and run the propose → review → ship loop, so a human decides what ships.

See the full OpenX story →

WHERE IT FITS

Between the unit and the family.

OpenX, team workshop

The workshop your team logs into.

OpenX →

Holonic, underneath

Why composition holds at every scale.

Holonic →

Workbenches, the unit

What a workshop is made of.

Workbenches →