# PassFast vs WalletWallet

Same job (wallet passes). Different meter — know which fits your usage.

HTML: https://passfa.st/compare/walletwallet

## Comparison

| | PassFast | WalletWallet |
| --- | --- | --- |
| Signing | Managed (PassFast) | Managed (WalletWallet) |
| Apple+Google | One API; counts as 1 | One API; both wallets count as 1 |
| Pricing model | $0.015 / active / mo | Ops quota (anti-active — operations, not live passes). Pro $39 · 100,000 create+update / mo. Business $99 · 1,000,000 create+update / mo (soft limit past). Scale from $379. |
| Free tier | 100 generates once | $0 · 1,000 create+update / mo |
| MCP | Remote HTTPS, `sk_live_` bearer | TBD |
| Templates | Visual template builder | TBD |

WalletWallet cells match live public pricing on walletwallet.dev/pricing (re-verified 2026-09-21).

## When PassFast fits

- You keep passes alive (loyalty, membership, tickets) and want a predictable per-active meter.
- You want Apple + Google from one API call, billed as one unit.
- You want managed signing and remote MCP with a secret key (`sk_live_`).

## When ops-quota may fit

- You create and update in bursts against a monthly operations budget, then do not keep a large live set.
- Your usage maps to a create+update quota ($0 · 1,000 / $39 · 100,000 / $99 · 1,000,000, per WalletWallet public pricing).
- You prefer an operations cap over an active-pass meter.

## Related

- Start free: https://passfa.st/signup
- Docs: https://passfa.st/docs
- MCP: https://passfa.st/docs/mcp
- MCP (markdown): https://passfa.st/mcp.md
- Pricing: https://passfa.st/pricing
- AI index: https://passfa.st/llms.txt

Last updated: 2026-09-21