v0.4.2regionus-east-1builds/7d41pipeline active
FLA / PUBLIC BETA
LEGAL / TERMS OF SERVICE
$flareo legal --terms# effective April 23, 2026

TERMS OF
SERVICE.

The plain-language version. If you find something confusing or disagreeable, open an issue on GitHub and we'll clarify or rewrite it.

01WHO THESE TERMS ARE BETWEEN

These terms are between you and Flareo ("we", "us"). "You" means any person or organization using the Flareo website, the command-line tool, the API, or any signed container images we publish.

Accepting these terms happens automatically when you use the service. If you don't accept them, don't use the service. Simple as that.

02WHAT WE PROVIDE

Flareo publishes rebuilt and cryptographically signed container images. We also provide a web catalog, a CLI, and an API for browsing and verifying those images.

Every signed image comes with an SBOM and a vulnerability scan at the time it was built. We don't warrant that a given image is safe to run, only that the signature really belongs to our build pipeline and the scan we ran found what it says it found.

03ACCOUNTS AND API KEYS

You can browse the catalog and verify images without an account. For higher API rate limits and for submitting your own modules (Horizon 2+), you sign in via GitHub.

You are responsible for keeping your API keys private. If a key leaks, revoke it immediately at /app/settings/api-keys. We'll also revoke it on request if you email us.

04ACCEPTABLE USE

Don't abuse the service. Specifically, don't try to:

  • automate requests past our rate limits (60/hour anon, 600/hour authenticated on verify; 300/hour on catalog reads)
  • probe for vulnerabilities without filing a report via GitHub Security Advisories first
  • use Flareo as a general-purpose container distribution service (that's Docker Hub's job)
  • misrepresent yourself or your organization when submitting modules

If you do any of the above we may throttle, suspend, or terminate your access without warning.

05OPEN SOURCE AND THE AGPL

Most of Flareo's own code — the web app, the CLI, the canary pipeline — is licensed under AGPL-3.0-or-later. Source is at github.com/Yolo1105/flareo. The images we publish inherit whatever license the upstream project uses; check each module page for the specific license.

If you deploy a modified version of Flareo as a service, the AGPL requires you to publish your modifications. That's the point.

06NO WARRANTY

Flareo is provided "as is," without warranty of any kind. We try to operate a reliable service, but we make no guarantees of uptime, accuracy, or fitness for any particular purpose.

In particular, a Flareo signature does not guarantee a container is free of security vulnerabilities, malicious code, or bugs. It guarantees only that the image was built by our pipeline from the upstream source we claim.

07LIABILITY

To the maximum extent allowed by law, Flareo is not liable for any indirect, consequential, or incidental damages arising from your use of the service. Our total liability in any dispute is capped at what you've paid us in the 12 months preceding the claim, or €100, whichever is greater.

During closed beta, the service is free, so in practice this cap is €100. That's the honest version.

08CHANGES TO THESE TERMS

We may update these terms. If the change is material — anything that affects how you use Flareo or what we do with your data — we'll email anyone with a registered account and post a notice at /changelog at least 14 days before the change takes effect.

09TERMINATION

You can stop using Flareo at any time. We'll delete your account data within 30 days if you open an issue on GitHub to request it.

We may terminate accounts that violate section 4, or for other good-faith reasons. If that happens we'll tell you what went wrong.

10GOVERNING LAW

These terms are governed by the laws of the jurisdiction where Flareo is incorporated. Disputes go to the courts of that jurisdiction unless both sides prefer arbitration.

11CONTACT

For terms questions: GitHub Issues. For security reports: GitHub Security Advisories. For everything else: GitHub Issues.

Last updated: April 23, 2026
See also: privacy policy