Bacalhau primary sources — 2026-05-09

Notes

• Bacalhau is most usefully treated as compute-over-data orchestration infrastructure, not as a standalone blockchain or token-centered compute market.
• The important analytical surface is its orchestrator-plus-compute-node topology, modular execution/storage adapters, and the commercial-vendor layer sitting above the open-source software.
• No standalone whitepaper was located during this pass.

Primary sources reviewed

• https://bacalhau.org/
  • Official landing page for product framing and use-case positioning.
• https://bacalhau.org/docs/
  • Official docs overview describing Bacalhau as an open-source distributed compute orchestration framework designed to bring compute to the data.
• https://github.com/bacalhau-project/bacalhau
  • Official GitHub repository showing the maintained software surface and product framing.
• https://raw.githubusercontent.com/bacalhau-project/bacalhau/main/README.md
  • Raw README capturing the most concise description of architecture, integrations, job types, and licensing/commercial positioning.

Key takeaways captured for corpus

• Bacalhau’s core move is to schedule workloads near data rather than centralizing data before computation.
• The single-binary client/orchestrator/compute-node model makes deployment simple, but also highlights where operator control can concentrate.
• Bacalhau is explicitly modular across execution engines and storage providers, which makes it a generalized orchestration/control-plane layer.
• The official README’s distinction between open-source software and the Bacalhau product distributed by Expanso is analytically important because it reveals a meaningful vendor-control surface.
• Bacalhau is a strong comparison class for Lilypad-style decentralized compute because it helps separate pure job orchestration from crypto-economic verification and settlement claims.