Skip to main content
ezForge offers four tiers to fit individuals and teams of every size.

​
Plans

Free

Get started with no credit card required

Developer

For developers shipping production MCP servers

Pro

For teams and production workloads at scale

Enterprise

Unlimited scale for growing teams

​
Feature comparison

* Not yet metered. The free plan’s 10,000 requests is a published allotment that is not yet enforced. Paid plans have no hard request cap: once metering is active, requests are billed by usage and bounded by a spend cap (see Spend cap).

​
Free tier details

The free tier is designed for development and exploration:
  • 2 servers — up to two MCP servers
  • 10,000 requests per month (allotment; not yet enforced)
  • 7-day log retention
  • Community support via GitHub Discussions
  • Personal domain only (no team access)
The free tier never charges you. The free plan’s 10,000-request allotment is published but not yet enforced; per-request metering is not yet active.

​
Developer tier

For developers shipping production MCP servers ($29/mo):
  • 10 servers with scale-to-zero
  • No hard request cap (requests not yet metered)
  • 30-day log retention
  • 10 deployment rollback history
  • Custom domains (coming soon)
  • Email support with 2-business-day response target
  • Personal domain only (no team access)
Upgrade via the dashboard or CLI:

​
Pro tier

For teams and production workloads at scale ($99/mo + $29/seat):
  • 50 servers with scale-to-zero
  • No hard request cap (requests not yet metered)
  • 30-day log retention
  • Team domains with access controls and audit log
  • Priority email support with 1-business-day response target
  • High-availability target — public status page coming soon
  • Additional team members: $29/seat/month (base price includes 1 seat)

​
Enterprise tier

Unlimited scale for growing teams ($199/mo + $19/seat):
  • Unlimited servers with scale-to-zero
  • No hard request cap (requests not yet metered)
  • 90-day log retention
  • Team domains with access controls and audit log
  • Priority email support with 1-business-day response target
  • High-availability target — public status page coming soon
  • Additional team members: $19/seat/month (base price includes 1 seat)

​
Usage and billing

​
How requests are counted

Requests are not metered yet. When metering is active, every call to your server’s SSE endpoint or message endpoint will count as one request. Health check polling by ezForge will not count as requests.

​
When usage reaches billing

Each hour of recorded usage is reported to Stripe once it has closed. Usage shown in Stripe and on invoices can trail real use by about an hour. If Stripe cannot be reached, the platform retries on its next pass and nothing is dropped while the hour is inside the 34-day age limit. If an hour’s usage is corrected after it was reported, the difference is sent so the total stays accurate. See Usage reporting to Stripe for details.

​
Monthly plan credit

Each time your Developer or Pro plan invoice is paid, your account receives credit equal to the plan fee ($29 or $99, or the amount actually paid if the invoice was discounted). The credit applies to usage charges and expires at the end of that billing period; unused credit does not roll over. See Period credit grant for details.

​
Billing cycle

Subscriptions renew monthly on the date you upgraded. You can view your current plan and billing period at any time. Request usage currently reads 0 because requests are not yet metered:
Or via the API:

​
Upgrading and downgrading

  • Upgrade — Takes effect immediately; you’re billed a prorated amount for the remainder of the billing period
  • Downgrade — Takes effect at the end of the current billing period; your current plan remains active until then
If downgrading from Developer to Free would exceed free-tier limits (e.g., you have 3 servers), you must delete servers first.

​
Stripe

Billing is powered by Stripe. ezForge never stores your payment information. Invoices, payment method management, and billing history are available in the Stripe portal, accessible from the dashboard under Billing.

​
Billing account

Each domain is one billing account with one Stripe customer. Platform, Ready, and Hub checkouts all use that customer: the first checkout on a domain creates it, and every later checkout, in any product, reuses it. Ready and Hub purchases are made by a user, so they bill the customer of that user’s personal domain.

​
One subscription per account

Ready and Hub purchases join the subscription you already have, so their charges appear on the same invoice and prices are unchanged. Buying Ready or a Hub upgrade adds an item to that subscription, with the first partial period prorated; with no subscription yet (for example, Ready on the Free Platform plan), checkout creates it. Buying a Platform plan after Ready or a Hub upgrade may still create a second subscription until Platform checkout is updated. Changing a Ready plan or Hub tier swaps only that item. Cancelling Ready removes only the Ready item and credits the unused time, and your other products keep running; when Ready is the only item, cancelling ends the subscription at the end of the billing period instead. Removing a Hub upgrade is not available in the dashboard yet, and cancelling the Platform plan is not available while Ready or a Hub upgrade shares its subscription. Your Ready 14-day trial applies only when Ready is your first paid product, because a Stripe trial covers a whole subscription, not one item. Accounts that subscribed before the shared customer existed may still have a different Stripe customer recorded on an older Ready or Hub subscription. The next Ready or Hub checkout moves that subscription record onto the shared customer. Hub tier checks look up the account’s shared customer first, then fall back to the older Platform and Ready records.