What's free, what's paid

The free tier is generous on purpose. You can build real things with it. Paid plans add the parts that turn "an agent that remembers" into "an agent that gets smarter the longer you use it."

The plans, at a glance

What "free" actually gets you

The free tier is not a crippled trial. You can use Sibyl Memory Plugin in production with it. You get:

• The full five-kind memory model (state, entities, journal, reference, archive).
• Fast search across everything you've stored.
• Multiple identities on the same machine.
• No round-trip to anyone's cloud for any memory operation. Sub-millisecond local recall.
• Account activation, including signing in with your wallet.
• 2 MB of local storage. Enough for a few weeks of real, daily use.

The 2 MB cap is a hard limit on the free tier. Writes that would push the local database past 2 MB are rejected with a clear upgrade prompt. The cap only triggers at the boundary; under-cap writes never phone home, so the local-first experience stays local-first. The check itself happens against the activation server, so paid users who upgraded after install are recognized immediately without reinstalling.

What paid unlocks

No storage cap

Use as much local storage as you have disk space for. A typical heavy user is at a few hundred megabytes after months of work, but the system handles gigabytes without trouble.

Self-learning

Your agent watches how you work and proposes reusable skills. If you've done the same kind of thing five times, it suggests a "skill". A short, structured recipe the agent can apply automatically next time. You review each proposal and accept or reject with a click.

Three ways to power the summarization:

• Free patterns only (default). The agent uses simple pattern detection. No external AI call.
• Bring your own AI. Paste your own API key (Anthropic, OpenAI, Venice, anything). The summarizer calls your chosen model. We never see the key or what flows through it.
• Sibyl-hosted AI. Pre-fund your account with USDC or a credit card; we route summarization through Venice on your behalf and bill against your balance. Most convenient option.

Full walk-through →

Memory check-up

A health report on your agent's memory. Surfaces duplicates, stale entries, items near the storage cap, anything that looks structurally off. Useful to run weekly; even more useful before a big launch when you want to confirm the agent's worldview matches yours.

What it checks →

Cross-device sync (Sync plan, building)

Your memory follows you across machines. The sync is end-to-end encrypted; we hold the encrypted blobs but can't read them. Sync only. Your laptop and your desktop see the same memory. We're shipping this in the next wave.

Self-hosted Enterprise (designing)

Run everything on your own infrastructure. Same SDK, pointed at your own Postgres database. Audit logs, SLAs, compliance support. For regulated industries, sovereignty-conscious orgs, or anyone whose risk team won't let them touch a vendor cloud.

Which plan fits which kind of user

Upgrading and downgrading

One command from your terminal:

$ sibyl upgrade

The browser opens. You pick one of two paths:

• Stake $SIBYL. Connect any wallet (browser injected or Coinbase Smart Wallet via passkey), sign once to bind your wallet to your plugin account, the server checks your on-chain $SIBYL balance on Base. If you hold the threshold (currently 100,000 SIBYL, liquid + staked combined), the cap lifts. No subscription, no recurring fee. As long as you hold the threshold, the cap stays lifted.
• Subscribe in USDC. Pick monthly, quarterly, or annual. The page builds a single USDC transfer on Base, your wallet signs and broadcasts it, and the server confirms the on-chain payment. Tier flips immediately. The subscription auto-expires at the end of the period; renew via the same flow.

Either way, upgrading takes effect immediately. You don't lose any data on the way up. Sibyl Memory Plugin just stops applying the free-tier cap and starts allowing the paid features. The CLI refreshes its local hints (credentials.json and the tier cache) so your next write picks up the new entitlement without an extra round trip — but the cap decision itself is always made server-side against the database, not from those local files. Editing the local file by hand doesn't work: every credentials.json is HMAC-signed by a key only the server holds, and the server uses the database tier as authoritative. See tamper-evident credentials for the full mechanism.

Downgrades work the same way: cancel the subscription or unstake, the entitlement check sees you below the threshold, your tier reverts to free at the next access check. You don't lose data, but the 2 MB cap comes back on for any new writes.

What we'll never do

• We won't read your memory content. Our database has no place to store it. Even if we wanted to, we structurally couldn't.
• We won't sell your data, train models on it, or share it with partners. Nothing about Sibyl Labs's business depends on either.
• We won't hold your data hostage if you cancel. Your memory.db is yours, plain SQLite, openable with any tool.