Pricing.

Beta pricing. The tiers below are what we’ll charge when billing turns on. Right now every beta account is hand-onboarded and free. Sign up, use it, tell us if the shape is right.

Private beta.Billing is off until we’ve proven the primitive with real customers. Talk to us and we’ll grandfather your usage in.
Free

For hobby projects + weekend agents.

$0forever

1,000 emails / month

  • 1 inbox
  • Schema with 10 revisions
  • HMAC-signed webhooks
  • MCP server access
  • 90-day event retention
Start free (beta)
Builder

For solo devs shipping a newsletter-native product.

$29per month

5,000 emails / month

  • Unlimited inboxes
  • Unlimited schema versions
  • Retry ladder + dead-letter
  • MCP server access
  • 90-day event retention
Request beta access
most common
Growth

For real products with real inbound volume.

$99per month

50,000 emails / month

  • All Builder features
  • 365-day event retention
  • Custom domain per inbox (waitlist)
  • Priority support
Request beta access
Scale

For teams treating email as core infrastructure.

$399per month

500,000 emails / month

  • All Growth features
  • Custom terms + invoicing
  • Direct founder support
Talk to us

What counts as an event?

One inbound email = one event. Duplicates dedup by Message-ID and don't count. Failed extractions still count (webhook fires regardless per the docs).

What happens if I exceed my quota?

Nothing scary. We keep receiving your email and flag events past the quota; nothing is dropped. Once billing is live, overage above quota is planned at $0.005 per event on Builder and Growth, $0.003 on Scale.

Is MCP included?

Yes, on every tier. Every Inbin app is an MCP server: list inboxes, browse and search events, read the schema. Connect from Claude Desktop or Cursor with your API key, or via npx @inbin/mcp.

Do you offer annual pricing?

Not yet. We want retention data first. When we do, expect the usual ~20% off for annual commit.

Custom domain?

On the Growth waitlist. Instead of foo@in.inbin.dev, your users forward to foo@in.yourbrand.com. Tell us when you upgrade and we'll wire your domain by hand until self-serve ships.

Enterprise, SOC 2, BAA?

Not yet, and we won't claim otherwise. Compliance work starts when the first customer needs it contractually. HIPAA-adjacent workloads need a conversation first (email content can be PHI).