Gauntlet

• Name: Gauntlet
• URL: https://www.gauntlet.xyz/
• Category: DeFi risk-management company / vault-curation operator / yield-integration infrastructure company
• Summary: Gauntlet belongs as an entity note, not a protocol note. The useful question is who curates the vault menu, operates the guardian and monitoring workflow around Aera-powered vaults, packages the SDK/API layer developers integrate, and compresses allocator judgment into an institution-facing yield product. The practical leverage sits in company-run curation, exposure limits, guardian operations, and integration defaults rather than in a standalone neutral protocol boundary.
• What it does:
  • Sells the Gauntlet Developer Kit, an SDK/API/developer-portal stack for integrating curated vault access, deposits, withdrawals, positions, attribution tracking, and revenue-sharing flows into applications
  • Curates institutional-grade vault strategies and market-allocation sets across protocols and chains rather than exposing raw DeFi markets without opinionated selection
  • Runs offchain risk systems that monitor market conditions, protocol health, and portfolio exposures, then informs guardian operations around Aera-powered vaults
  • Operates as the guardian for Aera vaults in the official security model, with onchain hooks and constrained roles intended to bound but not eliminate Gauntlet’s operating influence
  • Packages risk tiers, market selection, concentration limits, and rebalancing logic into a product surface that downstream apps can inherit with a single integration
  • Publishes machine-consumable docs, contract references, and API surfaces that make Gauntlet’s allocator judgment easy to embed as default yield infrastructure
• Key claims:
  • The docs describe the Gauntlet Developer Kit as the easiest way to integrate with DeFi yield and position it as a single SDK/API layer above Gauntlet Vaults and infrastructure
  • The overview page says developers get a single API to access, compare, and interact with yield opportunities across all Aera and Gauntlet vaults, which is useful because it frames Gauntlet as a distribution and curation shell over underlying venues rather than only as a research brand
  • The security docs say Aera is built and operated by Gauntlet and that Gauntlet operates as the guardian for Aera vaults, which is the clearest primary-source statement that real operating authority sits with the company layer
  • The same security docs say strategy quality depends on Gauntlet’s off-chain risk analysis and that guardian liveness is required for active management, which makes the company-run operating boundary analytically more important than the nominal vault protocol label
  • The curation docs say Gauntlet actively decides which DeFi markets a vault can deploy into, how much capital goes to each, and under what conditions allocations change, making allocator judgment and market admission part of the real control surface
  • Official materials also emphasize monetizable attribution tracking and fee-recipient configuration, which matters because integrations inherit not just vault access but Gauntlet’s distribution and economics shell
• Whitepaper: No separate company whitepaper is the important artifact here. The strongest primary materials were Gauntlet’s official docs, security and curation pages, developer-kit overview, Aera-V3 integration materials, and API surface references already captured in ../whitepapers/gauntlet-primary-sources-2026-04-25.md.
• Sources:
  • https://www.gauntlet.xyz/
  • https://docs.gauntlet.xyz/
  • https://docs.gauntlet.xyz/llms.txt
  • https://docs.gauntlet.xyz/guides/concepts/security
  • https://docs.gauntlet.xyz/guides/concepts/curation
  • https://docs.gauntlet.xyz/guides/concepts/supported-protocols/aera-v3/overview
  • https://docs.gauntlet.xyz/openapi.json

Internal linkages

• Protocol substrate beneath the company layer: aera.
• Strongest adjacent operator-risk read: chaos-labs.
• Useful allocator and vault-policy contrast: morpho and pendle.
• Project-layer alias: gauntlet.

Protocol / company boundary

• There is no especially clean standalone Gauntlet protocol doing the main analytical work here.
• The underlying vault substrate is Aera, while the market curation, guardian operation, monitoring, SDK/API packaging, and developer-facing revenue/attribution shell are explicitly run by Gauntlet.
• That is why this note belongs in companies/: the practical question is who decides which markets are admissible, who manages allocations inside bounded rails, who packages the easiest integration path, and whose offchain risk process users are really trusting.

Control surface

• Practical leverage sits in vault admission and curation, risk-tier definitions, market-selection criteria, concentration and correlation limits, guardian operations, offchain monitoring, and the SDK/API defaults downstream apps adopt.

• Even with onchain hooks constraining execution, Gauntlet remains the operating layer deciding what counts as acceptable yield exposure, when allocations should change, and how integrators discover and route into vaults.

• Read Gauntlet as a company-run allocator, curation, and integration control plane around Aera-powered vaults, not as a neutral protocol primitive.

• Last reviewed: 2026-08-06 UTC