zeekayandHanzo Dev
f888991a7a
FSL-1.0-Apache-2.0 grants us the code, not the name. "Sentry" is Functional Software's trademark, so every place the running app says it to a user -- page titles, onboarding, empty states, toasts, settings copy, the self-hosted footer -- now says Sentinel. Attribution is the other half of the deal and stays untouched: upstream copyright headers, LICENSE, NOTICE. So does anything where the mark is a fact rather than a brand -- @sentry/* packages, sentry-cli, the wizard and bundler plugins, docs.sentry.io, the whole gettingStartedDocs tree. Renaming those would leave instructions that no longer work. Nothing structural moved. No import, identifier, route path, feature flag, API field or test id changed; the diff is 312 lines in and 312 out. Colocated specs were updated in lockstep with the copy they assert. Marketing and community links point at hanzo.ai, only where a real page exists to point at. Co-authored-by: Hanzo Dev <[email protected]>
Sentinel
Error tracking and performance monitoring for the Hanzo cloud. Sentinel receives events from your applications, groups them into issues, and tells you which ones are new, regressed, or getting worse.
Sentinel speaks the Sentry wire protocol, so the existing ecosystem of client SDKs reports to it unchanged — a DSN pointing at your Sentinel instance is the only configuration difference. There is no Sentinel-specific SDK to adopt, and none is planned; the protocol is the interface.
Running it
The deployed image is ghcr.io/hanzoai/sentry. Deployment is declared in the
universe repository and reconciled by Hanzo CD, like every other service.
Attribution and licensing
Sentinel is a fork of Sentry by Functional
Software, Inc., used under the Functional Source License, Version 1.0, Apache
2.0 Change License (FSL-1.0-Apache-2.0). See LICENSE for the
terms and NOTICE for attribution; both are required and are kept
current.
The FSL grants no trademark rights. "Sentry" is a trademark of Functional
Software, Inc., and this project is neither affiliated with nor endorsed by them.
Upstream marks are not used as branding here — where the name appears in this
codebase it refers to the module namespace (src/sentry/), the wire protocol, or
upstream attribution, none of which are brand usage.