Yes. Sleuth treats monorepos like any other repo setup.
Currently, the way to represent your environments in Sleuth is to model them as projects. Create a new project for each environment, such as staging, production, development, etc., and then map change sources, deployments, feature flags, etc., to each environment individually.
More information about how environments are represented in the Sleuth Information Architecture is available on the Terminology page.
Someone on your team might have already created a Sleuth project, and connected integrations already. Instead of creating a new account and project from scratch, you can join their organization, which can be your team or your company. If your email address domains match, you can automatically connect to their environment, which will give you access to all their projects and integrations.
Sleuth uses an open source anomaly detection tool to perform its impact source reporting. When you deploy, Sleuth immediately starts analyzing the information received from your integrated tools. Of course, the more tools you have means that Sleuth has more information to process, which will give you a much clearer picture of how healthy or unhealthy your deploys are. For example, with a Datadog integration you can set the baseline of the reported metrics and then configure Sleuth how to process any deviations; for example, less 500 errors are better than more.
Yes! Sleuth uses Tawk.to for chat support. Look in the lower-right hand corner of your Dashboard and click on the Tawk.to icon to get instant chat support (available Monday thru Friday, 8 am to 5 pm PST).
You can get detailed pricing and purchasing information on the Purchasing page.