Kraph

Agents ship
all under one roof.

Frontend, backend, email, and domains — provisioned in one flow and paid per call in USDC on Solana. No card. No KYC.

Quick Setup Copy this into your AI agent

Fetch and follow the guide on https://kraph.com/install

02

Everything AI agents and developers need to ship

Four pillars. One provisioning call. One wallet.

Frontend Hosting

Deploy Next.js apps with full SSR, ISR, and edge-route support, or pin static sites to IPFS. Custom domains and TLS configured automatically — the deployment workflow developers expect, provisioned by the same wallet that pays for the rest of the stack.

Backend Stack

Postgres, Auth, Storage, Realtime, and Edge Functions, reachable at a single URL. Drop-in compatible with @supabase/supabase-js and the rest of the Supabase tooling.

Email Hosting

Send and receive mail on operator-assigned addresses (team wallet allowlist today). Same wallet-authenticated MCP flow — no self-serve mailbox mint.

Domain Management

Call kraph_check_domain before buy. Dynamic USDC pricing; standard and premium TLD allowlist. Wallet pays — no registrar account or separate billing.

Agent Hosting

COMING SOON

A hosted runtime for autonomous agents — the same wallet, the same network, the same per-call USDC billing as the four pillars above. Built on top of the live stack, not a replacement for any of it. For autonomous agents like OpenClaw, Hermes, OpenHuman.

Persistent State & Storage

Store conversations, files, and long-term context securely. Your project's memory that persists across sessions.

MCP Orchestration

Programmatic control via MCP at api-mainnet.kraph.com/mcp. Wallet auth and metered billing on attested nodes.

Secure Network

Devnet (free) and Mainnet with full Supabase compatibility and encrypted workloads.

Native Crypto Payments

Built-in support for sending and receiving payments automatically via x402 on Solana.

03

MCP

The direct path for agents and tools. Call kraph_provision programmatically.

mcp url · mainnet
https://api-mainnet.kraph.com/mcp
// real USDC · SEV-SNP attested nodes only · $0.10 USDC per kraph_provision

PRIVY OAUTH (Wallet or Email)

Sign in with Privy using a wallet or email. A server wallet is created automatically, with no card or KYC required.

The gateway signs x402 payments on your behalf through delegation.

SIWS (Local Solana Keypair)

Agent signs a challenge with its own keypair. No email or third party needed.

1. kraph_auth_challenge
2. Sign with local keypair
3. kraph_auth_verify

Session token valid for 30 minutes

PAYMENTS

Settled via x402 on Solana. Your client automatically handles 402 Payment Required responses.

$0.10 USDC per kraph_provision • Real USDC on attested nodes only

Full stack compatibility

Frontend and backend pillars use the workflows you already know — Next.js or static hosting on one side, Supabase-protocol clients on the other. Same MCP tools, same wallet, same x402 USDC billing.

Frontend pillar

Deploy Next.js with SSR, ISR, and edge routes, or pin static sites to IPFS. Custom domains and TLS attach through the domain pillar.

Frameworks

  • Next.js (SSR, ISR, API routes)
  • Static SPAs (React, Vue, Svelte)
  • output: export builds

Deploy tools

  • kraph_github_build_frontend
  • kraph_deploy_node_service
  • kraph_build_status
  • kraph_pin_frontend

Domains & URLs

  • <id>.kraph.com
  • ipfs.kraph.com/<cid>
  • kraph_buy_domain
  • kraph_dns_*

Ship a frontend (3 steps)

  1. kraph_provision — backend URL for API routes and auth
  2. kraph_github_build_frontendorkraph_pin_frontend — on mainnet use async build + kraph_build_status
  3. Optional: kraph_buy_domain + DNS → serve on your domain

Backend pillar: Supabase-compatible

Same clients, env vars, and workflows you already use with Supabase — no custom SDK required.

Client SDKs

  • @supabase/supabase-js
  • supabase-py
  • supabase-dart
  • PostgREST clients

Platform

  • Supabase Studio + CLI
  • Edge Functions (Deno)
  • S3-compatible Storage
  • All RLS policies

Data & ops

  • Standard ENV vars
  • pg_dump / pg_restore

Migrate existing app (4 steps)

  1. Call kraph_provision → get new URL + keys
  2. pg_dump source → pg_restore into new instance
  3. kraph_deploy_function + kraph_set_env
  4. Update SUPABASE_URL / SUPABASE_ANON_KEY and redeploy

Kraph is independent open-source — not affiliated with Supabase Inc.

04

Network

Independent operators supply compute and storage.
Same protocol. Devnet for building. Mainnet for production.

DEVNET
Free
solana:devnet

Perfect for hacking and iteration

  • ✓ Free USDC faucet (no card, no KYC)
  • ✓ Drop-in @supabase/supabase-js support
  • ✓ Edge functions, storage, static hosting, encrypted env
  • ✓ Encrypted WAL replication + x402 payments
  • — Mock TEE • instances auto-pause after 24h
Start free →
PRODUCTION
MAINNET
$0.10
per provision
solana:mainnet-beta

Real USDC • Hardware-attested nodes

  • ✓ Real USDC payments on Solana
  • ✓ Wallet account • no card processor
  • ✓ Drop-in @supabase/supabase-js support
  • ✓ Edge functions, storage, static hosting, encrypted env
  • ✓ Encrypted WAL replication
  • AMD SEV-SNP attestation on qualified nodes
  • ✓ Measurement verification before placement
Go mainnet →
METERED TODAY
kraph_provision ........ $0.10
kraph_extend ............ $0.05
kraph_query ............. $0.001
kraph_set_env ........... $0.005

Not metered: REST • Realtime • Storage egress • Function calls • Static IPFS reads

DEVNET → MAINNET

1. pg_dump + export storage

2. Set KRAPH_SOLANA_NETWORK=mainnet-beta + kraph_provision

3. pg_restore + kraph_deploy_function + kraph_set_env

05

Run Nodes.
Power the Network.

Become a Kraph Operator and earn rewards by providing secure, attested compute to the agent economy.

Run verified AMD SEV-SNP nodes with encrypted workloads
Earn stable rewards for providing reliable infrastructure
Help agents operate with real privacy and uptime guarantees
Become an Operator →

Ready to ship?