FAQs

Yes, Distr can be white-labeled with your branding, providing a consistent experience for your customers and making the platform appear as an extension of your product suite.

Yes. Distr’s Docker-based controller can run inside a WSL2 Linux distribution on Windows. See the Windows WSL2 guide for the Distr-specific setup, Docker checks, and Windows port forwarding steps.

No, there is no way to toggle between the Vendor and Customer views. If a vendor wants to manage their own deployments, they can do so using the Deployments tab within the Vendor Portal. The Customer Portal is only accessible to end-customers who have been onboarded by a software vendor. After onboarding, the customer will receive an email to set their credentials. Once the credentials are set, the end-customer can access the Customer Portal.

Not by default. The Distr controller only connects outbound to Distr and gives you no way into the customer’s infrastructure. Logs, metrics and support bundles cover most support cases. When they do not, and the customer agrees, you can deploy Tailscale or a Cloudflare Tunnel as a Distr application next to your application and undeploy it once the case is closed. See Remote Access for Debugging.

Yes, definitely. If you want to simulate a target environment by running a container hosting emulator like Docker Desktop on your macOS machine, check out this short guide. It covers the configuration steps needed to ensure Distr can communicate with the Docker daemon.