StakeWise Labs

• Name: StakeWise Labs
• URL: https://stakewise.io/
• Category: staking-infrastructure company / vault-and-validator workflow operator / white-label liquid-staking entity
• Tags: ethereum-ecosystem
• Summary: StakeWise Labs belongs in companies/ because StakeWise’s own docs now separate Protocol, Interface, DAO, Labs, and the current institution-facing control story is not exhausted by immutable vault contracts. The sharper question is who publishes the main interface, packages the easiest vault-deployment path, runs the operator-service and institutional workflow, curates the marketplace/default experience around operators and UI, and sells the white-label staking stack used by partners like MetaMask and Chorus One. Those levers sit with StakeWise Labs more clearly than with the abstract protocol note.
• What it does:
  • Acts as the core development team behind StakeWise Protocol and its ecosystem tools
  • Packages the web interface and institution-facing deployment path around the underlying protocol
  • Markets white-label staking infrastructure where partners can deploy custom pools, choose operators, and ship a branded UI or API surface with limited engineering work
  • Frames a marketplace model in which deployers choose from StakeWise-linked operators or run their own infrastructure
  • Sits above the protocol as the named organization shaping the easiest path into vault creation, vault operations, and partner-facing staking products
• Key claims:
  • The StakeWise docs overview explicitly splits the stack into Protocol, Interface, DAO, Labs and describes StakeWise Labs as The core development team behind StakeWise Protocol and its ecosystem tools, which is strong first-party evidence that the company boundary is real rather than inferred
  • The institutional page markets enterprise-grade staking infrastructure and says deployers can Customize permissions, fees, and validator settings, Choose from our marketplace of operators or run your own, and Deploy with our API or ready-to-use interface, which makes the company-run packaging shell analytically distinct from the protocol contracts
  • The operator introduction says anyone can create a Vault via app.stakewise.io, that StakeWise infrastructure already powers staking solutions deployed by MetaMask and Chorus One, and that operators can launch a white-label staking product powered by StakeWise smart contracts; that is exactly the sort of named operator-and-distribution boundary the companies/ layer is meant to capture
  • The same operator docs say both Regular and MetaVaults rely on the Operator Service to automate day-to-day Vault operations, which makes the operating workflow and service shell matter separately from the immutable vault contracts
  • The homepage keeps pushing the combination of curated by our partners and powered by StakeWise, vaults curated by our partners, DVT-backed validator diversity, and the broader staking community story, reinforcing that the practical adoption path is shaped through a company-run product shell rather than only through permissionless contracts
  • The v3-core repository README still presents governance controls, validator management, keepers, and MEV-management components as part of one modular system, which is useful because it shows how much implementation and integration gravity still flows through the StakeWise-maintained software stack
• Whitepaper: No standalone company whitepaper is the point here. The strongest primary materials for this split were the official overview, institutional page, operator docs, homepage, and the main protocol repository snapshot collected in ../whitepapers/stakewise-labs-primary-sources-2026-08-10.md.
• Sources:
  • https://stakewise.io/
  • https://stakewise.io/institution
  • https://docs.stakewise.io/docs/overview
  • https://docs.stakewise.io/operator/introduction
  • https://raw.githubusercontent.com/stakewise/v3-core/master/README.md

Internal linkages

• Protocol-layer note: stakewise.
• Useful adjacent staking-operator company reads: alluvial, figment, kiln, and chorus-one.
• Helpful contrast for another company-versus-protocol split in staking infrastructure: p2p-org.

Protocol / company boundary

• Keep stakewise on the deployed product and mechanism surface: vault types, osToken, operator selection inside vaults, MEV handling, validator lifecycle logic, and how stake-routing policy becomes a live control surface.
• Use this company note when the sharper question is who packages the main interface, who sells the institutional deployment path, who steers operator-marketplace and white-label workflow, and who maintains the ecosystem tooling users and partners are most likely to inherit.
• That split matters because how do StakeWise vaults work? and which organization shapes the easiest production and partner path into those vaults? are related but not identical questions.

Control surface

• Practical leverage here is not absolute control over all vaults. The better read is that StakeWise Labs controls the reference interface, institutional packaging, partner-facing deployment path, operator-service workflow, and much of the software and documentation gravity around the protocol.

• That matters because staking products often centralize through defaults, UI distribution, validator-marketplace curation, and operational services long before they centralize through contract ownership.

• Read StakeWise Labs when the question is about white-label deployment, partner distribution, interface and API packaging, or the named team shaping the operational path most institutions and integrators will actually use.

• Last reviewed: 2026-08-10 UTC