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.JobStatus

created_atstring

CreatedAt is the time when the job was created

deployment_idstring

DeploymentID is the ID of the active deployment for this job. Empty if there is no active deployment.

revisioninteger

Revision is a per-job monotonically increasing revision number that is incremented on each update to the job's state or specification. This includes both user-initiated changes (which also increment Version) and system-initiated changes (status updates, state transitions, etc.). Revision >= Version always.

state object

State represents the current state of the job

details object

Details is a map of additional details about the state.

property name*string

messagestring

Message is a human readable message describing the state.

state_typetypes.JobStateType (string)

StateType is the current state of the object.

Possible values: [``, pending, queued, running, completed, failed, stopped, deleted]

updated_atstring

UpdatedAt is the time when the job was last updated

versioninteger

Version is a per-job monotonically increasing version number that is incremented on each job specification update. Version tracks changes to the job specification (user-defined fields like runtime, deployment settings, etc.). Compare with Revision which tracks ANY change including status updates.

types.JobStatus
{
  "created_at": "string",
  "deployment_id": "string",
  "revision": 0,
  "state": {
    "details": {},
    "message": "string",
    "state_type": ""
  },
  "updated_at": "string",
  "version": 0
}