If it has an API and an auth method, we can connect to it

CloudMonitor isn't locked to Azure/AWS/GCP — the same scanner-and-normalize pattern works for any system that exposes data through an authenticated API.

The connectors in the box — Azure, Microsoft 365, AWS and GCP (the last two in Beta), Kubernetes, MuleSoft and Docker, with a set of SaaS platforms still marked coming soon — cover the bulk of what most teams run. But the underlying CloudMonitor architecture — scanner pulls metadata, normalizes into a common resource & finding model, runs rules, renders in the dashboard — doesn't care about the source. If a system has an authenticated API, we can build a connector for it. Custom connectors are built to order; none has shipped to a customer yet, so read this as how we would do it rather than a catalog.

What "we can connect to it" means concretely

What it does not mean: there is no on-premises agent and no private-network link today, so a system that is only reachable from inside your network is out of reach for now.

The pattern

  1. You give us API docs (or point us at OpenAPI / Swagger) and a sample read-only credential.
  2. We map the resource model into our normalized schema (the same Resource + Finding model the Azure / AWS / GCP connectors use).
  3. We write a small scanner module that runs on the same schedule as the built-in ones.
  4. It is enabled for your tenant first; whether it is ever offered to other customers is your call.

Examples of what a custom connector could surface

What we won't do

If you have a system in mind and want to know if it fits, the fastest path is to get in touch and send the API docs.

← Back to all posts