Public pages explain DriftFence. Commercial use should be explicit.
These pages describe the product, the measured public results, and the current commercial offer. They are not a substitute for a paid pilot order, commercial agreement, or any software license that ships with a specific package or repository artifact.
Use the site and public docs reasonably.
The public DriftFence site is for evaluating the product, reviewing measured results, and deciding whether a fit review or pilot makes sense. Do not misuse the site, interfere with it, or use it to publish unlawful or abusive content through public channels.
Pricing pages are commercial guidance, not a self-executing contract.
Public pricing is intended to make the commercial shape legible. Final pilot scope, paid rollout terms, support expectations, and any private-repo handling should be confirmed in a written order or commercial agreement.
- Public prices may change as the product matures.
- Pilot scope should be explicit before work starts.
- Enterprise rollout terms should be agreed in writing.
Public results describe measured cases, not universal guarantees.
The product pages and results pages describe measured workflows and replay windows. They show what DriftFence caught in those cases, how the results were reviewed, and how teams can evaluate one private workflow against the same loop. Results depend on each repo, workflow, and CI setup.
Use rights come from the software terms that actually apply.
Nothing on this site grants a separate software license by itself.
The current repo and published packages are intended to be offered
under the Business Source License 1.1 (BUSL-1.1).
That means source is available for review and non-production
evaluation, while production use before the change date requires a
commercial license.
- Read the repository license in LICENSE.
- Commercial rollout terms still need a written order or agreement.