Setup

Choose the AIGIS boundary before you connect the first system.

Start with a free evaluation workspace. Choose AIGIS-hosted, split into a hybrid control plane, or run customer-hosted inside your environment. Paid activation begins only after the runtime, secrets, audit, and connector boundary is clear.

Apply for hosted deployment Sign in

Selected path

AIGIS-hosted

Paid activation

Request an AIGIS-hosted activation; runtime work starts only after paid approval.

Runtime

Governed

Secrets

AIGIS-managed vault after activation; customer owns production model keys

Audit

AIGIS-managed audit trail after activation

First value

After paid activation

Setup paths

Pick the paid activation path that matches the buyer.

Start with the operating boundary: who runs the runtime, who holds secrets and model keys, and where audit evidence needs to land.

Paid activation

AIGIS-hosted

Teams that want Governed to operate the control plane

Governed can operate the AIGIS console, metadata store, runtime, API endpoint, and connector orchestration after a paid SOW or activation deposit. Your business systems and production model keys remain customer-owned.

Paid commercial activation first
BYO production model keys
Runtime provisioned after approval

Select Continue

Paid hybrid activation

Hybrid

Growing or regulated teams

Governed can operate the public experience and customer portal after paid approval while your runtime, secrets, and data-touching connectors stay in your environment.

Customer-hosted MCP runtime
BYO production model keys
Optional audit replication

Select Continue

Paid private activation

Customer-hosted

Large enterprise, VPC, private cloud, or on-prem

After paid approval, your team hosts the AIGIS console, governance engine, database, secrets vault, connector runtime, logs, and optional knowledge indexes.

Dedicated runtime boundary
Customer-managed database and audit store
Deployment kit and upgrade path

Select Continue

Deployment comparison

What changes by deployment mode

The product surface is the same. The paid activation step, operating boundary, secrets model, and rollout effort change.

Path	Best for	Runtime	Secrets	Effort
AIGIS-hosted	Teams that want Governed to operate the control plane	Governed	AIGIS-managed vault after activation; customer owns production model keys	Commercial approval, activation call, credentials, rollout
Hybrid	Growing or regulated teams	Customer cloud	Customer vault; customer owns production model keys	Deploy runtime, connect systems, configure audit export
Customer-hosted	Large enterprise, VPC, private cloud, or on-prem	Customer VPC or private cloud	Customer vault; customer owns production model keys	Deployment kit, runbook, security review, controlled rollout