Overview

Intempt gates a small set of limits by your organization's subscription tier: how many seats and projects you can have, how many AI credits your seats get each month, your API rate limit, and (on the Free tier only) monthly caps on metered usage like analytics events and journey sends. These limits apply at the organization level and are shared across every project in that organization, except where noted.

Plan limits

📘 Good to know

Upgrading is the only way to raise the seat, project, or API rate limit caps above what your current tier allows. There's no per-project override.

Free-tier metered usage caps

The Free tier also caps a handful of metered products. These caps apply per organization, reset monthly, and don't exist on Pro, Organization, or Enterprise, where the same meters are unlimited.

When a Free-tier organization crosses one of these caps, Intempt blocks further usage of that specific meter, for example pausing active journeys that send through the capped channel. The usage counter itself resets automatically every month, but a paused journey, experience, or feed doesn't resume on its own. You need to resume it manually or upgrade the organization. Analytics is the exception: event ingestion resumes automatically once the counter resets.

Use cases

1. Confirm you can invite another teammate. Check the seat limit before sending an invite; Free tier tops out at one seat.
2. Plan a second project. Free tier is capped at one project, so a second product or environment means upgrading to Pro or above.
3. Size a journey campaign before launch. On Free tier, check the email, SMS, and push send caps against your expected campaign volume so a send doesn't get blocked mid-month.
4. Budget AI credit usage across a team. Multiply the per-seat monthly credit allowance by seat count to estimate how much Blu usage (Ask, Recipes, Creative Studio) your organization can run before topping up.
5. Design around your API rate limit. Check the requests-per-minute cap for your tier before building a high-volume integration against the Intempt API.
6. Decide whether Organization tier is worth it for compliance. Audit log retention only starts at Organization (30 days) and extends to a full year with API export at Enterprise.
7. Explain a blocked journey to a customer. If a Free-tier organization's emails or SMS sends stop going out, check the metered usage caps table first, since blocking there is the most common cause.
8. Choose custom roles for a large team. Free and Pro only offer default and standard roles; Organization adds role presets and Enterprise supports fully custom roles.

Where to go next

• Usage & billing for how billing cycles and usage-based charges work.
• Organizations & projects for how orgs and projects relate to each other.
• API Keys for the keys your integrations use against your API rate limit.