Exact identity
Application, release, capability, sequence, digest, and signature checks remain part of acceptance.
Flutter support today
Ship the patch.
Keep the boundary.
Hyfens is secure mobile release infrastructure for signed, exact release patches to supported mobile application code.
01Supported ordinary Dart and Flutter source
02Patch Format v1 with signed bytes
03Normal Flutter AOT remains the fallback
What Hyfens is
Secure mobile release infrastructure for Flutter teams.
Hyfens records an exact release identity, classifies supported source changes, creates signed patch artifacts, and delivers them through managed Cloud or self-hosted infrastructure.
The runtime remains responsible for accepting the exact bytes that run. Read the product workflow or compare Cloud plans when you are ready to choose an operating model.
A normal edit, a bounded patch.
The workflow starts in a Flutter project and ends with a checked artifact or a clear reason to use a store release.
- doctor / init / release
Establish a baseline
Check the Flutter project, write the minimal
hyfens.yamlbinding, and record the release identity for the target. - analyze
Classify the change
Analyze the edit against the exact release. Unsupported or native changes stop with a store release required result.
- patch / inspect / verify
Sign and inspect
Create a signed Patch Format v1 artifact, then inspect its bytes, digest, signature, and release binding locally.
- deploy / rollback
Deploy or recover
Upload exact verified bytes to the selected endpoint, or issue the bounded signed rollback-to-base operation.
The service can suggest. The runtime decides.
Delivery may be managed or self-hosted. Device-side checks stay authoritative for the bytes that run.
Local verification
Inspect and verify the artifact before deployment. The selected endpoint is not the runtime trust root.
Separate trust
Authentication JWT signing material stays separate from Patch Format signing material.
Bounded recovery
Signed rollback-to-base keeps the runtime high-water intact and does not make an old patch replayable.
One CLI. Two deployment choices.
Use the managed API when it fits. Select a self-hosted endpoint when your team needs to own the delivery surface.
Managed
Keep the endpoint simple.
The managed control plane is selected by the active profile. The Cloud workspace and CLI use the same identity and authorization authority.
Sign in to CloudSelf-hosted
Keep the operator in control.
Choose an HTTPS API base or a loopback development endpoint. Storage, keys, upgrades, and availability remain operator responsibilities.
See the self-hosted pathHyfens Cloud
Start free. Add capacity when you need it.
Begin with managed Cloud infrastructure and the real Hyfens workflow. Move to Starter, Team, or Enterprise as your applications and organization grow.
Free is a Cloud plan. Self-hosting is separate when your team needs to own infrastructure, storage, keys, and operations.
When the boundary says no, it says why.
Hyfens does not turn an unsupported change into a partial patch. It reports the normal release path when the edit includes a native or unsupported input.
- Native code, manifests, permissions, and entitlements
- Dependency, asset, or compiled-library changes
- Unsupported Dart or Flutter constructs
Start with the command surface.
Read the supported workflow, then decide whether managed or self-hosted delivery fits your deployment.