zeekayandHanzo Dev a26924402f the beacon was mailing the admin's address to upstream
BEACON_URL was https://sentry.io/remote/beacon/ and every self-hosted install
POSTed to it on a schedule. The payload is not anonymous by default: alongside
install id, version and usage counts it carries get_all_package_versions() — the
full dependency inventory of the running instance — and, whenever
`beacon.anonymous` is off, "admin_email", the address in system.admin-email.

So the fork's own operators were reporting their contact details and software
inventory to a third party, and the settings page explained the arrangement as
though it were still upstream's product. It now posts to api.hanzo.ai/v1/beacon,
and the copy on that page says so, which it could not honestly do before.

Three more outbound identities went with it. USER_AGENT announced every request
this server makes as "sentry/<version> (https://sentry.io)". The Jira and
Bitbucket app descriptors named Functional Software as the vendor — that string
is what a customer reads in the Atlassian marketplace before installing. And the
MS Teams cards sent people to sentry.io/signup for an account they cannot use
here.

Left alone: comments citing upstream issues, form placeholders, and the OIDC
`iss` claim, which is a token-validation input rather than a link.

Co-authored-by: Hanzo Dev <[email protected]>
2026-08-10 18:01:23 -07:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2026-03-26 22:44:08 -07:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2026-08-04 17:21:55 -07:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00
2024-02-15 17:01:50 +00:00

Sentinel

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.

S
Description
Hanzo Sentry — Error tracking and performance monitoring
Readme
27 MiB
Languages
Python 61.4%
TypeScript 37.4%
HTML 0.4%
Less 0.4%
JavaScript 0.2%
Other 0.1%