Deployment

MrProbe, by QDEX Consulting (Chennai, India), is an enterprise AI agent assurance platform for red teaming and functional evaluation.

There are two deployment stories, and they are not the same path. The hosted app at mrprobe.ai and app.mrprobe.ai is where a customer signs in, registers an agent, and runs LENS campaigns. The API host for that app is api.mrprobe.ai.

ATC is the control path for calls after an agent is in use. The homepage states that the self-hosted ATC path keeps prompts, logs, and the ledger in the customer cluster, with no egress on that path. Planes named on the homepage are GKE, EKS, AKS, on-prem, and air-gapped.

Putting ATC in a cluster is a deployment project. It is not turned on by creating a Free account. Enterprise catalogue flags include SSO and RBAC. A team that needs a private network path should start from the contact page and the ATC page, not from an assumption that every tier ships a cluster installer.

CI/CD is a flag on Starter, Professional, and Enterprise in the billing catalogue. It is off on Free. The integration route inside the app is /integrations/cicd and it requires a signed-in user. This marketing URL only describes that the gate exists.

Docs for the first hosted-app setup are at /docs/getting-started. This page does not move documentation off docs.sniffr.ai. No redirect is published until those old URLs are confirmed as MrProbe docs.

Ask which path you need before you buy. A team that only wants a hosted campaign can start on the app and stay there. A team that must keep prompts inside its own network is talking about ATC in the cluster, which is a deployment project with its own network rules. Write down the host names you will use, who can see reports, and whether CI should block a build. Then use the contact page if the catalogue tier does not match that design. The security contact for this website is support@mrprobe.ai. Do not treat a Free account as a cluster install. Those are different jobs. Write the decision down before the install starts so the team agrees.

Security headers on this website include HSTS. The domain is not being submitted to the HSTS preload list from this change. Preload is hard to undo, and the edge in front of the site already sends a preload token that should be reviewed before anyone submits the domain.