Plan your deployment

DEPLOYMENT / 01

Choose the execution model
for the capabilities you need.

One CroGate currently maps to one team server. Foreground host execution, a Linux system service and Compose are available deployment approaches.

Choose where the gateway runs. Local inference and current public connector management require host execution. Mac servers, arm64 and more GPU platforms are later expansions. — Local inference and current public connector management require host execution. Mac servers, arm64 and more GPU platforms are later expansions.

DEPLOYMENT / 02

Prepare the foundation.

Use the requirements and exact versions supplied with the intended delivery.

Deployment prerequisites
Area	Planning requirement
Gateway runtime	Node.js 22 and persistent gateway state; embedded SQLite is part of the implementation.
Employee containers	Linux Docker Engine is the primary baseline. The service must manage employee containers and their private storage.
Local inference	Run CroGate directly on the host for current inference management; select an engine and model suited to that platform.
Public connector	Current management requires a Linux host gateway with HTTPS; Cloudflare configuration is a separate prerequisite.
Mac client	CroLink targets Apple silicon and macOS 14 or later. Verify the delivered client and gateway combination.
Additional servers and platforms	CroHub and multi-host management are planned. Mac server, arm64 and GPU expansion follows platform-specific work and acceptance.

DEPLOYMENT / 03

Record what will be delivered.

Keep server platform, exact Harness versions, images, models and responsibilities together. Some runtime creation paths resolve an official latest version, so the delivered inventory matters.

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.

DEPLOYMENT / 04

Accept the workflow
on the actual system.

Capacity and reliability are tied to real workload and deployment choices.

01

Connect

Verify employee login, environment selection and the intended entry.

02

Work

Run representative materials with the selected runtime and model.

03

Reconnect

Test files, connection loss and the expected session behavior.

04

Recover

Exercise maintenance and the agreed backup and recovery process.

KEEP EXPLORING

Choose the execution modelfor the capabilities you need.

Choose where the gateway runs