Choose an integration path
Use a direct gVault integration when users should deposit into an existing Ground gVault and hold its shares in their current wallets. Your backend uses the Ground API only to manage deposit access. Deposits, withdrawals, and share accounting happen onchain. Use a fee wrapper when your application needs a performance fee, designated fee recipient, or a customer allowlist isolated from the underlying gVault. Ground provisions the wrapper, but the underlying gVault already exists.POST /v2/fee-wrappers provisions a fee wrapper over an existing gVault. It
never creates the underlying gVault.Integrate directly onchain
Allowlist EVM addresses and interact with an existing Ground gVault.
Configure revenue sharing
Provision a fee wrapper around a gVault and configure its performance fee.
Start building
gVault quickstart
Complete a sandbox integration from discovery through the first deposit.
Understand the model
Learn how gVaults, fee wrappers, addresses, shares, and API resources fit together.