Your boundary
Customer data and OAuth tokens move between your application and the upstream platform only. There is no OpenSteward cloud in the data path, and no telemetry.
OpenSteward runs inside your own infrastructure, so your security team reviews the code and the deployment rather than a vendor's promises. This page is the short version; the security guide has the threat model and the hardening checklist.
Customer data and OAuth tokens move between your application and the upstream platform only. There is no OpenSteward cloud in the data path, and no telemetry.
The license file is signed and checked on the install itself. Nothing phones home, so air-gapped installs work, and an expired license never stops production: features step down after a 30-day grace period and nothing is deleted.
Every line is on GitHub. Images are multi-arch, digest-pinned, cosign-signed and SBOM-attested, and the build gates on a vulnerability scan.
127.0.0.1.Please report security problems through GitHub Security Advisories on the OpenSteward repository, not in public issues. We aim to acknowledge reports within 5 business days and follow a coordinated 90-day disclosure window. If GitHub is not an option, write to support@opensteward.dev. The same details are in security.txt.
opensteward.dev and docs.opensteward.dev are static pages. They set no cookies and load no analytics, fonts or scripts from anyone else. A strict Content-Security-Policy allows only this site's own files, plus platform logos from Brandfetch on the docs' Platforms page, and HSTS keeps every visit on HTTPS. Signing up for a license happens on license.opensteward.dev, under its own terms and privacy notice.