What is Expanso and how does it work?

Expanso is a managed platform for deploying intelligent data pipelines at the edge. It processes data where it's generated - reducing bandwidth, latency, and costs. You deploy lightweight agents on your infrastructure, build pipelines using our visual builder or YAML, and control everything from a central SaaS platform.

Can I run AI/ML models directly in my data pipelines?

Yes! Expanso supports running ONNX, TensorFlow Lite, and other models as native pipeline steps. Execute low-latency inference on streaming data, enrich events with model outputs (like risk scores), and make decisions at the edge without cloud round-trips.

How many pre-built components are available?

Expanso provides 200+ pre-built components including inputs (Kafka, HTTP, files), processors (transformations, filtering, PII masking, aggregations), and outputs (S3, Snowflake, Datadog, Splunk). Browse the complete catalog in our Component Reference.

Do I need to write code to build pipelines?

No - use our drag-and-drop visual pipeline builder to create sophisticated pipelines without code. For advanced use cases, you can also write pipelines in YAML or use the Bloblang transformation language for complex data mappings.

How does Expanso help with data governance and compliance?

Expanso includes built-in governance features: automatic PII detection and masking, policy enforcement at the edge, RBAC, SSO integration, and comprehensive audit trails. Mask sensitive data before it ever leaves your network.

types.DeploymentSpec

auto_promoteboolean

Auto-promote canary deployments

canary_countinteger

Canary-specific settings

canary_percentinteger

Percentage of canary nodes

health_check object

HealthCheck defines health check configuration (required for rolling/canary, ignored for immediate)

deadlinestring

Deadline is the maximum time to wait for an execution to become healthy (required) Example: "5m", "30s"

max_error_ratenumber

MaxErrorRate is the maximum error rate allowed during health checks (optional, default: 0.10) Example: 0.10 = 10% error rate

min_healthy_timestring

MinHealthyTime is the minimum continuous healthy duration required (optional, default: "30s") Example: "30s", "1m"

max_failed_nodesinteger

MaxFailedNodes is the maximum number of failed nodes before stopping (optional, default: 10)

max_failed_nodes_percentnumber

MaxFailedNodesPercent is the maximum percentage of failed nodes before stopping (optional, default: 10.0)

max_parallelinteger

MaxParallel is the maximum number of nodes to update in parallel (0 = all at once)

no_auto_rollbackboolean

NoAutoRollback disables automatic rollback on deployment failure (default: false = auto-rollback enabled)

strategytypes.DeploymentStrategyType (string)

Strategy: immediate|rolling|canary

Possible values: [immediate, rolling, canary]

types.DeploymentSpec
{
  "auto_promote": true,
  "canary_count": 0,
  "canary_percent": 0,
  "health_check": {
    "deadline": "string",
    "max_error_rate": 0,
    "min_healthy_time": "string"
  },
  "max_failed_nodes": 0,
  "max_failed_nodes_percent": 0,
  "max_parallel": 0,
  "no_auto_rollback": true,
  "strategy": "immediate"
}