Skip to content

2026-10-18

Why Kobia builds on five networks

Kobia builds across web3, web2 and AI. People often ask why our products do not all live on one chain. The short answer is that a product should pick the network that fits the job, and the user should never have to care which one it is.

One network per job

Every product starts from a user problem, then we choose the rails.

Ethereum sits underneath much of this as the shared standard for contracts and tooling.

What we optimise for

Three questions decide the network for each product:

  1. Does the money move the way users expect? Stablecoins for payments, Bitcoin for Bitcoin yield.
  2. Can we remove the hard parts? Handles instead of addresses, sponsored gas instead of fee management, escrow instead of trust.
  3. Does the network already have the people we need? Games need players, bounties need contributors, and Celo and Mezo bring them.

The cost, honestly

Building on several networks is more work. Each one has its own contracts, wallets, edge cases and failure modes, and we write the smart contracts in-house. Security is treated as a feature, not a final step. We accept the extra work because the alternative is a worse product on the wrong rails.

Web2 and AI fill the gaps

Not everything belongs onchain. Coven lets people withdraw to a bank account, which is a web2 problem. AI is used where it earns its place, for example helping verify activity, with a human kept in the loop. The aim is the same across all of it: apps people use without thinking about the chain.

What's next

Several of these products are still early. Check each product's status on the products page, and if you want to build any of this with us, see opportunities.