Architecture
Understand how Expanso's control plane and edge nodes work together.
System Overview
Expanso Control Plane
The central management interface hosted at cloud.expanso.io.
Responsibilities:
- Pipeline creation and configuration
- Node deployment and monitoring
- Metrics aggregation and visualization
- User authentication and authorization
- Network management
You don't run this - it's a managed service provided by Expanso. Enterprise customers can run an on-prem orchestrator.
Edge Nodes
The runtime that executes pipelines on your infrastructure.
Characteristics:
- Lightweight binary (150MB)
- Runs on Linux, macOS, Windows
- Connects to control plane (Expanso Cloud or local orchestrator) over TLS
- Executes one or more pipelines
- Reports metrics and health
Deployment locations:
- Bare metal servers
- Virtual machines
- Docker containers
- Kubernetes pods
- IoT devices and gateways
Data Flow
Where Data Lives
Edge nodes:
- Read from local data sources
- Process data locally
- Write to local or cloud destinations
Expanso Control Plane:
- Stores pipeline configurations
- Receives metrics and health data
- Does NOT process your data
Your sensitive data never goes through the Expanso Control Plane - it flows directly from edge sources to edge destinations.
Communication
Node → Control Plane:
- TLS-encrypted connection
- Sends: metrics, health, logs
- Receives: pipeline configs, commands
Data → Data:
- Direct connection from source to destination
- No intermediary (unless you configure one)
- Full control over data routing
What's Next?
👉 Core Concepts - Overview of key concepts
👉 Quick Start - Deploy your first pipeline
👉 Build Your First Pipeline - Step-by-step tutorial