Overview
How LogoRouter charges map to API entitlements, meters, and dashboards.
Subscriptions are sold on logorouter.com and fulfilled by Stripe. We store your active plan, seat count (where applicable), and API key metadata in Postgres. The edge Worker reads a fast cache (KV + Durable Object metering) so authorization stays hot without round-tripping the database on every request.
Plans
Each plan unlocks:
- Daily and per-minute rate budgets
- Maximum logo raster size
- Feature flags for batch, colors, intelligence, cache refresh, and more
You can compare marketing copy on /pricing — this section documents behaviour, not marketing copy.
Where data lives
| System | Responsibility |
|---|---|
| Stripe | Invoices, renewals, payment methods, tax |
| Webhook workers (Vercel) | customer.subscription.updated, invoice.payment_*, checkout completion |
| Neon (Postgres) | Source of truth for user ↔ plan mapping |
| Cloudflare KV / DO | Hot usage meters + API key cache |
Need to debug access?
- Confirm the user has an active subscription or trial row in Postgres.
- Ensure the Clerk user matches webhook identity (email / external ids).
- Use the dashboard usage widgets — they summarise DO + Neon aggregates.
Continue to How billing works for Stripe events.