hyfens
Dashboard

Self-hosted

Run delivery where your team operates.

Choose the endpoint once, keep the same CLI and auth model, and make the operator boundary visible from the first command.

A profile carries the choice.

Managed and self-hosted work use one profile shape: endpoint, authenticated session, organization, application, and environment. Profiles contain metadata only. Credentials are stored separately and bound to the endpoint origin and API base path.

Select an endpoint
# managed default
$ hyfens login
# self-hosted profile
$ hyfens login \
  --host https://hyfens.example.com \
  --profile acme
# deploy through the active profile
$ hyfens deploy

Same identity. Same boundary.

Developer workflow

One command surface.

Login, profile, init, release, patch, verify, deploy, and rollback keep the same names and semantics across endpoints.

Review the product path

Identity authority

One session model.

Short-lived access JWTs, revocable server sessions, and authoritative membership authorization serve the CLI and web dashboard together.

Review the security model

Ownership is part of the deployment.

The current self-hosted path is a local and single-node reference. It is useful for exercising the workflow, not a claim of packaged production hosting or high availability.

  • Storage and immutable artifact retention
  • Signing key handling and access policy
  • Backups, upgrades, and recovery procedures
  • TLS, ingress, capacity, and availability

Keep the source close too.

See the open workflow and the current distribution boundary.

Explore open source