SalexHub changes every day, and a marketing site falls behind. A feature gets renamed, a limit moves, a plan changes, and the page that described it stays as it was. We'd rather you learn what SalexHub does from this site than from a support ticket, so we hold the site to a few rules.
Only what's built, unless it says otherwise#
The rule is simple. If this site shows something as available, it should be built and running. Something we've planned but not built yet appears only with a "Coming soon" label, and only when an approved plan includes it. You'll see the label on the pricing page, on the Developers page and in the documentation. When we find something that breaks the rule, we fix the page.
Every docs page says where it was checked#
Each docs page records, in its source, the version of the product's code it was checked against and the files it was checked in. When the product changes, we know which pages to read again and what to check them against.
Some of it is checked by code. The site won't build if a docs page is missing a required field, links to a docs page or heading that doesn't exist, or is missing from the navigation. Blog posts get the same field and link checks, and a post that describes the product names the version of the code it was checked against. A few facts are also checked against their source by scripts: the prices against the catalog we bill from, and the webhook events and the number of tools in the registry against the product's code. A script fails when the site and the source differ.
Every security claim has a status#
The security page lists what protects your data, and each item says where it stands: live, or in staging. Below the list is what we don't claim yet. A page that listed only what's done would be shorter; we think this one is more honest.
Examples are made up#
The drawings and animations on this site show the product at work for made-up customers, such as Northwind and Fabrikam, with example addresses. They're illustrations, not screenshots of a real customer's organization. You won't find customer logos, quotes or usage figures here until they're real and we have permission to show them.
When we get it wrong#
We do. This site once said that every change in SalexHub goes through one registry of tools, and later named the wrong exceptions. The product's code shows that a few settings still save directly, so the pages now say that. One registry for the Agent, workflows and the API explains the difference.
If you find a claim here that the product doesn't back up, tell us. We'll fix the page, and we'd like to know.