Self-hosting doesn't mean going without support.

SLA-backed response times, upgrade assistance, and implementation guidance for organizations that want to stay self-hosted but need a safety net beyond community channels.

What the support relationship covers

Three things, matched to where self-hosters actually get stuck. Response: when something breaks, a bounded time-to-answer rather than best-effort community attention. Upgrades: help moving an instance — with its configuration and data — to each release, so staying current never becomes a postponed risk. Implementation guidance: scoping the control model, structuring entities and jurisdictions, and sequencing integrations so the instance reflects your organization rather than a default.

What support does not do is quietly take over the operating model: your instance stays yours, on your infrastructure, and the support line is a safety net under your operation rather than a managed service in disguise. Specific terms — response tiers, coverage hours, pricing — are set in a conversation; nothing is published here.

The typical supported organization is mid-size and up: enough security and compliance estate for self-hosting to matter, enough of it that a failed upgrade or a stalled implementation has a real cost. Below that scale, the community channels are usually enough — and saying so honestly is part of this page.

If your needs grow further — managed hosting, TruSecure's own private inference, premium connectors — TruSecure GRC is the natural next step, built on the same core you're already running.