Fair-Use Limits¶
Every feature of Askalot is open to every account. On the free service, a few fair-use limits bound how much one person starts at a time, so that one heavy user cannot slow the service down for everyone else. They are limits on quantity, never on what you can do.
The four limits¶
| Limit | What counts |
|---|---|
| Projects | Projects you created that still exist. Your default Project does not count. |
| Collaborators per Project | The owners of one Project. |
| Active or paused campaigns | Campaigns in the Projects you created that are active or paused. Draft, scheduled, completed and aborted campaigns do not count. |
| Completed responses per month | Responses completed this calendar month (UTC) in the Projects you created, simulated ones included. The count resets on the 1st. |
Your profile page shows each count against its limit, and so does the
get_my_entitlements MCP tool. The badge next to your name in the menu shows
the limit you are nearest to.
Who is charged¶
A Project, its campaigns and its responses count for the person who created the Project. Being added to someone else's Project as a collaborator never uses up your own limits, so an invitation is never refused because of your counts. Removing yourself from a Project you created does not free its slot; deleting the Project does.
Limits are counted per person across every organization you belong to on the free service. A community organization (a university course, a non-profit) can have its limits raised by Askalot; what is created in that organization is checked against the raised values.
What a limit does — and never does¶
A limit is checked only when something new would start:
- creating a Project
- adding a collaborator to a Project
- launching or resuming a campaign, including the launch that happens when you send the first invitation, create an access link, publish an open link or publish a questionnaire to a draft campaign
Reaching a limit refuses only that one action, and the message says which limit, your count, and how to free a slot. If you act on someone else's Project and its creator is at a limit, the message says so without showing their counts.
A limit never:
- removes, hides or locks anything you already have
- stops a running campaign or a survey in progress
- turns a respondent away: every response is recorded, even past the monthly limit. Reaching the monthly response limit only stops you launching or resuming a campaign until the next month
AI agents and simulations acting for you count like you do. A batch simulation creates its own Project and launches its own campaign, so the simulation form tells you before the run starts if that would take you past a limit.
Warnings and the notice period¶
You are warned in the product when a count reaches 80% of its limit, and again at the limit. When the limits are introduced, they are first shown with warnings only, for a notice period of 30 days. The date refusals start is announced to everyone, and emailed to anyone already at or over a limit.