AI WORK INFRASTRUCTURE FOR TEAMS

The infrastructure
for AI work.

Connect people to managed AI work environments.
Bring Harnesses, models and shared skills together on your team’s server.

CroGate + CroLink · Development preview ↗
CroLink and the planned CroHub browser entry connect to one server layer: CroGate access control and managed Harness environments. Harnesses call model services directly; the dashed CroHub link represents planned logical integration.
MANAGED ENVIRONMENTSMODEL CHOICESHARED CAPABILITIES
Deploy centrallyManage runtimes on the server
Assign individuallyA work environment per employee
Choose the right modelLocal, public API or vendor service

02 / SEE THE WHOLE SYSTEM

One view of what connects.

People enter through the gateway. Work runs in individual Harness environments. Each Harness sends model requests to its chosen service.

SYSTEM ARCHITECTURE

One system, clear responsibilities

Full size ↗
One system, clear responsibilities. CroGate manages the server. Harnesses call models directly. CroHub and the Hermes adapter are planned; dashed amber paths show future logical integration.
CroGate manages the server. Harnesses call models directly. CroHub and the Hermes adapter are planned; dashed amber paths show future logical integration.

03 / INFRASTRUCTURE THAT SUPPORTS THE WORK

Bring the right parts together.

Document processing, data analysis and software development are built on a combination of runtime, model and tools.

FROM INFRASTRUCTURE TO WORK

A runtime, a model, and the right tools

Full size ↗
A runtime, a model, and the right tools. Actual capabilities depend on the selected Harness, model, dependencies, skills and business configuration.
Actual capabilities depend on the selected Harness, model, dependencies, skills and business configuration.

Document workflows

Prepare source materials, work through documents and review the resulting files.

Data analysis

Combine data, repeatable scripts and the selected model to explore a question.

Software development

Use terminal tools, code and project files in an assigned environment.

Application scenarios, illustrated conceptually. Actual results depend on the runtime, model, tools and business setup.

04 / CHOICE AT THE RUNTIME LAYER

A common foundation.
A choice of Harness.

Choose the agent runtime for each employee environment. Web and terminal workflows share the same management layer.

HARNESS FAMILY

Choose how people interact with AI

Full size ↗
Choose how people interact with AI. Four Harness integrations in the current gateway scope, with Hermes Agent planned. Claude CLI is the Claude Code command-line tool.
Four Harness integrations in the current gateway scope, with Hermes Agent planned. Claude CLI is the Claude Code command-line tool.
Compare model, skill and network support ↗

05 / KNOW WHERE WORK LIVES

Your environment has a home.
Your models have a destination.

Employee work state lives on the team server. Saved files and model requests follow their own paths.

DATA AT A GLANCE

Where the environment lives. Where requests go.

Full size ↗
Where the environment lives. Where requests go.. The team server stores primary work state. The Mac can keep saved files. Model request content reaches the selected service; CroHub’s data flows are still to be defined.
The team server stores primary work state. The Mac can keep saved files. Model request content reaches the selected service; CroHub’s data flows are still to be defined.
Explore storage and data boundaries ↗

06 / THE NEXT ACCESS LAYER

CroHub brings the browser
into the product architecture.

CONCEPT / PLANNED SAAS
Planned · delivered in stages

A unified employee entry.

CroHub is planned to help people find their assigned environments and give teams a shared view of gateways, configuration and health.

CroGate continues to manage each server. SaaS identity, web and terminal delivery, and file flows will be defined during integration.

Explore the CroHub direction ↗