This page describes how The Channel Standard operates, what the company commits to, and how Channel Companion is built around those commitments. It is published in full because every other player in the channel has a financial reason not to publish a page like this. We believe the absence of one is part of why the channel works the way it does today.
The Channel Standard is the company. Channel Companion is the platform. The commitments below belong to The Channel Standard. The platform behaviors that implement them belong to Channel Companion. We keep the names distinct because the relationship between them is intentional architecture.
The technology services channel runs on relationships, but the infrastructure that supports those relationships has historically operated on opacity.
None of this is a moral failure of any individual company. It is a structural feature of an industry where the players responsible for transparency are the same players whose business models depend on opacity. The asymmetry is invisible because there is no comparison case.
The Channel Standard exists in part to be that comparison case. Channel Companion is the platform that operationalizes it. This page is the architecture that connects the two.
The Channel Standard is built around three audiences whose interests have to be aligned for the channel to work. Channel Companion is the platform built to implement these commitments.
The following commitments are published in writing because publishing them in writing is the most credible way to make them durable. Each item describes a category of behavior The Channel Standard will not engage in, and that Channel Companion is built to make impossible.
These distinctions are listed because confusion about them is the source of most concerns we hear from people new to the platform.
Channel Companion does not collect client billing data, contract terms, commission information, or any data from TSD systems. The platform does not access advisor email, calendars, or systems outside Channel Companion.
Channel Companion is built to SOC 2 standards. We are actively pursuing SOC 2 Type II certification.
We will publish updates to this section as our security posture evolves.
A transparency layer for the channel requires structural conditions that are difficult to reconcile with most existing channel business models.
The Channel Standard meets these conditions because we built the company around them from inception, not because we discovered them later and adapted. Channel Companion is the platform built under those conditions. This page is the disclosure of them.
We are not the only company that could in principle meet these conditions. We are the company that has chosen to organize around them and to publish that fact in a place that can be referenced and held to account.
If you have questions about anything described on this page, or believe something we have published is inaccurate or has changed, contact us at hello@thechannelstandard.com. We respond to substantive questions in writing and update this page when corrections are warranted.
If you are a supplier security team or compliance reviewer evaluating Channel Companion, request the platform’s security documentation through your point of contact at The Channel Standard, or contact us directly at the address above.
If you are an advisor or supplier who has experienced something on Channel Companion that does not align with the commitments published on this page, we want to hear about it. Email us at hello@thechannelstandard.com with the specifics.
This page was last updated April 21, 2026. Material changes to commitments are dated and the prior version is preserved.