Alluvial

• Name: Alluvial
• URL: https://alluvial.finance/
• Category: institutional staking software company / Liquid Collective integration operator / staking-workflow middleware vendor
• Tags: ethereum-ecosystem
• Summary: Alluvial belongs as an entity note, not a protocol note. Liquid Collective is the staking rail; Alluvial is the company selling the API, onboarding, reporting, account-mapping, and workflow layer around that rail, plus a broader staking-operations console through SMS. The leverage is in workflow defaults and integration control, not in new validator mechanics.
• What it does:
  • Sells enterprise APIs for platforms integrating Liquid Collective, including onboarding, reporting, accounting, and operational support
  • Maps institutional account structures into technical resources such as organizations, depositors, and wallets, with explicit custodial versus non-custodial and omnibus versus segregated handling
  • Publishes technical guides for ETH staking and LsETH redemptions that combine smart-contract interactions with offchain API calls
  • Offers Alluvial SMS as a staking-management system for institutions that want workflow automation, multi-operator coordination, multi-custodian setups, auto-compounding, and configurable staking strategies
  • Acts as the software-development and integration company around Liquid Collective rather than as the protocol itself
• Key claims:
  • The docs explicitly say Liquid Collective is the protocol while Alluvial is the software development company supporting that protocol’s development and ecosystem growth, which is the main taxonomy clue
  • The architecture docs are concrete about the real integration model, including how a platform’s internal account structure maps to Alluvial API resources and where signing responsibility lives in custodial and non-custodial flows
  • The staking and redemption guides show that Alluvial is not just brochure middleware; it exposes contract-call flows, redemption-status APIs, timing projections, and queue mechanics around LsETH
  • The enterprise APIs page says institutions can add Liquid Collective support within weeks and access onboarding, reporting, and accounting through Alluvial’s API layer, reinforcing the company’s role as integration middleware
  • The SMS product broadens the picture from liquid-staking integration into a more general institutional staking-control-plane story through multi-operator orchestration and configurable staking workflows
• Whitepaper: No standalone company whitepaper is the point here. The strongest source of truth is the official docs and product pages, with Liquid Collective docs needed to understand the protocol layer Alluvial wraps; see ../whitepapers/alluvial-primary-sources-2026-04-27.md.
• Sources:
  • https://alluvial.finance/
  • https://alluvial.finance/enterprise-apis/
  • https://alluvial.finance/sms/
  • https://docs.alluvial.finance/
  • https://docs.alluvial.finance/readme.md
  • https://docs.alluvial.finance/guides/supplemental_guides/architecture.md
  • https://docs.alluvial.finance/guides/supplemental_guides/staking.md
  • https://docs.alluvial.finance/guides/supplemental_guides/redemptions.md

Internal linkages

• Legacy project-layer alias preserved for old links: alluvial.
• Best adjacent reads: liquid-collective, stakewise, and figment.
• Keep the split clean: Alluvial is the workflow and integration company around the rail, not the staking rail itself.

Control surface

• The leverage is in onboarding, account mapping, approval flow, reporting, custody integration patterns, redemption handling, and which validator or liquidity paths SMS makes easy by default.

• Liquid Collective supplies the staking rail. Alluvial sells the workflow wrapper around it.

• Last reviewed: 2026-07-07 UTC