Want to request a feature / improvement?

Tell us how we could make the product more useful to you.

Hetzner Cloud integration for self-hosted deployments — built and ready to contribute

The public integrations catalog lists Hetzner (2 checks), but the check DSL is intentionally excluded from the catalog sync and there is no code manifest — so self-hosted deployments get the catalog entry without the integration. We run Comp self-hosted (EU company, all production infra on Hetzner) and built the integration as a validated dynamic-integration JSON: 9 checks against the hcloud API with a read-only token — firewall attached per server, no management ports open to 0.0.0.0/0, backups enabled + recent, delete protection, LB https + health checks, certificate expiry, labeled-inventory evidence, SSH-key allowlist — each mapped to ISO 27001 / SOC 2 via taskMappings, with Spanish names/remediations (but we can provide an engilish version too). It runs daily against our real infrastructure and already surfaced a genuine finding on day one. We'd like to contribute it upstream so every self-hosted user gets Hetzner out of the box. Two possible paths — maintainers' choice: Code manifest under packages/integration-platform/src/manifests/hetzner/ (PR to dev per the writing-integrations docs). Caveat: code manifests take precedence over dynamic slugs, so this would shadow the production dynamic hetzner — happy to coordinate merging the two check sets. We donate the validated dynamic JSON so it lands in the production catalog for cloud and self-hosted alike. While building it we found and reported two runtime bugs with proposed fixes (GitHub issues: page pagination breaks on envelope APIs; buildUrl drops baseUrl path segments) plus a UX papercut (post-connect redirect goes to /cloud-tests, which is hardcoded to aws/gcp/azure and can never show the provider just connected). Happy to open the draft PR or hand over the JSON — whichever the team prefers.

Eudald Arranz 12 days ago

More branding controls in the Trust Center

Our Trust Center is embedded directly into our website and plays a key role in shaping how large customers perceive our brand. Since it’s a touchpoint designed to build confidence, it’s important that it visually aligns with our brand identity. Right now, customization options are quite limited, which creates a mismatch with our otherwise consistent brand experience. Some things I’d like to do: Color customization – Ability to set primary, secondary, and background colors. (Example: we’d like a dark background theme to match our website.) Customize the header - add a description, contact email, and external links More subtle ‘Monitored by Comp AI‘ - should be at the bottom of the page. While I totally get its value, being a fellow startup, it should be a bit more discreet, especially on a site whose whole goal is to ensure trust. I don’t want to market another startup overly on it. I think that at the bottom of the page is equally good, as someone who’s interested will scroll there to check it out anyway. I think Intercom’s Trust Center is a good example of what we’d like to achieve with branding and customizations:

Markus Palm 12 months ago