Deploy Shield360
Shield360 runs two ways:
Sign in at app.shield360.ai. Nothing to deploy: enrol machines and point SDKs at your organisation.
Self-hostedRun the whole platform in your own infrastructure, so telemetry and collector data never leave it.
A self-hosted deployment has three components:
- The Shield360 platform (UI, APIs, collector ingest, and the CLI downloads served to enrolling machines)
- ClickHouse for telemetry and collector data
- An OpenTelemetry Collector for SDK telemetry
Self-host with Docker Compose
Section titled “Self-host with Docker Compose”git clone git@github.com:ThinkfleetAI/Shield360.gitcd Shield360docker compose up -dShield360 is then available at http://127.0.0.1:3000.
The platform image carries the shield360 CLI for macOS, Linux and Windows. Machines enrolling against your deployment download it from /api/cli/download/*, with install scripts at /api/cli/install.sh and /api/cli/install.ps1. See Deploy the collector.
Kubernetes
Section titled “Kubernetes”For production Kubernetes deployments, contact hello@shield360.ai for manifests and sizing guidance.
Frequently asked questions
Section titled “Frequently asked questions”Should I use managed or self-hosted Shield360?
Managed is the quickest start. Self-host when collector data, prompts and telemetry must stay inside your own infrastructure; every feature in this documentation runs self-hosted.
Can I reuse my existing ClickHouse or OpenTelemetry Collector?
Yes. Shield360 can connect to infrastructure you already run instead of deploying its own ClickHouse or OTel Collector. See Connect Multiple Databases for setup.
Do enrolled machines need to reach the internet?
No. Machines download the CLI from, enrol with and report to your Shield360 deployment only.