Status & roadmap

What Swivy runs today, what's being built, and what comes before general availability.

Preview: Swivy is not generally available

This page is the honest status. If something is listed under "Building" or "Next", you can't rely on it yet. Request early access.

Today

Building

Staging runs on Swop's own infrastructure: API, worker, isolated signer, console and Postgres, on testnets (base-sepolia, solana-devnet).
Built and tested: email and wallet login, passkey/TOTP/SMS step-up, EVM and Solana wallets, signing and transaction intents, gas sponsorship, per-environment RPC routing, webhooks, agent session grants, Sign in with Swop (OIDC with discovery, JWKS, hosted login and consent, refresh tokens), and SDKs for web, React, Expo and Node.
Split-custody logins no longer auto-create server-side accounts (fixed October 2026), so browser-held keys stay the user's.
Swop itself still runs on Privy. Swivy isn't wired into the Swop app yet.

Built and in review, not merged or deployed yet:
- app-owned server wallets;
- creating, looking up and deleting users from a server;
- server-side session checks;
- webhook retries with more event types;
- several workers running safely side by side;
- passkey and SMS as the main login;
- Bitcoin segwit wallets;
- gas sponsorship that leaves no balance in the user's wallet (Solana fee payer, EVM exact gas) and per-wallet daily caps.
Still to build: incoming-transfer webhooks, encrypted key export, and permanent delegated signers.
Swop staging on Swivy for new test users, behind a flag.
Production-grade operations: Postgres-only storage with tested backups and restore, several workers side by side, the signer running in an attested enclave with key-release policy, real RPC through Swop RPC, email delivery, monitoring and alerting.
Access control: richer roles for operators and customers, invites and member lifecycle, approvals for control-plane changes.
Security review of the API, signer and custody flows by an outside firm before production.

New Swop users on Swivy in production, with managed custody by default and split custody as a setting.
Existing Swop users move later, by their own action.
SDKs published and docs opened to everyone.
Longer term: device-held keys with server-assisted recovery or threshold signing, a multi-region signer fleet, and compliance certifications.

No completed external audit, no compliance certification and no threshold MPC today. We'll say so here when that changes.