Enforcing Plan Limits Without Surprising Customers

Every plan on our platform includes certain limits: how many websites an account can have, how much storage it can use, how many items of certain kinds it can create and which capacities come with add-ons. Limits keep pricing fair and costs predictable. They also create moments of friction when an organization reaches one.

How a platform handles those moments says a lot about how it treats people. We try to enforce limits clearly, fairly and without surprises. Here is how.

Check before the action, explain the reason

When someone tries to do something that would exceed their plan, the check happens before the action, and the person sees a clear notice explaining which limit applies. For example, creating a blog category beyond the plan's limit shows a notification rather than failing silently or saving something half-way.

The message names the limit, shows where the account stands and points to the next step, usually an upgrade or an add-on.

Enforced on the server

Limits are enforced where actions run, not only in the interface. A limit that only hides a button can be bypassed. Our checks run on the server for each action, the same way permissions do, as described in a hidden button is not security.

Existing data is never deleted to fit a limit

Changing to a smaller plan does not delete content to make it fit. Existing pages, posts, files and records stay where they are, and the limit applies to creating new items beyond the plan. Organizations should never lose work because of a billing decision.

Usage is visible

Organizations can see their usage against their limits, such as storage used or the number of websites in the account. Visible usage lets people plan ahead rather than discovering a limit at an inconvenient moment.

Upgrades are straightforward

When an organization needs more, upgrading should be simple. Plans and add-ons can be changed from the billing area, and the new limits apply once the payment is confirmed. Prices are shown before purchase, and paid access is granted only when the payment is verified, as explained in only a verified payment signal grants paid access.

Internal and complimentary accounts

Some accounts, such as our own internal accounts, pilots and rehearsal accounts used for testing, may have complimentary plans with generous limits. Those are configured explicitly and recorded, so the reason for an exception is always clear. Exceptions do not leak into other accounts.

Limits that protect everyone

Some limits exist not for pricing but for safety: radius limits on searches that call paid services, monthly spending caps on outside providers and limits on automatic charges per day. Those protect organizations from runaway costs and protect the platform from abuse. They are described in plain terms in the relevant settings.

Limits are set in one place

Plan limits are defined on the plans themselves and managed by our administrators, not scattered through code as fixed numbers. Each check asks the same plan service whether an action fits, which keeps limits consistent across modules. When a plan changes, every module sees the new limit at once, and nobody has to hunt for an old number buried in a feature.

Grace for timing

Some limits involve timing, such as access that lasts until the end of a paid period. When a subscription is not renewed, access continues through the period that was already paid for and then ends as described, rather than disappearing the moment a renewal fails. Clear dates on billing pages tell organizations exactly when a change takes effect.

Messages written for the person reading them

A limit message is often seen by someone who did not choose the plan, such as a volunteer adding a blog category or a staff member uploading photos. So messages avoid billing jargon and explain the situation simply: what limit was reached, that nothing was lost and who in the organization can change the plan. That small courtesy prevents confusion and unnecessary support requests.

Fairness in both directions

Clear limits are fair to organizations, who know what they are paying for, and fair to the platform, which needs sustainable pricing to keep serving everyone. Handling limits with clear messages, visible usage and respect for existing data keeps that fairness from feeling like a trap.

Frequently asked questions

What happens when I reach a plan limit?

You see a notice explaining which limit applies and how to increase it, before the action runs. Nothing you already created is removed.

Will downgrading my plan delete my content?

No. Existing content remains. Lower limits apply to creating new items beyond the plan.

Can I see how close I am to my limits?

Yes. Usage such as storage and website counts is visible so you can plan ahead.