Polymarket vaults
Turn strategies into investable products.
Build managed prediction-market vaults with connected deposits, allocation controls, execution, and reporting for managers and participants.
The building blocks
Everything connects.
Make it your own.
Connect the asset and investor lifecycle.
Inside the product
Managed white-label
We run cycle ops, custody, and strategy. You ship a branded vault product to your users — landing pages, deposit flow, dashboards, and statements under your name on your domain.
- Branded UI on your subdomain
- We operate cycles end-to-end
- Partner share of fees per contract
- Fastest path: weeks to first deposit
No upstream dependency
Our wallet contract has no dependency on Polymarket’s factory or whitelist. Only our governance can authorize upgrades. Polymarket cannot upgrade, brick, or recover wallets your users deposit into.
ERC-4626 on day one
Standard tokenized-vault shares. Every existing piece of DeFi tooling — portfolio trackers, allocator strategies, on-chain accounting — works with your branded vault without integration work.
On-chain track record
Every deposit, deployment, trade settlement, and terminal liquidation is publicly verifiable. Track record is reconcilable to the cent — the proof your users will ask for.
Polymarket vaults
Ready to build with this?
Tell us what you have in mind. We’ll help scope the right approach.
Behind your experience
Your product, up front.
The connections, handled.
Choose the components your product needs. Keep the customer experience and operating controls in one connected flow.
Your experience
Polymarket vaults
Connected outcomes
Availability, providers, and supported workflows are scoped to your product and operating requirements.
Plan your integrationThe possibilities
From an opportunity to an investment experience.
Explore the products and use cases that connect to this stack.
Go a little deeper
Built around the details.
Explore the workflows, components, and implementation considerations behind the experience.
Points
Your users want exposure
Polymarket is the largest prediction-market venue in crypto. Deterministic settlement, persistent mispricing, uncorrelated returns. Your users would allocate — if you offered the wrapper.
The wrapper is the hard part
Capturing the alpha requires a 24/7 operation, but offering it to users requires a custody-grade vault, an ERC-4626 share model, fund-style cycles, and an audit trail. That stack doesn’t exist off the shelf.
You don’t want to build it
Smart-wallet factory, TEE custody, vault contracts, cycle ops, terminal liquidation logic — months of audit and integration before your first deposit. We already did that work.
Core components
Closed-end ERC-4626 vaults
Standard tokenized-vault shares your product can wrap, report on, and surface in any portfolio tracker. Each vault is one fixed-term cycle — deposit, lockup, terminal liquidation, redeem.
- Plug-and-play with portfolio trackers and aggregators
- On-chain accounting, no integration work
- Deterministic deposit and redemption windows
- Composable with the rest of DeFi on day one
Self-custodied smart wallet
Each cycle deploys a fresh wallet contract from our own factory. We wrote it. We audited it. We control its upgrade path. Polymarket cannot upgrade, brick, or recover wallets your users deposit into.
- Independent factory — not Polymarket-controlled
- Fresh keypair per cycle, blast-radius contained
- Cold-key pause-and-sweep recovery built in
- Upgrade path governed by us, not the venue
Policy-enforced custody
Keys live inside Turnkey’s TEE. Cold owner keys require an N-of-M approver quorum to sign. Hot operator keys are scoped, rate-limited, and time-bounded — enforced inside the TEE, not in our application code.
- TEE-enforced policy, not app-layer guards
- N-of-M quorum for cold-key signatures
- Domain-locked, rate-limited hot operators
- Compromise of one layer contained by the next
Implementation workflow
Deposit window opens
A new cycle opens on your branded surface. Typically 1–2 weeks.
Users deposit pUSD
Your users send pUSD to the vault contract. They receive ERC-4626 shares at 1:1.
Capital deploys
Window closes. Fresh wallet, fresh keypair, scoped operator. Strategy starts.
Cycle runs
Typical term is 4–8 weeks, configurable per vault you ship.
Terminal liquidation
All positions liquidate to pUSD. Terminal NAV is fixed and on-chain.
Pro-rata redemption
Users burn shares for pUSD. No queue, no liquidation discount, no operator discretion.
Whose brand is on the product end-users see?
Yours. White-label, SDK, embed, and co-managed deployments all surface under your brand on your domain or inside your app. We are the infrastructure layer — invisible to end users unless you choose to disclose us.
Who owns the LP relationship and customer data?
You do. Partners own KYC, onboarding, and the LP relationship. We provide vault contracts, custody, and reporting APIs. End-user identifiers stay in your stack.
How do fee splits work?
Enforced on-chain at the vault contract level. Standard split is partner / operator / platform; the exact basis points are configurable per cycle. No off-chain reconciliation, no trust assumption between parties.
Managed vs BYO strategy — which surfaces support which?
White-label is managed by default (we run the strategy). SDK + APIs and Co-managed are BYO strategy — you operate the trading, we provide the custody and vault rails. Embed widget works with either, depending on which vault it points at.
Multi-tenant — can we run multiple branded vaults in parallel?
Yes. Each cycle is fully isolated: its own keypair, smart wallet, operator scope, and fee split. A partner can run many concurrent vaults; a studio can run many partners. Cycle isolation is also a security boundary — a compromised cycle never touches another.
What integration time should we plan for?
Embed widget: days. SDK + APIs: 1–2 weeks for a working integration. White-label: weeks to first deposit including branding and content. Co-managed: depends on your strategy and ops readiness — typically 2–4 weeks.
How is your custody different from Polymarket’s wallets?
Polymarket-issued wallets ship from a third-party factory whose upgrade path is controlled by Polymarket. Our smart wallet is deployed from our own factory and audited in-house, so the venue cannot upgrade, brick, or recover wallets your users deposit into. The trading interface is the only Polymarket dependency.
Why closed-end instead of an evergreen vault?
Prediction-market alpha realizes at market resolution. A closed-end design lets the strategy hold to resolution rather than be force-liquidated by intra-cycle redemptions. The shape matches the asset class.
Regulatory?
Closed-end fund structures have decades of legal precedent. Each deployment is structured per jurisdiction with appropriate counsel — usually yours. We can introduce counsel we have worked with previously.
What chains?
Polygon, where Polymarket settles. Vaults accept pUSD, Polymarket’s native collateral. Bridging from any major chain is supported via Polymarket’s bridge.
Pricing?
Usage-based at the vault and custody layer with volume discounts; partner economics depend on which surface you pick (white-label vs SDK vs co-managed) and the fee split you configure. Speak to us about your model.
Your next step