Skip to content
Start free

How it works

Out over 443. Never in.

A probe and a collector at each site, agentless monitoring wherever it’s possible, and one outbound HTTPS connection to Ceburu. No inbound firewall rules to open, and no data lost when the WAN drops.

Start freeBook a demo

Ready to install? Read the getting-started guide (opens in a new tab)

The deployment

From your network to one portal.

  1. 01Your estate stays where it isApplications, servers, databases, network devices and log agents keep running as they are. Most of them need nothing installed at all.
  2. 02Telemetry lands at your edgeThe Ceburu Collector receives application, database and asset telemetry; the Log Forwarder receives logs. Both keep data on disk if the WAN drops.
  3. 03One probe per site, one way outThe Ceburu Probe runs discovery and commands and is the single egress point. End agents need no internet access — their installers come from the probe over the LAN.
  4. 04Out over 443. Never in.Everything connects out to Ceburu over HTTPS. Nothing in Ceburu’s cloud ever dials into your network, so there are no inbound firewall holes to open.
  5. 05Separated by tenant and siteCompanies contain regions or sites, each with its own data and keys, and only the modules enabled for that customer.
  6. 06See, understand, actSign in once through the Ceburu account portal and work from one portal: every module, AI Core, dashboards and automations.

Your site

ApplicationsOpenTelemetry
ServersWinRM · SSH · SNMP · vSphere
Databasesremote · read-only
Network devicesSNMP · vendor APIs
Log agentsFluent Bit

Site edge

Ceburu Collectorbuilt on OpenTelemetry
Log Forwarderwrite-ahead log
Ceburu Probeone per site · single egress

Disk buffers on the collector and forwarder hold data through WAN outages.

Outbound HTTPSport 443 only

Ceburu

Ceburu cloudmulti-tenant
Ceburu portalevery module + AI Core
  • Agentless where possible
  • Buffered through outages
  • Agents without internet
  • No inbound ports

By design

What your security team will ask first.

No inbound ports

Everything connects out over 443. Nothing in Ceburu’s cloud ever dials into your network.

Agents without internet

End agents talk only to the probe on your LAN, which also serves their installers.

Buffering through outages

The collector’s on-disk queue and the forwarder’s write-ahead log hold data until the WAN is back.

Agentless where possible

WinRM, SSH, SNMP and vSphere for servers; remote read-only queries for databases; discovery without credentials.

Install guides

Step-by-step, in the docs.

The documentation includes a Docs Assistant that explains each integration, checks prerequisites and helps you verify and troubleshoot the setup.

Get started

Start with one site.

Install a probe, connect out over 443, and see your first map and dashboards in the portal.

Sign upBook a demoRead the docs (opens in a new tab)

Already have an account? Sign in to the portal