Introduction
← Back to Index | Next: Architecture →
1.1 What this guide covers
This guide walks you through installing Deslicer AI and the Deslicer Automation Platform (DAP) on infrastructure you operate (your data center, cloud project, or agreed MSP environment)—not Deslicer SaaS.
You will:
- Use a Deslicer-provided provisioning package to obtain install answers and registry access
- Install Deslicer AI with the published curl installer
- Terminate public HTTPS with Deslicer-managed Caddy on the DAI and DAP hosts
- Enroll and install DAP from Deslicer AI Control
- Finish operator settings (SMTP, AI models, certificates) in Control
- Rename the default System tenant in the Enterprise workspace, then assign roles (Chapter 8, Chapter 12)
- Apply updates from Control → Updates, and uninstall with the published teardown scripts when retiring a DAI or DAP host
1.2 Key terminology
| Term | Definition |
|---|---|
| Deslicer AI | Application for end users: web UI, data plane, and supporting containers (database, LLM proxy, and related services). |
| Control | Deslicer AI management UI on the same hostname under /control. Operators use Control after install for platform settings and DAP enrollment. |
| Enterprise workspace | Customer access management UI at /dashboard/enterprise (tenants, members, roles, teams). Not the same as Control. |
| Deslicer Automation Platform (DAP) | Required automation component: Observer API and Observer management UI. |
| Observer API | DAP HTTP API used by workers, insights, and Deslicer AI integration. |
| Deslicer provisioning package | Handoff file (provision.yml or age-encrypted provision.enc.yml) from Deslicer that carries engagement answers and credentials. |
| Install state | Age-encrypted host file (/opt/deslicer/ai/install-state.enc.yml) that stores the generated master seed for updates. |
| DAI host / DAP host | The two product servers in a split install. Prefer these terms over bare “host” when either product could be meant. |
<dai-host> / <dap-host> | Placeholders for the public DAI FQDN and DAP FQDN. Do not interchange them in commands. |
| Edge proxy (Caddy) | Deslicer-supplied reverse proxy on each product host. It terminates TLS and routes to loopback application ports. |
| Container registry | Deslicer registry used to pull product images (container-registry.deslicer.io and related hosts). |
| Artifact registry | Host for install scripts and packages (artifact-registry.deslicer.io). |
| Engagement | A customer deployment instance planned and handed off by Deslicer. |
1.3 Install sequence (summary)
Host prep on DAI host (deslicer:deslicer, etc/age keygen)
→ send printed age1… recipient to Deslicer
→ stage provision.enc.yml under /opt/deslicer/etc/dai/
→ deslicer-dai-install.sh (app + Caddy; host-staged secrets)
→ sign in to Control
→ enroll DAP (public hostname DNS ready) → Update or Fresh token from Control
→ Host prep + deslicer-dap-install.sh on DAP host (stack + Caddy; --update when Control issues Update)
→ verify Control probe Active / Healthy → Web certificates and post-install settings
1.4 Document scope
In scope
- Split-host enterprise install (DAI host and DAP host)
- CIS Benchmark / STIG-hardened Linux hosts (Amazon Linux 2023, RHEL-family, Debian-family)
- Curl installers and uninstallers from the artifact registry
- Deslicer Caddy TLS for DAI and DAP
- Control enroll for DAP, Control → Updates, and post-install operator settings
- Outbound network allowlists for registries and ACME
Out of scope
- Deslicer SaaS tenancy
- Splunk host enrollment and worker package uninstall (covered in product runbooks after the platform is up)
- Assisted installs performed by Deslicer on your behalf