The installer checks your host, registers your evaluation, pulls the platform images and starts everything under Docker. It runs on the infrastructure you control, and your data stays there.
curl -fsSLO https://apimapper.ai/install/install.sh && bash install.shinstall.sh in the current folder and then runs it, so you can read the script first. To check it against the published checksum before running it (optional):curl -fsSLO https://apimapper.ai/install/SHA256SUMS
grep ' install.sh$' SHA256SUMS | sha256sum -c -docker-compose.yml, .env and license/), the license status and the Portal address.bash install.sh update-license /path/to/license.jsoncurl -fsSLO https://apimapper.ai/install/install.sh && bash install.shinstall.sh in the current folder and then runs it, so you can read the script first. To check it against the published checksum before running it (optional):curl -fsSLO https://apimapper.ai/install/SHA256SUMS
grep ' install.sh$' SHA256SUMS | shasum -a 256 -c -docker-compose.yml, .env and license/), the license status and the Portal address.bash install.sh update-license /path/to/license.jsonInvoke-WebRequest https://apimapper.ai/install/install.ps1 -OutFile install.ps1; pwsh -ExecutionPolicy Bypass -File .\install.ps1install.ps1 in the current folder and then runs it, so you can read the script first. To check it against the published checksum before running it (optional):$expected = ((Invoke-RestMethod https://apimapper.ai/install/SHA256SUMS) -split "`n" | Where-Object { $_ -like '*install.ps1' }).Split(' ')[0]
(Get-FileHash .\install.ps1 -Algorithm SHA256).Hash -eq $expecteddocker-compose.yml, .env and license/), the license status and the Portal address.pwsh -ExecutionPolicy Bypass -File .\install.ps1 update-license C:\path\to\license.json