Financial products should not own their users.

People deserve an account that feels like a bank without needing a bank's permission to use it.

A note from Candide's founders For teams building onchain finance

The problem

Nobody loses control of their money in one step. It goes in small pieces, each one reasonable on its own.

  • An account that can be frozen.
  • A transfer that sits pending for three days with no explanation.
  • A recovery flow where the company decides whether you are really you.
  • A balance that is yours until an institution decides otherwise.

Each of these is a normal Tuesday at most financial companies. Put them together and the user no longer holds their money. They hold a claim on it, and someone else holds the keys.

That matters because money is not abstract. It is rent, payroll, a parent's remittance, the savings someone plans to leave with.

You can build something people love without building something they cannot leave.

Our position

The easiest way to build a financial product is to take control. Hold the keys on your servers, route every action through your backend, and decide yourself when a user can move money or recover access. Complexity disappears because the company becomes the final authority on everything.

We want to be fair about this: it produces good UX. It is also how most of onchain finance quietly turned back into the thing it was meant to replace.

We started Candide for teams who want that UX without becoming the bank. The accounts run on Safe contracts on Ethereum. Gas is sponsored, so users never see it. Recovery goes through guardians the user chose, not a support ticket. The same account works across chains and apps. And if a team ever wants to leave Candide, the accounts go with them, because we never held the keys in the first place.

What ownership means in product decisions.

Moving money never waits on us

A user can send funds without a company saying yes first. If Candide disappeared tomorrow, the accounts keep working.

Recovery gets you back in. It does not hand the product a master key.

Guardians, delays, and limits belong to the user. A recovery process that gives the company permanent power over the account is custody with extra steps.

The rules are onchain and readable

When software controls money, people can read the rules and notice when they change.

Nobody has to learn what gas is

Seed phrases, chains, account abstraction. None of it belongs in the user's head. Hiding the complexity is fine. Hiding who holds the keys is not.

A door that stays unlocked

We would rather help a team build something useful than make its users dependent on us. Our retention has to come from being good, because leaving is always possible.

The work

None of this requires the user to become technical. People do not want to understand chains or seed phrases, and they should not have to. They want an account that works, that they can get back into when they lose their phone, and that does not turn into leverage against them later.

That is the account we are building. Candide exists to make it the default rather than the exception.