Open source

The source is part of the boundary.

Read the workflow where it is implemented: a source checkout, a canonical CLI, a bounded runtime, and a reference control plane.

Open source and Cloud serve different jobs.

OSS gives teams the core workflow and the option to operate it themselves. Hyfens Cloud is the managed path for teams that want the same release and runtime boundary without running the control plane, storage, TLS, upgrades, and recovery procedures. The Cloud service is not a privately modified dashboard fork.

Start from a checkout.

Hyfens is not currently published as a pub.dev package or a downloadable global binary. The supported distribution path is the repository source checkout.

The public command is hyfens. The existing tool entry point is only a deprecated compatibility name and is not a second implementation.

See the release workflow

Source checkout

$ cd hyfens/cli
$ dart pub get
$ hyfens() {
  dart run bin/hyfens.dart "$@"
}
$ hyfens doctor
$ hyfens init

Open surfaces, with their edges visible.

Runtime

A bounded interpreter with an AOT fallback

The runtime checks release identity, capabilities, signatures, sequence, and health without requiring a cloud connection for correctness.

Toolchain

A CLI around ordinary source

The public command surface covers doctor, status, profile, init, release, patch, inspect, verify, deploy, and rollback.

Protocol

Patch Format v1 stays normative

Product metadata refers to signed artifacts and release identity. It does not reinterpret the patch container.

Operations

A reference path for local control

The local and single node control plane makes delivery, profile scope, and operator responsibility inspectable.

Choose your next read.

Product

Follow the command path.

See how source changes become artifacts tied to a release and how unsupported inputs stop.

Read product

Deployment

Put the endpoint in context.

Compare managed and self-hosted delivery without changing the identity or runtime boundary.

Read self-hosted

Need the trust boundary first?

Security is documented alongside the source path, not added as a product footnote.

Read security