Air-gapped installs
Miabi runs without internet access. Nothing it needs to deploy apps, serve traffic or validate a licence depends on a connection to the Miabi project. A few features reach out by default; this page lists each one and the setting that turns it off.
Connections Miabi makes on its own
| Destination | Purpose | How to turn it off |
|---|---|---|
https://versions.miabi.io | Daily update check for Miabi, the node agent, the runner and the gateway | MIABI_UPDATE_CHECK=false |
https://miabi.io | Anonymous installation statistics | MIABI_TELEMETRY=false or DO_NOT_TRACK=1 |
https://marketplace.miabi.io | Marketplace template catalog sync | MIABI_MARKETPLACE_URL= (set, but empty) |
| Docker Hub and other registries | Pulling platform, database and application images | A registry mirror, or images pre-loaded on each host |
| Let's Encrypt | Automatic TLS certificates | An internal ACME issuer in the gateway config, or uploaded certificates |
| Public DNS | Domain verification | Force verify the domain as a platform admin |
Each of these fails quietly when it can't connect: the update check records the error for admins, telemetry drops the event, and the marketplace keeps the templates built into the image. Turning them off avoids the attempts and their log lines.
Licence validation is offline. An Enterprise licence is verified locally against a key built into Miabi, so it needs no connection.
See Installation for every installer option.
Connections you configure
These connect only when you set them up, and only to the address you give:
- Git providers for pipelines and Git-sourced apps
- SSO identity providers
- DNS providers for DNS-01 certificates
- S3-compatible storage for backups
- Webhooks and alert notification channels
- An SMTP server for email
- SIEM audit-log sinks
Point each at an internal service, or leave it unconfigured.