- Company sizes or stages where the product may be inappropriate
- Very early prototypes without a defined monetization model may find simple payment links or Merchant-of-Record solutions sufficient.
- Large enterprises that require publicly documented compliance attestations may find missing public security artifacts to be a blocker.
- Industries or use cases where competitors are more appropriate
- Organizations prioritizing a standardized, enterprise-grade billing stack with mature modules (dunning, revenue workflows, advanced reporting) may prefer established vendors such as Chargebee or Recurly.
- Technical requirements the product does not meet (based on public documentation)
- No publicly documented on-premises deployment option or strict EU-only data residency offering was found.
- Budget constraints
- For teams where $99/mo plus a setup fee is not affordable or where simple checkout flows suffice, lower-cost or Merchant-of-Record alternatives may be more appropriate for low-volume sales.
- Procurement red flags
- If detailed metered pricing and billable event definitions are only available through sales interactions, require a written pricing schedule and definitions for billable events before contractual commitment.
- Current limitations acknowledged in public materials
- Public documentation does not list an explicit known-issues tracker.
- Roadmap and feature requests
- No publicly published roadmap items with dates were found in the reviewed sources.
- Scale considerations
- No public scale limits or performance thresholds were documented.
- Security or compliance gaps
- No publicly documented SOC 2/ISO certifications or pen-test summaries; SSO/SAML/SCIM/audit log features are not clearly documented publicly.
- API limitations or integration constraints
- Public docs describe Events API and entitlements endpoints, but rate limits, quotas, and SLAs are not detailed in the public documentation.