Bacalhau

• Name: Bacalhau
• URL: https://bacalhau.org/
• Category: distributed compute orchestration framework / compute-over-data infrastructure / decentralized workload routing comparator
• Summary: Bacalhau is a compute-over-data orchestration framework, not a blockchain and not a generic GPU-marketplace note. The point is straightforward: it schedules jobs near existing data and exposes the real authority surface in orchestrators, admission policy, backend choice, and operator control.
• What it does:
  • Runs distributed jobs close to the data source instead of requiring large datasets to be moved first
  • Uses a single binary that can operate as client, orchestrator, or compute node depending on runtime mode
  • Supports multiple execution engines and storage backends, including Docker, WebAssembly, S3, HTTP/HTTPS, IPFS, and local storage
  • Supports several workload types, including batch, ops, daemon, and service jobs
  • Allows declarative job specs via YAML as well as imperative CLI submissions
  • Publishes results to local volumes or external storage systems such as S3
  • Markets the stack for log processing, distributed warehousing, fleet management, machine learning, and edge computing
• Key claims:
  • The official docs and README describe Bacalhau as an open-source distributed compute orchestration framework designed to bring compute to the data, which is the clearest reason to treat it as workload-routing infrastructure rather than as a classic crypto network primitive
  • Bacalhau emphasizes data sovereignty, security boundaries, and cross-organizational computation, which makes it analytically useful where crypto systems want decentralized execution without forcing raw data into one shared network
  • The architecture is explicitly orchestrator-plus-compute-node based, so practical authority likely concentrates in scheduler policy, node admission, permissions, and deployment topology more than in token economics or consensus design
  • The framework supports several job types and pluggable storage/execution layers, which suggests Bacalhau is a generalized control plane for distributed execution rather than a single-purpose ML marketplace
  • The official README says Bacalhau software is open source but that the Bacalhau product is produced exclusively by Expanso, Inc. and distributed under commercial terms, which is important because it introduces a vendor-control wrinkle into an otherwise open orchestration story
  • Compared with Lilypad, Bacalhau appears more like a general compute orchestration substrate and less like a crypto-economic verification-and-settlement layer, making it a useful baseline for asking when decentralized compute is really just better scheduling over heterogeneous infrastructure
• Whitepaper: No standalone Bacalhau whitepaper was located during this pass. The strongest primary materials were the official docs and repository README captured in ../whitepapers/bacalhau-primary-sources-2026-05-09.md.
• Sources:
  • https://bacalhau.org/
  • https://bacalhau.org/docs/
  • https://github.com/bacalhau-project/bacalhau
  • https://raw.githubusercontent.com/bacalhau-project/bacalhau/main/README.md

Internal linkages

• Best comparisons: lilypad for the more crypto-economic execution layer, fluence for the cloud-marketplace contrast, and aleph-cloud for the broader decentralized-cloud control-plane comparison.

Control surface

• The leverage sits in orchestrator topology, node and job admission, backend selection, and how much practical power stays with Expanso or the deployment operator.

• So treat Bacalhau as scheduling middleware over heterogeneous infrastructure, not as a neutral compute primitive.

• Last reviewed: 2026-05-26 UTC