Commercial strategy · Recommendation v1.1
Price the value.
Meter the infrastructure.
Sell EzeBridge by concurrent support capacity and managed endpoints. Keep direct P2P and ordinary control-plane usage included, give automatic TURN fallback a bounded pooled allowance, use a tightly bounded forever-free tier for acquisition, and sell forced privacy relay separately.
The pricing principle
Customers pay for operational capacity—not packet volume.
Concurrency and endpoint scale track the value delivered to an IT team. A bounded P2P-only Free tier earns product adoption; paid tiers protect variable TURN cost with allowances, alerts, and relay packs without turning every support session into a confusing metered bill.
01 · Commercial plans
Simple enough to buy. Strong enough to scale.
All figures are proposed USD prices before taxes. Entitlements are pooled at the organization level.
No card required
- 1 user
- 1 concurrent connection
- 1 owned remote device
- 5 sessions each month
- 60 minutes maximum per session
Billed annually
- 1 user
- 1 concurrent connection
- 5 owned computers
- Essential remote access controls
Billed annually
- 3 technician accounts
- 1 concurrent support channel
- Unlimited attended devices
- 100 managed devices
Billed annually
- 10 technician accounts
- 3 concurrent support channels
- 500 managed devices
- Team roles and shared administration
Billed annually
- 30 technician accounts
- 10 concurrent support channels
- 2,000 managed devices
- Advanced audit and priority support
Custom concurrency and endpoints, SSO, API/SIEM integration, SLA, dedicated region or relay, and onboarding—subject to release readiness and contract scope.
Annual contract02 · What we charge vs. what Cloudflare charges
Healthy unit economics—even at full allowance consumption.
This table intentionally ignores Cloudflare’s free 1 TB pool and assumes it has already been exhausted. That gives us the conservative marginal cost of every plan.
| Plan | Annual-billed price | Included TURN | Max CF cost | Revenue after TURN | CF share of revenue |
|---|---|---|---|---|---|
| Free | $0 | 0 GB · P2P only | $0 | $0 | Not applicable |
| Access | $9 | 10 GB | $0.50 | $8.50 | 5.6% |
| Support Solo | $29 | 25 GB | $1.25 | $27.75 | 4.3% |
| Support Team | $99 | 100 GB | $5.00 | $94.00 | 5.1% |
| Support Business | $299 | 500 GB | $25.00 | $274.00 | 8.4% |
Revenue after TURN is contribution after relay egress only—not profit. Payment fees, support, control-plane services, taxes, and product development remain outside this comparison.
max(0, total egress GB − 1,000) × $0.05
The free 1 TB applies once to the Cloudflare account, not once per EzeBridge customer.
Treat the free pool as company-level upside so unit economics remain valid as usage scales or vendor terms change.
03 · EzeBridge Private Relay
Forced relay is a paid privacy product.
Automatic TURN fallback protects connectivity. Private Relay forces relay-only ICE policy and prevents silent P2P fallback.
Organization-level usage notifications and admin visibility.
Opt into automatic top-ups or enforce a hard monthly relay cap.
Private Relay fails closed when quota or policy prevents a relay path.
Allowance accounting follows Cloudflare egress, including TURN overhead.
04 · Founder scenario model
Change the customer mix. See the relay exposure.
The default case models 5,000 Free accounts plus the first 1,000 paid organizations at 25% paid-plan TURN allowance utilization.
05 · Founder decisions requested
Approve the commercial frame—not a premature GA claim.
Free forever for one device, five monthly session starts, and a hard 60-minute limit per session.
Direct P2P only, no included TURN, no Private Relay entitlement, and server-authoritative monthly/session enforcement.
$9 Access, $29 Solo, $99 Team, and $299 Support Business on annual billing.
10 / 25 / 100 / 500 GB pooled monthly, budgeted at full marginal cost.
Private Relay packs at $19 / $79 / $149, with transparent alerts and no silent P2P downgrade.
Pricing approval does not imply production readiness. Entitlement enforcement, anti-abuse, physical coverage, recovery, soak, signing, support, and release gates must close independently.
Recommended resolution
Let one device in free. Monetize capacity, scale, and privacy.
This structure gives individuals a durable zero-cost entry point, converts growing support needs into paid plans, and keeps relay economics predictable without penalizing healthy P2P sessions.