Skip to content

Platform

Collect every signal once and use it everywhere

Tracix gathers application, infrastructure, network and security telemetry with one OpenTelemetry-native collector, stores it in a workspace that belongs to you alone, and gives every team the same data to explore, alert on and automate.

How it fits together

Telemetry flows in one direction. Control flows back.

  • Telemetry
  • Configuration and jobs
Your estate sends telemetry to the Tracix Collector over OTLP, SNMP, flow and log protocols. The collector exports it to your isolated workspace, where you query it to analyze and act. Policies, signed configuration and network configuration jobs flow back from the workspace to the collector.
  1. Sources

    Your estate

    • Applications and services
    • Hosts, containers, Kubernetes
    • Routers, switches, firewalls
    • AWS, Azure and GCP accounts
    • Browsers and mobile apps
  2. Collect

    • Receivers for every signal
    • Processors and enrichment
    • Discovery for devices and clouds
    • Exporter to your workspace
    • Linux, macOS, Windows, Kubernetes, Docker
  3. Store

    Your isolated workspace

    • Dedicated ClickHouse cluster
    • Own namespace and hostname
    • Pipelines and lifecycle rules
    • Hot and cold storage tiers
  4. Use

    Analyze and act

    • Explorers and dashboards
    • Monitors, SLOs and problems
    • Brain investigations
    • Workflows and approvals
    • Network configuration changes

Product areas

Everything on one data plane

The foundation under every area

  • Tracix Collector

    An OpenTelemetry Collector distribution with fleet management. About the collector

  • Pipelines

    Parse, enrich and filter telemetry in the collector, then expire it with lifecycle rules.

  • Dashboards

    Explorers for logs, metrics and traces, and dashboards you can share read-only.

  • Isolated workspaces

    Every workspace gets its own namespace, ClickHouse cluster and hostname, on every plan.

  • Integrations

    OTLP, Prometheus, SNMP, NetFlow and cloud APIs. Browse integrations

  • APIs and as code

    Monitors, dashboards and detection rules kept in Git, and scoped API keys for CI.

Why one platform

Three tool categories, one workspace

Most teams run an APM suite, a network monitoring tool and a security product, each with its own agent and its own copy of the inventory.

CapabilityTracixAPM-first suitesNetwork toolsSecurity tools
APM, logs and metricsIncludedCorePartialLogs only
SNMP devices, flows and topologyIncludedOften an add-onCoreNot offered
Network configuration managementIncludedRarely offeredOften a separate productNot offered
Software inventory, SBOM and attack pathsIncludedSeparate productNot offeredCore
OpenTelemetry collector with fleet managementIncludedVariesRarelyRarely
Isolated database per customerEvery planTop tier, where offeredVariesVaries

Category descriptions reflect typical public product packaging as of [review date]. Individual vendors vary.

Deployment

Fully managed, with the database choice that suits you

  • Tracix Cloud

    All plans

    We run the platform. Each workspace gets its own Kubernetes namespace, ClickHouse cluster and hostname.

    • Provisioned in about four minutes
    • Releases and upgrades handled for you
    • Custom domains from Starter, SSO from Professional
    • Hosted on AWS in us-east-1
    Create a workspace
  • Bring your own ClickHouse

    Option

    Already run ClickHouse? Create a workspace on a cluster you operate, reachable over HTTPS. Tracix runs the application, and your telemetry stays in your database.

    • Your cluster, storage and backups
    • Chosen when you create the workspace
    • The same Tracix application

    Cold storage tiers, high availability and read-only SQL need the managed database.

    Talk to sales
  • OpenTelemetry conventions first

    Official semantic convention names wherever they exist, and Tracix names only where OpenTelemetry has none.

  • Upstream SDKs, no wrapper

    Instrument with the SDKs and agents the OpenTelemetry project publishes. There is no proprietary SDK to adopt.

  • Monitors and dashboards as code

    Keep definitions in Git and apply them from a reviewed plan, like any other code.

  • Notifications where you work

    Route alerts to Slack, Microsoft Teams, PagerDuty, Opsgenie, webhooks or email, with on-call escalation.

Start with one signal. Add the rest when you are ready.

Begin on the Free plan with one workspace, then move to a larger plan as more teams and signals come on board.