Expanso primary-source snapshot

Fetched: 2026-08-11 UTC

1) Expanso homepage / control-plane framing

Source: https://expanso.io/

Selected excerpts from official materials:

Run pipelines on connected customer-controlled nodes.

Send Only Configured Outputs

Monitor node health, jobs, and executions from one control plane.

Control What Moves

Process pipeline payloads on customer-controlled nodes and send only configured outputs.

Additional signals from the same page:

  • The homepage is selling an operator-managed workflow around customer-controlled nodes, not only a library or standalone runtime
  • The one control plane framing is the clearest reason a company note is useful beside the Bacalhau project note

2) Expanso product page / managed entry path

Source: https://expanso.io/product/

Selected excerpts from official materials:

Control data at the source.

Expanso runs lightweight agents wherever your data is born.

They filter, transform, and route in place, so your warehouses, SIEMs, and lakes receive a smaller stream of governed records, not the raw firehose.

Try Expanso

Additional signals from the same page:

  • The product page puts lightweight agents and company-managed workflow ahead of any protocol or framework branding
  • The destination framing is enterprise data plumbing, which helps separate the entity note from a generic decentralized compute project note

3) Expanso docs homepage / managed SaaS claims

Source: https://docs.expanso.io/

Selected excerpts from official materials:

Expanso enables you to deploy and orchestrate data pipelines from edge to destination through a unified control plane.

Expanso is a managed platform for deploying intelligent data pipelines at the edge:

Managed SaaS: Central control plane with automatic agent updates.

Enterprise Governance: PII masking, policy enforcement, and compliance audit trails.

Sign up for Expanso Cloud (free tier available)

Additional signals from the same page:

  • The docs make the company boundary explicit: managed platform, Expanso Cloud, and automatic agent updates are all operator-shaped trust surfaces
  • Governance, audit, and policy language matter because they shift the practical dependency from raw job execution to company-defined workflow controls

4) Expanso about page / company identity

Source: https://expanso.io/about-us/

Selected excerpts from official materials:

Expanso brings policy-driven pipelines to the edge, processing data before costly centralization.

We Solve the Distributed Data Problem

Built by leaders behind Kubernetes, Amazon Web Services, Google Cloud, Microsoft Azure, Kubeflow, and global compute platforms.

Security First

Open Innovation

Additional signals from the same page:

  • The about page is useful because it is explicit about the company trying to own a broader distributed data problem category rather than only one tool surface
  • Leadership and investor framing reinforce that this is a real operating company boundary, not a loose open-source collective

5) Bacalhau README / open framework baseline

Source: https://raw.githubusercontent.com/bacalhau-project/bacalhau/main/README.md

Selected excerpts from official materials:

Bacalhau is an open-source distributed compute orchestration framework designed to bring compute to the data.

Orchestrator-Compute Model: A dedicated orchestrator coordinates job scheduling, while compute nodes run tasks

This repository contains the open-source Bacalhau software, covered under the Apache-2.0 license except where noted.

Commercial terms are not required to use, modify, or distribute this code under that license.

Additional signals from the same source:

  • The current README is a useful counterweight to the managed-company framing because it keeps Bacalhau legible as an open framework on its own
  • That makes the taxonomy split cleaner: projects/bacalhau for the orchestration mechanism and companies/expanso for the named operator and managed-control-plane shell around adjacent commercial packaging

Notes

  • This snapshot was created to support a new companies/expanso note and a project/company boundary refresh for projects/bacalhau.
  • The practical distinction is: Bacalhau for open compute-over-data orchestration mechanics; Expanso for the company-run control plane, governance packaging, and managed agent workflow.