What Upshift does and doesn't do

For teams shortlisting vault infrastructure. Upshift covers part of the stack, and you appoint the rest.

Upshift helps fintechs build and offer savings products that earn yield on stablecoins. You get vault contracts, risk controls, NAV accounting, fee logic and withdrawal processing without building any of it. Upshift doesn't hold your customers' assets or pick the strategy day to day. Your custodian, fund administrator and compliance function stay where they are.

Most vendor comparisons in this category are written by the vendor, and everything scores well. That's not much use when you're building a shortlist. The tables below mark where Upshift fits badly as clearly as where it fits well. Better to find the gap now than halfway through legal review. Figures are current as of 20 August 2026.

What is Upshift built to do?

Upshift runs five vault products, all on the same contracts and the same policy engine. What separates them is where the yield comes from and who the depositor is.

Vault-as-a-Service is the wrapper around all of it. Any of the products above can launch as a vault under your own brand and front end, scoped in weeks rather than quarters. A fintech that wants a custom DeFi yield vault gets it that way.

The contracts underneath are ERC-4626, the Ethereum standard for tokenised vaults. That buys you portability. Your position is a receipt token other protocols already know how to read, so a custodian can hold it or a lending market can take it as collateral with no bespoke integration. The OpenZeppelin implementation notes are a reasonable primer if your engineers haven't worked with the standard before.

Deposits are stablecoins or crypto assets rather than fiat. If your product holds customer money in dollars today, something has to convert it first. That conversion sits outside the vault. USDC is the most common deposit asset across our vaults, though multi-asset vaults accept several deposit assets against a single reference asset for redemption.

What does Upshift deliberately not do?

This is the half of the map that usually gets left out. Each row below is a job that has to happen for a yield product to work, and that Upshift doesn't perform.

On insurance, Upshift has relationships with underwriters and can point LPs and curators to them. The cover itself gets written by the insurer rather than by us. The audit reports are published in full on the smart contract audits page.

Who else do you need on the deal?

A live vault normally involves four or five parties. Knowing which ones you already have shortens the scoping conversation considerably.

The step teams miss is the custodian. Your custodian has to be willing to hold the vault's receipt token, and that approval takes longer than the technical integration in most cases. Start it in parallel rather than after. There's a fuller walk through the sequence in who does what in an onchain vault.

Does your use case actually fit?

The table marks fit against the use cases we're asked about most often.

What controls sit on the money?

Capital routes into segregated subaccounts that the curator manages. Every transaction gets checked against Upshift's policy engine before it executes. The engine enforces restrictions at four levels:

• Chain. Which networks the mandate can touch at all.
• Protocol. Which venues are approved, so a curator can't wander into an unvetted one.
• Token. Which assets can be held or swapped.
• Function. Which specific contract calls are permitted, which is finer-grained than most allowlists go.

A curator who tries to interact with something outside that set has the transaction rejected onchain, before it executes, rather than flagged in a report afterwards. The risk management framework documents how the restrictions are set and changed. For how the underlying strategies behave, the strategy reference covers mechanics, risk and historical returns. Tiering strategies by risk sorts them the way most treasury teams do.

Policy enforcement covers curator behaviour rather than a bug in the contracts themselves. That's what the audit programme addresses, and it's why the general limits of smart contract security are worth understanding before you size a first allocation.

Separately, Upshift's prime stack can structure a credit facility against a vault. As of July 2026 it serves over $7B in monthly transaction volume and more than $800M in loans originated. That facility is what makes settlement financing and card float work, rather than the vault contract on its own.

Always make sure to do your own research and be aware of the above and any other risks before depositing.

How do redemptions work?

Every Upshift vault processes claimable redemptions daily. Each vault carries its own lag, set by how long the underlying strategy needs to unwind a position. Most vaults also offer instant redemption for a fee, subject to available liquidity in the buffer.

In practice a request placed on a Friday afternoon runs on that day's cycle rather than waiting for a Monday settlement window. If you need the money sooner, the instant path exists and costs a fee. Ask for the lag on the specific vault during scoping. The number varies by strategy, so an average won't help you.

This is one of the sharper differences between a vault and a fund wrapper. A tokenised money market fund typically settles on the issuer's calendar, so the exit window is set by the issuer rather than by the strategy. Redemption timing is worth writing into your own product spec before you pick a structure.

How big is Upshift, and does that matter?

Scale matters here mainly as evidence that the operational machinery has been exercised. As of 20 August 2026 Upshift holds more than $479M in deposits across its vaults, against a peak of over $550M, with 50+ vaults live on 30+ chains and more than 60,000 users. The contracts have been through 10 audits by 6 independent firms, and Upshift raised a $10M Series A led by Dragonfly in March 2025.

Treat public aggregator figures for any vault provider with care. Third-party trackers cover a subset of chains, so they tend to understate multi-chain deployments by a wide margin. If a number matters to your committee, ask the provider for it and ask which vaults it includes.

Where does this sit against the regulatory picture?

Upshift supplies infrastructure rather than a regulated product, so the perimeter question lands on you or on the partner you appoint. What that means in practice varies by market. In the EU, firms distributing to retail generally work through a licensed asset-management entity, and the MiCA framework sets the baseline. In the US, consumer-facing distribution usually runs through a broker-dealer partner.

The wider direction of travel is well documented by the standard setters. The Bank for International Settlements has published work on tokenisation and the future financial system that's a useful primer if your risk committee wants a source with no commercial interest in the answer. Bring your counsel in early, because the licensing question decides your distribution model rather than following it.

Frequently asked questions

Is Upshift custodial?

No. Depositors remain self-custodied throughout, and neither Upshift nor the curator can move funds to an external wallet. Assets route to segregated subaccounts governed by the policy engine.

Can we run a vault only our own balance sheet can deposit into?

Yes. Whitelisted and sole-depositor vaults are a standard configuration, and the depositor list is a parameter change rather than a contract change.

Do we have to use a curator you choose?

No. You can select from curators already on the platform, bring your own, or curate the mandate yourself if you have the capability in house.

What happens if we want to replace the curator?

Curator replacement is handled at the vault parameter level. Agree the mechanism during contracting rather than assuming it, because the answer depends on who controls the whitelist.

Does a vault deposit make us a securities buyer?

That's a question for your counsel, and the answer depends on your jurisdiction and the wrapper you use.

How long does a launch take?

Vault-as-a-Service deployments are scoped in weeks. The long pole is usually custodian approval and your own legal review rather than the integration.

Which chains are supported?

More than 30 as of August 2026, spanning major EVM networks plus Solana and Stellar. Check the current list during scoping, since new deployments are added regularly.

Keep reading

• What is Upshift: the plain-language introduction to the platform and the vault model.
• Who does what in an onchain vault: the end-to-end workflow, from capital to NAV to signatories.
• What an onchain vault is, for a treasury team: the same structure explained for a treasury audience.
• How to launch an onchain vault: mandate to live, including what to decide first.
• Upshift FAQ: custody, redemptions, fees, risk and integrations in detail.