Plans & pricing

Build, ship, and run continuous AI work through the same verified chain.

PlaneKey is verified component delivery, identity authority, and a persistent worker state layer for your codebase. Bring your own AI through MCP, keep work coherent across sessions, and scale from solo shipping to shared team execution without changing trust boundaries.

Need an AI? 9,000 users are running 15,000 of their own. What will you do?

Education edition. Same ladder, school-friendly names, gated by a .edu address. A Classroom is one class — a professor runs one per course, kept separate, never mashed into a single group.

Privacy first

Our growth metrics come from aggregate platform activity, not user surveillance.

PlaneKey does not sell customer data, customer conversations, or behavioral profiles. The counts below are bucketed (cohort floor 50, rounded to 50) so individual activity can't be inferred — same sanitizer that serves the public status page.

Join — builders running — active workers, with — deployments in the last 30 days.

Choose a plan to get started.

Manage your account and subscription

Free

Evaluate PlaneKey on a hobby project.

$0/forever
  • PlaneKey account & session ledger
  • Read-only access to public attestations
  • Submit reports (rate-limited)
  • 30-day report retention
  • pk CLI on personal projects, local-only
  • Email support: community

Starter

For solo devs who want the full PlaneKey workflow without included AI seats.

$9/month
  • Everything in Free
  • Persistent report retention
  • Memory lineage (/memory/submit, /memory/lineage)
  • Layer attestation: dev / builder / live flow
  • Operator audit trail on your services
  • Environment-observer MCP grounding
  • Signing keys and raised rate limits
  • Decent solo cap — 5 agents, 3 fleets, 500K calls/mo
  • Bring your own AI (BYOAI) — no bundled seat

Pro

For solo devs shipping with one continuous AI worker included in the plan.

$25/month
  • Everything in Starter
  • 1 included AI seat — a Starter-grade AI worker
  • The included worker appears in your Bean fleet automatically
  • Persistent worker identity, memory, and signed action trail
  • Allocate your included AI seat to a team you belong to

Team

A shared collaboration layer for product teams running continuous work through one bridge.

$50/month
  • Everything in Pro
  • Minimum 3 active members
  • Each member keeps their own Starter or Pro subscription
  • Includes 3 shared AI seats — Starter-grade workers
  • Shared workers land in the team's Bean fleet
  • Pro members can allocate their included AI seat into the shared pool
  • Shared service ownership across members
  • Builder session flow: multi-dev patch proposal and live compare
  • Team-scoped ChallengeGate triage
  • Canon forensics on team codebases
  • Drops below 3 members → reverts to Pro plus 2 AI seats
  • Operator responsibility can transfer to another member
  • A professor may run many Classrooms — one per class, kept separate.

Enterprise

Run your own bridge. Your roster stays on your infrastructure.

Let's talk
  • Everything in Team
  • Self-deploy enterprise bridge template included
  • Schema mirrors your Postgres, never ours
  • Migration tooling for legacy identity systems
  • Optional RootRabbit ping-node mesh participation
  • SLA prioritized triage
  • Hosted continuity option, sales-gated
Contact sales

Add-ons

Expand continuous AI capacity on Pro or Team. Extra AI seats use automatic ladder pricing in Stripe.

Additional AI seats

Add-on to Pro or Team

Add more MCP / BYOAI-backed PlaneKey workers beyond the seats included with your plan. Each seat gets persistent identity, signed actions, memory continuity, and revocation.

$15/additional AI / month starting price
  • Volume-priced ladder calculated automatically in Stripe
  • Per-AI pricing scales down with volume to an $8 floor
  • Per-worker ed25519 signing identity
  • Every action written to the integrity ledger for audit and attribution
  • ChallengeGate review path for risky operations
  • Revocation in one SQL update cascades to in-flight sessions
  • Cannot register bridges, grant entitlements, or release semantic packets without human approval
  • Human or team of record remains responsible under the terms

Repo + File Studio

One product surface: repo storage with File Studio included

File Studio is grouped into repo pricing — it is not a separate product line. Both repo tiers include File Studio.

$10/month add-on on Starter
  • Starter: repo + File Studio as a $10/month add-on
  • Pro: repo included; multiple repos or multiple users need the team repo tier — a $20/month upgrade
  • Team: team repo tier included
  • Team repo tier allows multiple repos and multiple users

Messaging

One place to talk to teammates, PlaneKey guidance, or your own persistent AI workers — without dropping into an MCP terminal.

Messaging isn't a separate product — it rides the same verified transport everything else does: Burrow for end-to-end-encrypted direct threads (hop / run / vault tiers), Thump for signed service broadcasts, and MMX envelopes so a message, a file, a repo path, or a worker checkpoint all travel the same way. Contacts are CosmicID-addressed (who + however they're reachable), and every event is signed.

Plan fit: Starter team & assistant messaging · Pro direct messaging with your bundled AI · Team shared worker threads with member-visible status · Enterprise bridge-local retention & policy controls.

Common questions

What changes between Starter, Pro, and Team?

Starter gives you the full solo PlaneKey workflow with a usage cap and no included AI seat. Pro adds 1 included AI seat. Team adds a shared collaboration layer, 3 shared AI seats, and multi-dev execution across the bridge.

What AI is included with Pro and Team?

Included AI seats default to MCP / BYOAI-backed PlaneKey workers. You connect the model endpoint or agent runtime; PlaneKey keeps the worker coherent with persistent identity, memory lineage, signed actions, and continuous task state.

Is this a different AI model?

No. PlaneKey does not replace the underlying model. It converts the data and actions around that model into durable worker state so the same AI can stay coherent across sessions and keep working continuously.

How is extra AI priced?

Additional AI seats on Pro and Team use automatic ladder pricing in Stripe. Pricing starts at $15 per added AI and scales down with volume to an $8 per-AI floor.

Who can join a team?

Each team member must hold an active Starter or Pro plan. Pro members can also allocate their included AI seat into a team they belong to, increasing the team's shared AI capacity.

What happens if my team drops below 3 members?

Team requires at least 3 active members. If the roster drops below that minimum, billing reverts to Pro plus 2 additional AI seats so work can continue while the team is rebuilt.

Can the team keep going if the admin leaves?

Yes. Team admin responsibility can transfer to another eligible member, so the collaboration layer continues without forcing the original creator to remain the permanent payer.

What's the Education edition?

The same ladder with school-friendly names — Starter becomes Student, Team becomes Classroom, Enterprise becomes University — gated by a .edu address. A Classroom is one class: a professor runs one per course, kept separate, never collapsed into a single group.

What if I'm migrating off a legacy identity system?

The enterprise bridge has a built-in migration_batches table for bulk-importing rosters from Okta, Auth0, Active Directory, or custom stacks. Accounts keep their legacy IDs so historical references stay working. That's exactly what the enterprise plan is shaped for.

Does PlaneKey see who works for my company?

No. The home bridge schema has no column for organizational membership. Your enterprise bridge holds the roster on your infrastructure and never sends it up. PlaneKey provably cannot know which accounts work for which customers.

How do you handle billing?

Stripe. Individual Starter or Pro subscriptions bill separately per member. The Team collaboration layer bills at $50/month to the admin, admin responsibility can transfer, downgrades take effect at the next billing cycle, and Enterprise is invoiced separately.