INTELLISYS / START HERE

Get started

What an administrator and a Mac user need to connect to IntelliSys.

CHOOSE YOUR STARTING POINT

Prepare the server.
Connect the employee.

Start with the role you are taking in the deployment.

I use the work environment

Get the complete gateway address and your account from the administrator, then connect with CroLink.

Read the access guide ↗

A DELIVERY DEFINED FOR YOUR TEAM

Six choices shape the deployment.

The intended workload determines the model, tools and resource plan. Identify the operating responsibilities along with the software.

DELIVERY BLUEPRINT

Define the deployment before sizing it

Full size ↗
Define the deployment before sizing it. A delivery identifies the platform, exact runtime versions, model sources, access path, data policy and maintenance responsibilities.
A delivery identifies the platform, exact runtime versions, model sources, access path, data policy and maintenance responsibilities.

LOCAL PLANNING CHECKLIST

Keep track of what is ready.

This checklist is a planning aid saved in your browser. It does not inspect or provision a server.

Deployment planning0 of 6 prepared

Saved in this browser only.

BEFORE YOU BEGIN

Set the right expectations.

Is this a hosted signup?

This page helps plan a deployment. The current preview is CroGate with CroLink. CroHub’s unified SaaS employee entry is planned.

Does choosing a Harness also choose a model?

It defines how models can be configured. DSH and pi can receive shared connections; Codex CLI and Claude CLI currently use the employee’s vendor service. Hermes integration is planned.

Can we work offline?

Offline delivery is an option. Its scope depends on the Harness, model service and dependencies. Current vendor-backed CLI integrations require external connectivity.

What should acceptance include?

A representative business task, the actual client and gateway versions, file handling, reconnect behavior, data storage and an operational recovery procedure.