TinyCloud Integration

Use OpenKey here when you want TinyCloud to keep its SIWE flow but replace a browser wallet with passkey-based signing.

What stays the same

TinyCloud still uses SIWE
TinyCloud still derives identity from an Ethereum address
TinyCloud still issues the session after a valid signature

What OpenKey provides

A browser-friendly signer
Passkey authentication
A path that does not require MetaMask or another wallet extension

Working example

import { OpenKey, OpenKeyProvider } from "@openkey/sdk";
import { TinyCloudWeb } from "@tinycloud/web-sdk";
import { providers } from "ethers";

const openkey = new OpenKey({ host: "https://openkey.so", appName: "My TinyCloud App" });
const authResult = await openkey.connect();
const eip1193Provider = new OpenKeyProvider(openkey, authResult);
const web3Provider = new providers.Web3Provider(eip1193Provider);

const tcw = new TinyCloudWeb({
  providers: {
    web3: {
      driver: web3Provider,
    },
  },
});

await tcw.signIn();
await tcw.kv.put("hello", "world");

Why this shape

The TinyCloud Web SDK expects an ethers-compatible provider. The OpenKey SDK’s provider wrapper supplies that compatibility.

TinyCloud-specific advice

Keep the OpenKey host separate from the TinyCloud host
Use providers.web3.driver for the TinyCloud Web SDK integration shown in the OpenKey repo
Treat this as a sign-in flow, not an OAuth flow

The integration example mirrors the OpenKey SDK repository’s TinyCloud example, so the API shape matches the source-backed integration path.

SpacesUnderstand the TinyCloud container that owns a user's data

​What stays the same

​What OpenKey provides

​Working example

​Why this shape

​TinyCloud-specific advice

What stays the same

What OpenKey provides

Working example

Why this shape

TinyCloud-specific advice