Limits Policy
Last updated:
We publish our limits up front, in plain numbers: no hidden meters, no credit pools, and no charges for going over. This page lists the limit for every plan and explains how each one is counted. If your team needs more than a published plan offers, get in touch and we will sort something out.
1. How limits work
Every plan has published limits, and we never bill you for going over. Your bill changes only when you choose to change it, and you get a heads-up before you reach a limit.
- 80% of a limit. A banner appears in your dashboard so you can plan ahead, and we email the organization that owns the project. We send at most one email per threshold for each limit per calendar month, so you will not get repeat mail about the same one. If the limit itself changes, because you add capacity or change plans, the new limit gets its own heads-up.
- 100% of a limit. The next action of that type stops with a “limit reached” message, and the dashboard shows you what you can do: add capacity where your plan sells it, upgrade, or get in touch. Inbound webhook deliveries are the exception and are held rather than refused, as described under monthly usage.
Limits are checked the moment you act, so two requests at the same time can never push you past a limit, and any action that does not complete never counts against you.
Reaching a limit never deletes anything you already have. Two things are removed on a schedule of their own, archived feedback and attachments on finished feedback, and section 5 sets out both in full.
2. Capacity
What you can have at any one time, counted live from your account.
| Resource | Free | Builder | Pro | Business |
|---|---|---|---|---|
| Projects | 1 | 1 | 3 | 5 |
| Feedback items | 100 | Unlimited | Unlimited | Unlimited |
| Team members | 2 | 3 | 10 | Unlimited |
| Storage | 512 MB | 20 GB | 175 GB | 450 GB |
The figures above are what each plan includes. Some plans also let you buy more of one of them, up to a published ceiling. Extra capacity is added only when you ask for it, from your billing page, and filling a plan's ceiling never costs more than upgrading to the next plan.
- Pro can add up to 40 seats, at $9 each per month, or $7.10 each per month on an annual plan.
- Business can add up to 10 projects, at $49 each per month, or $39.20 each per month on an annual plan.
3. Monthly usage
What you can do in a single calendar month. The counters reset on the 1st, at 00:00 UTC.
| Resource | Free | Builder | Pro | Business |
|---|---|---|---|---|
| AI synthesis operations | 150 | 2,000 | 10,000 | 50,000 |
| Spec drafts | 3 | 15 | 50 | 200 |
| API write operations | 0 | 1,000 | 5,000 | 25,000 |
| Inbound webhook events | 5,000 | 500,000 | 3,000,000 | 12,000,000 |
Inbound webhook deliveries are the one row here that does not stop outright. Your connected tools send events on their own schedule and most will not send the same event twice, so refusing one would lose it for good. When you run out we hold new deliveries and send them through as soon as there is room, oldest first. A held delivery counts against the month it is processed in, not the month it arrived.
We hold up to 50,000 deliveries per organization, and a held delivery is dropped if it is still waiting after 45 days. That window is longer than a billing period, so nothing expires purely because it was waiting for your counter to reset. If the holding area fills up we email the organization owner and discard new deliveries until there is room. A single delivery larger than 1 MB is too big to hold and is discarded rather than queued.
4. What counts
Here is exactly what each row counts, so a number on this page is never a surprise.
- Projects
- A distinct workspace inside your organization. Each project has its own categories, statuses, members, and portal.
- Feedback items
- A single feedback item in a project. Comments, votes, and attachments on the same item do not count separately. Archived feedback does not count, so archiving old items frees up room.
- Team members
- A person in your organization: every member counts once, no matter how many projects they belong to, and a pending invitation reserves a seat until it is accepted or expires. People your identity provider adds automatically through single sign-on or directory sync count the same way, one seat each. Portal contributors and anonymous voters are unlimited and do not count.
- Storage
- Every file you are currently storing with us: attachments on feedback and comments, plus your portal logo, favicon, and banner, project images, and roadmap covers. This is what you are using right now, not a monthly total. Delete a file, or the feedback it is attached to, and the space comes straight back. Files that reach the end of their retention window free up their space too, and section 5 explains when that happens.
- AI synthesis operations
- One AI pass over your feedback: either the understanding pass that reads a new or edited item (finding what it asks for, placing it in a theme, and suggesting a category) or a theme synthesis that names and summarizes a theme. Editing an item without changing its meaning is not counted again. Two things are never counted: the search indexing we run on feedback in the background, and the work we do to keep themes tidy, such as merging duplicates or rebuilding after we change our own models.
- Spec drafts
- One product spec drafted from a theme. Available on every plan, with its own monthly allowance separate from AI synthesis operations, because each draft is a much larger generation.
- API write operations
- Any call made with a project API key that changes something in your project (a status change, a comment, or a roadmap link), whether it arrives through the MCP server or the REST API. Both use the same key and the same allowance. Reads do not count toward this limit. Drafting a spec counts against the spec allowance instead, never both.
- Inbound webhook events
- One accepted delivery from a connected integration (GitHub, Linear, Jira, Intercom, Slack). Rejected deliveries (invalid signature, disabled integration) and duplicate retries do not count, and neither does a delivery that turns out to carry nothing new, such as an echo of a change we made in the connected tool ourselves.
5. How long we keep things
Almost everything you create is kept for as long as your project exists. Two things are not, and both are set out here.
- Archived feedback. Archiving is how you free up feedback capacity, and it is not a recycle bin: an item that stays archived for 90 days is permanently deleted, along with its comments and attachments. Restore anything you want to keep before then. Nothing that is not archived is ever removed this way.
- Attachments on finished feedback. A file attached to feedback or a comment is removed only once both of these are true: it is older than your plan's retention window (90 days on Free, 180 days on Builder, 365 days on Pro, and no expiry on Business), and the feedback it belongs to is closed or archived. The window runs from when the file was uploaded, so closing an old thread can make its files due straight away, while a file on open feedback is never removed however old it is. Reopening an item keeps its files for as long as it stays open and withdraws any notice we had already sent. We email the organization owner 7 days before anything is removed, with the count and the date, so there is time to download the files or upgrade to a plan that keeps them longer. The feedback itself stays and shows without the file. Portal logos, favicons, banners, project images, and roadmap covers are configuration rather than content, and are kept for as long as the project exists.
Attachment removal pauses for as long as an organization's subscription is paused or lapsed, so a billing problem never costs you files.
Separate retention periods apply to account data, logs, and backups. Those are set out in the Privacy Policy.
6. Abuse protection
Separate from the monthly limits, we apply short-window rate limits to expensive operations (AI synthesis, spec drafting, API writes and searches, webhook ingestion, starting a checkout, and manually re-running an integration sync) to guard against runaway loops and scripts. These limits sit well above normal usage, so hitting one usually points to a misconfigured integration. When you are the one asking, the response is a standard 429 Too Many Requests with a Retry-After header. When a connected tool is the one sending, we hold the delivery and process it shortly afterwards rather than refusing it, for the reason given under monthly usage. On public portals we may also ask a visitor to pass a bot check before their first vote, comment, or submission.
7. Changes
We publish changes to these limits in the same place we publish pricing changes, and we never quietly tighten a limit. If a number on this page goes down, we give at least 30 days’ notice here and on the pricing card before the change takes effect.
8. Questions
Questions about a limit, or need more room than a published plan offers? Email support@insightloop.io. You can also compare plans or read the Plans and billing section of our Terms of Service.