● Enforcement
Simple pricing.
Hard enforcement.
Billing sets limits. Validation enforces them at runtime.
If validation fails, execution does not run.
No contracts. No sales calls.
MachineID enforces limits when autonomous systems run—not after the bill arrives.
Free
$0
/ month
- 3 devices
- Full runtime enforcement
- All core endpoints
- No credit card required
Same enforcement logic as paid plans.
Pro
$29
/ month
- 25 devices
- Enforce limits at startup and before work
- Downgrades enforce immediately (devices may clamp)
- Stripe billing
Most teams start here.
Scale
$99
/ month
- 250 devices
- Continuous runtime enforcement
- Revocations deny execution on the next validate
- Built for unattended runtimes
Built for always-on systems.
Max
$249
/ month
- 1,000 devices
- Org + device identity at scale
- No redeploys when limits change
- Audit-friendly enforcement signals
Need more? Contact Support
Limits are enforced, not advisory.
MachineID does not report usage—it enforces it.
If the org is over limit or inactive, validation fails and execution stops. This is intentional.
How billing works
- Plans are enforced via Stripe subscription state
- Upgrades apply immediately
- Downgrades apply immediately and may clamp devices if you are over the new limit
- Cancel takes effect at period end; enforcement clamps after access ends.
- No redeploys, no config changes, no new keys
Billing defines the limit. Validation enforces it at runtime.
No lock-in
- Cancel anytime via Stripe portal
- Keep your existing autonomous system config
- Enforcement logic remains consistent across all plans
“You’re not paying for analytics. You’re paying for enforcement.”