Bitfield Runtime Terms
Closed-source runtime terms for Runtime Kit, Bitfield runtime artifacts, activation, updates, and signed product releases.
Last updated: May 11, 2026
Scope
These Runtime Terms are part of bitfield-product-terms-2026-05-11. They apply to Bitfield Runtime Kit, Bitfield runtime artifacts, runtime launchers, activation tooling, account and license verification tooling, and any object-code runtime artifact shipped by Bitfield or inside a signed Bitfield product release.
Runtime license grant
Subject to your account standing, payment status, product terms, and activation state, Bitfield grants you a limited, non-exclusive, non-transferable right to install and run the runtime artifacts only for valid signed Bitfield product releases and valid activation leases.
You do not receive a general right to copy, resell, host as a separate service, sublicense, publish, or redistribute Runtime Kit or Bitfield runtime artifacts outside a signed Bitfield product release or a written builder redistribution grant.
Closed-source runtime
Runtime Kit and Bitfield runtime artifacts are closed-source Bitfield artifacts unless Bitfield publishes a separate written open-source grant for a specific artifact.
Package material may be inspectable or editable when a product policy allows it. That package lane is separate from the closed-source runtime lane.
Activation and active-device counting
Runtime use is controlled by signed activation, signed manifests, and signed observations. Active device is the public pricing label for a runtime identity where Bitfield was asked to run during the billing window.
Bitfield does not count project names, page names, route names, package names, clicks, visitors, or runtime seconds as active devices by themselves.
Restrictions
- Do not remove, bypass, forge, replay, or disable activation, lease, signature, audit, watermark, update, or package-admission controls.
- Do not extract Runtime Kit or Bitfield runtime artifacts for standalone resale, service bureau use, public mirroring, or unauthorized redistribution.
- Do not reverse engineer or decompile runtime artifacts except where applicable law clearly gives you a non-waivable right to do so.
- Do not use Bitfield runtime artifacts to violate law, infringe rights, attack systems, or bypass account limits.
Third-party components
Runtime artifacts may include third-party dependencies. Third-party notices and licenses remain separate from Bitfield-owned runtime terms.
A third-party notice does not make Bitfield-owned runtime code open source and does not expand your rights in Bitfield-owned artifacts.
Updates and revocation
Bitfield may provide signed updates, security fixes, replacement artifacts, and revocation lists. A product release may require an update before future activation or protected boot continues.
If an account, lease, artifact, or release is revoked, expired, or withdrawn, the affected runtime rights end except for any rights the law requires Bitfield to preserve.
Audit and watermarking
Bitfield may use signed release provenance, watermarks, activation records, package-use proofs, and audit records to detect misuse, trace unauthorized redistribution, and support account or builder compliance.
Watermarks and audit rights are evidence and deterrence. They do not replace activation, signed release manifests, or package admission.