Fair Use Policy

Last updated: April 23, 2026

EasySchema offers generous, flat-rate plans so you can focus on building, not counting. This policy explains how we apply plan limits and what constitutes "fair use" so everyone has a fast, reliable experience.

1. Hard Limits vs Soft Limits

Each plan has specific limits for workspaces, collections, requests, webhook listeners, and documentation sites. These come in two forms:

• Hard limits — enforced at the API level. You cannot exceed them. Examples: number of collections, webhook listeners, and doc sites.
• Soft limits — monitored but not enforced in real-time. We'll notify you if you're consistently exceeding them and ask you to upgrade. Examples: burst request rates, occasional spikes above monthly request quotas.

2. What Happens When You Hit a Limit

• Workspace and collection limits: You can still access everything you have, but new creations are blocked until you upgrade or free capacity.
• Monthly request limits: Proxy requests beyond your quota are rejected until the next billing cycle or you upgrade. Existing requests and data remain accessible.
• Storage and retention: Webhook payloads and audit events older than your retention window are automatically cleaned up. Upgrading extends retention going forward but does not recover deleted data.
• Webhook payload count: New payloads are rejected when a listener is full. Clear old payloads or upgrade to continue receiving.

3. Fair Use Expectations

Our plans assume normal development and documentation usage. The following count as abuse and may result in throttling, suspension, or termination:

• Using the proxy as a general-purpose CDN or outbound traffic router for unrelated applications
• Storing large files, offsite backups, or general hosting content in request bodies, webhook payloads, or doc sites
• Sustained burst rates designed to extract maximum value while providing minimal product feedback
• Running automated request loops that don't correspond to legitimate testing or integration activity
• Creating workspaces, users, or collections programmatically to bypass per-entity limits
• Coordinating multiple accounts to bypass plan limits

4. Resource Consumption

Even within plan limits, we may throttle or block activity that:

• Consumes disproportionate CPU, memory, or I/O compared to other customers
• Degrades service performance for other users
• Triggers our abuse-detection systems repeatedly

In practice, this almost never affects normal users. We'll always attempt to reach out before taking restrictive action.

5. Large Files and Payloads

Maximum sizes are enforced at the application level:

• Request bodies and webhook payloads have per-plan size caps (64 KB to 2 MB depending on plan)
• Uploaded logo/favicon files are capped at 2 MB (logos) and 1 MB (favicons)
• Overall API request body size is limited to prevent denial-of-service

If you have a legitimate use case that requires higher limits, contact us — custom Enterprise terms are available.

6. Notifications

We'll notify you via email and in-product:

• When you approach 80% of a hard limit
• When you hit 100% of a limit
• If we detect patterns of abuse or fair-use violations

8. Disputes

If you believe a limit was enforced incorrectly or you need a temporary increase for a legitimate reason, contact support@easyschema.xyz. We're reasonable and will work with you.

9. Changes

We may adjust limits over time as we scale infrastructure. Material changes that reduce limits on existing plans will be communicated at least 30 days in advance.

10. Contact

Questions about fair use, limits, or custom capacity? Email support@easyschema.xyz.