Expanso Cloud
Expanso Cloud gives teams one place to build pipelines, choose where they run, and follow their operation across a fleet of edge nodes. Use the visual editor or YAML, test transformations before deployment, and roll out changes with health checks and rollback controls.
Production pipelines execute on Expanso Edge nodes. You choose the hosts, source systems, and destinations. Cloud manages configuration and orchestration and provides a shared view of pipelines, nodes, executions, and telemetry.
Start with your task
| Task | Guide |
|---|---|
| Set up your team and separate environments | Organizations and workspaces |
| Connect nodes and choose where pipelines run | Fleet management |
| Build, reuse, and test pipeline logic | Pipeline authoring and testing |
| Release a change gradually and recover a previous version | Deployments and rollback |
| Inspect throughput, errors, executions, and logs | Monitoring and troubleshooting |
| Configure team access and automation credentials | Access and API keys |
| Reference credentials from secret providers | Secrets and configuration |
| Get help building and fixing a pipeline | Pipeline assistant |
| Automate deployments and operate repeatable environments | CLI and delivery workflows |
| Understand workspace utilization | Usage and availability |
For a first deployment, follow the Cloud quickstart. For a terminal-based workflow, follow Deploy to Cloud.
How the pieces fit
An organization brings your team together. A workspace contains the nodes and pipelines for a particular environment or purpose. A pipeline describes what to read, how to transform it, and where to send it. An execution is a particular instance running on a node. A deployment tracks a pipeline release across its target nodes.
This separation helps operators answer distinct questions: what configuration should run, where it should run, whether the rollout is progressing, and whether each execution is healthy.
Data and configuration
The normal production record path runs from sources through your edge nodes to your configured destinations. Cloud also handles the information needed to manage those pipelines, including configuration, status, metrics, and requested logs. Testing and assistant workflows can send samples or configuration you provide to Cloud. Review the authoring workflow before using production records in a test or assistant conversation.
Available controls
The guides describe customer-facing controls. Some panels, including the secrets editor and usage reporting, appear only when enabled for your account. Pipeline rollout choices in the console are Rolling and Immediate. Follow the availability notes on each page and contact [email protected] when you need a control that is not visible.
