Silo for developers
Skip building memory. Ship on Silo.
Building an AI app like Granola, Friend, or Dot? Use Silo as your identity and context layer instead of building your own memory system. Persistent memory, connected services, and governance — through one integration.
Three mechanics. One control plane.
Memory. User access. Services. Through one integration.
Default hosted memory
Every new MCP connection auto-provisions a hosted silo named after your app (e.g. 'Granola silo'). Your users get persistent memory the moment they connect — no separate memory stack to build, host, or scale.
Developer plan covers user access
Pay for your users' access at the platform level (B2B2C). They don't need a separate Silo subscription to use your app. You get a per-app billing relationship; they get a Silo that outlives your app.
One integration point
Memory, services, and governance through the same control plane. Wire Silo once and your app inherits Google, Dropbox, Plaid, GitHub, audit logging, PII scrubbing, and per-tool approvals.
The data outlives your app
Every silo auto-named after your app (e.g. “Granola silo”) is undeletable while the connection exists, and persists as a user-owned silo if the user disconnects. Even if your app disappears, the user keeps everything it helped them capture — that's the portability thesis, working in your favor: every user you onboard onto Silo is a user you can keep serving from any future surface.
POST /mcp/connect → silo “{app}silo” readyWhere this is going
Developer integrations
Phase 1 · 0–12 months — Free hosted memory silo on every MCP connection. Drop in our SDK and ship a memory-enabled feature today. No tier required to start.
Connect your Silo
Phase 2 · 12–24 months — Cross-app context becomes an activation play. 'Connect your Silo' lets new users bring their existing context with them — your app gets a meaningful first-session answer from day one.
Works with Silo
Phase 3 · 24+ months — A 'Works with Silo' badge becomes a user-acquisition signal. Every platform that integrates Silo becomes a Silo user-acquisition channel — the same flywheel that made 'Sign in with Google' a category standard.
Developer plans
Pay for your users' access. Skip the memory stack.
Tiered developer plans cover user access at the platform level, with analytics, rate limits, priority routing, and SLAs on higher tiers. Modeled on Twilio and Stripe.
See developer plans