Self-hosted Hyfens
Self-hosting runs the OSS customer/control-plane package on infrastructure you operate. It is a separate deployment model from Hyfens Cloud.
Supported deployment scope
The public v0.1.10 guide documents a single-node Docker Compose deployment with PostgreSQL and MinIO, application ports bound to loopback by default, and TLS provided by a reverse proxy you operate.
The guide does not claim high availability, automatic TLS, scheduled backups, or zero-downtime migrations. It requires PostgreSQL and MinIO data to be backed up together and restores to be tested, but does not provide a restore or cleanup procedure.
Image access can block installation: The guide notes that anonymous pulls from GitHub Container Registry may return 401. Check package visibility before starting. If access is restricted, use only an authorized registry login or the image override path allowed by the guide; keep registry credentials out of project files and logs.
Use the canonical guide
Follow the versioned Hyfens v0.1.10 self-hosted installation and upgrade guide. It is maintained with the deployment package and is the source of truth for prerequisites, environment setup, startup, health endpoints, backup requirements, and upgrades.
Do not use the Cloud documentation hostname or Cloud marketing pages as a substitute for control-plane URLs, credentials, or self-hosted setup instructions. Conversely, self-hosting guidance does not establish that managed Cloud account or release workflows are enabled.