The operating problem
Regulated and industrial environments need repeatable upgrades, offline assets, customer-managed identity, secrets, TLS, backups, observability, and emergency access.
The intended control surface
This capability is part of the reviewed product architecture, not a decorative console module.
- Offline image and documentation bundle
- Customer-provided TLS, SMTP, identity, and object storage
- Restricted-egress defaults
- Local backup, restore, upgrade, and audit evidence
What exists today
A hardened Docker Compose single-VPS topology exists. Dedicated on-premises packaging, SOPS/age delivery, and air-gap installation evidence remain incomplete.
Work with the implementation team
Reallexi is accepting architecture conversations with teams whose requirements can shape this production slice. An inquiry does not imply that an unshipped feature is available.
Frequently asked questions
Is this capability generally available?
No. The page describes a reviewed implementation direction. The current capability boundary is stated above and in the public changelog.
Can Reallexi evaluate our requirements?
Yes. Use the enterprise inquiry form without including credentials, private payloads, or regulated data.