Sablier

• Name: Sablier
• URL: https://sablier.com/
• Category: Onchain token distribution / token streaming / vesting / airdrop infrastructure protocol
• Tags: ethereum-ecosystem
• Summary: Sablier is an onchain token-distribution protocol built around persistent, non-upgradeable smart contracts on Ethereum and other EVM chains. Its official materials describe four main systems—Lockup for vesting, Merkle Airdrops for onchain distributions, Flow for open-ended token streaming, and Bob for price-gated vaults—alongside a web interface, detailed docs, public code, audits, indexers, and even AI-agent skills for interacting with the protocol. Keep this note on the protocol rail; use sablier-labs when the real question is the official interface, deployment expansion, comptroller-admin workflow, or the company-run pricing and support shell around those contracts.
• What it does:
  • Provides smart-contract systems for fixed-term vesting, vested airdrops, open-ended payroll/grant streams, and price-gated token vaults
  • Publishes detailed technical docs, deployment references, governance/admin references, and contract-level documentation across protocol modules
  • Operates across Ethereum and multiple EVM chains, with official docs listing shared comptroller/admin structures and protocol deployments
  • Maintains public GitHub repos for the EVM monorepo, docs, indexers, SDK/deployment data, Solana work, audits, and AI-agent integrations
  • Exposes LLM-friendly documentation surfaces (llms.txt, protocol-specific bundles, .md doc variants) and agent skills for natural-language stream, vesting, and airdrop workflows
• Key claims:
  • Official docs define Sablier as “a powerful onchain token distribution protocol” built from “persistent, non-upgradeable smart contracts” that prioritize security, censorship resistance, and self-custody
  • The docs separate the overall protocol from the interface and the company, which is useful for understanding the trust model and what is actually onchain versus hosted by Sablier Labs
  • Official materials say Sablier currently consists of four systems—Lockup, Merkle Airdrops, Flow, and Bob—showing it should be cataloged as a multi-protocol distribution platform rather than a single “streaming payroll app”
  • Governance docs expose chain-by-chain comptroller and admin addresses, suggesting a comparatively transparent operational/control surface around protocol administration
  • The AI Agents guide and GitHub org show Sablier actively packaging its protocol for agentic workflows, including dedicated skills and LLM-oriented docs bundles
  • Public GitHub repositories show not just contracts and docs but also indexers, deployment metadata, Solana programs, and audits, which helps validate that the project ships meaningful infrastructure beyond a marketing site
• Whitepaper: No classic whitepaper or litepaper was found during this pass. The strongest primary materials were Sablier’s official docs index and concept pages, governance/admin docs, AI-agent guide, GitHub organization, EVM monorepo, and docs repository; see ../whitepapers/sablier-primary-sources-2026-04-25.md.
• Sources:
  • https://docs.sablier.com/llms.txt
  • https://docs.sablier.com/concepts/what-is-sablier
  • https://docs.sablier.com/concepts/governance
  • https://docs.sablier.com/guides/ai-agents
  • https://github.com/sablier-labs
  • https://github.com/sablier-labs/evm-monorepo
  • https://github.com/sablier-labs/docs
  • https://sablier.com/

Internal linkages

• Useful protocol-level neighbors: llama, safe, and openzeppelin-relayer.
• Company boundary for the official interface, deployment workflow, pricing shell, and comptroller-admin surface: sablier-labs.

Protocol / company boundary

• Keep projects/sablier on the durable token-distribution rail itself: the non-upgradeable contract systems, time-based vesting and payroll mechanics, Merkle airdrop construction, Bob’s price-gated vault logic, and the cross-chain deployment footprint of those protocol modules.
• Use sablier-labs when the practical question is who operates the official interface, packages organization-facing launch help, chooses where the branded deployment footprint expands, controls the docs and repo surface most teams inherit, or sits inside the documented comptroller-admin and fee-packaging workflow.
• That split matters because Sablier’s strongest protocol claim is immutability, while much of the operational reality most teams actually encounter still travels through a company-shaped shell above those immutable contracts.

Control surface

• At the protocol layer, the important leverage is in which modules a user adopts, what admin/comptroller hooks still exist around newer deployments, and how much trust is actually inside core contracts versus periphery workflow.

• The company note matters because official-interface defaults, Safe integration, fee sponsorship, deployment requests, docs distribution, and comptroller-admin workflow do not live cleanly inside immutable streaming contracts as a category.

• Read Sablier first as a durable token-distribution protocol, then ask whether the concrete operational question really belongs one layer up in sablier-labs.

• Last reviewed: 2026-08-08 UTC