Tier limits
Tier caps are enforced client-side by the signed JWT issued at activation. Upgrading a tier on the dashboard re-issues your entitlement on the next 24 h refresh.
Caps overview
| Metric | Builder | Solo Pro | Team | Agency |
|---|---|---|---|---|
| Marketplace accounts | 1 | 3 | 10 | ∞ |
| Personas / team members | 1 | 1 | 6 | ∞ |
| Listings published / month | 20 | ∞ | ∞ | ∞ |
| History retention | 30 days | ∞ | ∞ | ∞ |
Feature gates
| Feature | Builder | Solo Pro | Team | Agency |
|---|---|---|---|---|
| Margin calculator + trends | ✓ | ✓ | ✓ | ✓ |
| Sourcing & supplier scoring | ✓ | ✓ | ✓ | ✓ |
| Image processing pipeline | ✓ | ✓ | ✓ | ✓ |
| Manual publish flow | ✓ | ✓ | ✓ | ✓ |
| MCP server | ✓ | ✓ | ✓ | ✓ |
| 24/7 scheduler | — | ✓ | ✓ | ✓ |
| Inbox auto-responder | — | ✓ | ✓ | ✓ |
| Telegram team bot | — | — | ✓ | ✓ |
| Multi-persona P&L | — | — | ✓ | ✓ |
| White-label / multi-client | — | — | — | ✓ |
Enforcement mechanics
When a gated feature is invoked (for example the scheduler at boot), the
client checks the JWT’s entitlement.features list. Denied
features return a clear error message with an upgrade link. Soft caps
(like listings per month) are enforced at the enqueue step.