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)
kraph_provision — backend URL for API routes and auth
kraph_github_build_frontendorkraph_pin_frontend — on mainnet use async build + kraph_build_status
- 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)
- Call kraph_provision → get new URL + keys
- pg_dump source → pg_restore into new instance
- kraph_deploy_function + kraph_set_env
- Update SUPABASE_URL / SUPABASE_ANON_KEY and redeploy
Kraph is independent open-source — not affiliated with Supabase Inc.