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

connection_stringstring

ConnectionString is the libpq DSN (URI or keyword form). When set, takes precedence over the structured fields below.

databasestring

hoststring

Structured connection fields. Used when ConnectionString is empty. Any blank field falls back to the matching PG* env var.

max_open_connsinteger

MaxOpenConns caps the size of the connection pool. Tune to your database's connection budget — small managed instances often cap at 30-100 total connections, so scaling to multiple orchestrator replicas requires sizing this down accordingly.

passwordstring

Password is the postgres credential; prefer the PGPASSWORD env var (or any libpq pgpass file) over committing this to YAML.

portinteger

schemastring

Schema selects the Postgres schema. Honoured regardless of whether ConnectionString or structured fields are used.

sslmodestring

userstring

types.StorePostgresConfig
{
  "connection_string": "string",
  "database": "string",
  "host": "string",
  "max_open_conns": 0,
  "password": "string",
  "port": 0,
  "schema": "string",
  "sslmode": "string",
  "user": "string"
}