Sites and agencies

A Formsieve plan covers a number of sites, and all of them share the plan's monthly AI checks. This page explains what counts as a site and how agencies use one key for many client sites. Plan limits are as of 2026-09-25; current plans are at https://formsieve.com/pricing/.

What counts as a site

A site is one production WordPress address, for example example.com or example.com/shop. The address is compared in lower case, without https://, www., a trailing slash, a trailing dot or the default port.
Each subsite of a WordPress multisite network counts as its own site.
A site takes its slot the first time it checks a submission or runs Test connection with the key. Settings → Connection and the dashboard show whether this site has a slot.

Staging and development sites

Staging, development and local copies never use a site slot. Formsieve treats a site as non-production when WordPress reports an environment other than production (WP_ENVIRONMENT_TYPE), or when its address looks like one: localhost, an IP address, a name ending in .test, .local, .localhost, .invalid or .example, or a name starting with staging., stage., dev. or test..

Their AI checks still count toward the monthly allowance. Solo, Pro and trial keys accept at most 10 non-production addresses at a time; remove old ones in your account when you reach that. The Free plan covers one production site. Staging and development sites need a paid plan (as of 2026-09-29).

When the plan's sites are used up

A new production site then gets "This site is not on your Formsieve plan": its forms keep working with the free local checks, and submissions are delivered (or held for review, if you chose that), never blocked. To make room:

remove a site you no longer use in your account (Sites → Remove): the slot is free at once, and that site's AI checks stop until it registers again;
deleting the plugin, or Disconnect under Settings → Connection, also frees the site's slot;
or upgrade to a plan with more sites.

After a downgrade to a plan with fewer sites, the account asks which sites to keep. If you changed the plan elsewhere (for example in the Stripe billing portal), the sites added first keep working and the ones added most recently are refused until you remove sites or upgrade.

One trial is allowed per site: a site that already ran a trial cannot start another one with a new key, whatever port, path or environment it reports. In the same way, a site gets the Free plan's AI checks with one key only (as of 2026-09-29); with another key Formsieve says "This site already used a free Formsieve allowance with another key, so the AI check is paused here."

Agencies

The Agency and Scale plans cover unlimited production sites. Fair use (as of 2026-09-25): sites you own, or build and maintain for your clients. Bundling the key into hosting plans or reselling it is not covered; hosting companies can ask for a Custom plan.

One line for every site. Put the key in each site's wp-config.php, so it never sits in the database and a client cannot copy it from the settings:
```
define( 'FORMSIEVE_API_KEY', 'FS-XXXX-XXXX-XXXX-XXXX' );
```
The constant covers every form plugin Formsieve protects on the site. Sites that still define the earlier plugins' constants (FSV_GF_API_KEY, FSV_CF7_API_KEY) keep working until version 1.2.0; rename them to FORMSIEVE_API_KEY.
Per-site usage. Your account's Sites and Usage pages show the AI checks of each site this month, so you can see which client uses what.
Your clients' data. When you run a client's site, Formsieve's service processes its submissions as your sub-processor. The Data Processing Agreement at https://formsieve.com/dpa/ covers that chain.
Rotating the key. If a key leaks, rotate it in your account. The previous key keeps working for 24 hours, so you can update your sites without a gap.

A key that suddenly appears on many new sites in one day is paused for new sites (at most 200 new addresses a day, as of 2026-09-26), so a leaked key cannot run up usage on your plan.