What a Node is (control vs data plane)
A SupremeTracking Node is the tracking engine installed on infrastructure you control. It receives events, translates them into the canonical Supreme Event Payload, persists them locally, and forwards them through the integrations you enable.
That boundary is the foundation of the product: customer events and PII do not travel through Supreme's SaaS System.
The three planes
| Plane | Where it runs | What it does |
|---|---|---|
| System - control plane | Supreme infrastructure | Owner verification, Plans, Licenses, billing, release distribution, and integration catalog metadata |
| Node - data plane | Your infrastructure | Event ingestion, canonical normalization, local persistence, and integration forwarding |
| Console - observability | Your browser | Connects to your Node and shows health, events, logs, and configuration |
The Console may also contact the System for control-plane concerns such as access. It does not route your marketing events through the System.
What the Node owns
The Node owns the operational event path:
- Receive a browser event or webhook.
- Translate it to the canonical event shape.
- Run Filter, Validation, Enrichment, Persistence, and Forwarding.
- Keep the resulting event data on the Node.
- Expose operational views to the Console directly.
Read The canonical event payload for the contract between sources, the pipeline, and destinations.
What the Node does not own
The Node does not decide who the Owner is, which Plan was purchased, how billing works, or whether a License grants access. Those are control-plane responsibilities.
A License is the authority that connects an Owner, a Node, and a Plan. The Node remains blind to licensing logic: it does not activate, validate, persist, or interpret Licenses or Plans.
This separation prevents a tracking hot path from becoming dependent on a remote billing or account service.
Zero-knowledge operation
"Zero-knowledge" here means the Supreme System is outside the client event path. Your Node processes conversion data on your infrastructure, and the browser-based Console reads it from that Node.
It does not mean that every destination receives no data. When you enable an integration, the Node forwards the canonical event fields that its self-contained handler maps to that platform. You control the Node, its credentials, and the active modules.
Learn how that boundary continues into destinations in Integrations overview.
Operational responsibilities
After deployment, keep these parts healthy:
- The Node domain resolves over HTTPS.
- The database connection works.
- The Node identity matches the installation you intended to register.
- The Loader and ingestion path are reachable.
- The Master Key remains private.
- Integration modules and credentials are configured on the correct Node.
To start using a new installation, follow Node installed, what's next? and then log into the Console.