Appearance
Usage and quotas
Each plan comes with limits. The Usage page shows how close your organization is to each one. Open it with Account → Usage, or with View usage details on Account → My Organization. The account pages are inside the app today and will move to collapy.com later.
Usage is counted per organization: everyone's activity in all of the organization's workspaces adds up. The page shows the organization that's currently selected in the top bar.
The Usage page
Current usage shows a meter for each limit, as "used / limit", or "used · Unlimited" when your plan has no cap:
| Meter | What it counts |
|---|---|
| Team members | People in the organization, including pending invitations. |
| Collaborative workspaces | All workspaces in the organization, including Personal. |
| Monthly cloud executions | Requests sent this month. Resets at the start of each UTC month. |
| Stored request history | Entries in the organization's execution history. Rolling cap: the oldest entries are removed every 30 minutes. |
A meter changes color as you approach the limit: amber from 80%, red at 100%.
Below the meters, Plans shows the three plans, with Current plan on yours, and a comparison table. See Plans and limits.
Banners
Account → My Organization shows banners when a limit needs attention:
| Banner | When it appears |
|---|---|
| Over the limit (red) | The organization has more members, workspaces or monthly cloud executions than its plan allows. It lists each one with its usage and limit. |
| Monthly cloud executions | From 80% of the monthly limit (amber). Turns red once the limit is reached. |
| Stored history (oldest trimmed every 30 min) | From 80% of the stored history limit (amber). |
When everything is under 80%, no banners are shown.
Two different limits
Monthly cloud executions and stored request history sound alike, but they work differently.
Monthly cloud executions
- What counts: every request you send from the web app, because the web app sends it through Collapy's cloud. Test runs count too, one per request they send.
- When it resets: at 00:00 UTC on the first day of each month.
- What happens at the limit: sending from the web app is blocked until the next month. Sending fails with
Monthly execution quota exceeded. - Limits: depend on your plan. See Plans and limits.
Web app
Requests are sent through Collapy's cloud, so they count toward your monthly cloud executions.
Desktop app (coming soon)
Requests go straight from your computer and aren't blocked by the monthly cap. They are still recorded, and currently show up in the Monthly cloud executions count.
Stored request history
- What counts: entries in execution history, across all of the organization's workspaces.
- What happens at the limit: nothing is blocked. Collapy removes the oldest entries automatically every 30 minutes. If you're far over the limit, this can take a few rounds, so the count may stay above the limit for a while.
- Limits: depend on your plan. See Plans and limits.
If you need old responses, copy what you need before they're removed. Execution history can't be exported.
Seats and workspaces
- Team members: you can't invite anyone once the organization is at its seat limit. See Members and roles.
- Collaborative workspaces: you can't create or duplicate a workspace once the organization is at its workspace limit. See Workspaces.
If you're already over a limit
Collapy never deletes members or workspaces to fit a limit. If an organization has more than its plan allows, for example after a downgrade, everything stays as it is. Only new additions are blocked. The red over-the-limit banner on My Organization stays until you're back under the limit, by removing members or deleting workspaces.
If your plan gets smaller
When an organization moves to a smaller plan:
- Members and workspaces over the new limits are kept. You can't add more until you're under the limits.
- Monthly cloud executions: the smaller limit applies straight away, to the executions you've already used this month. If you're already past it, sending from the web app is blocked until the month resets.
- Stored request history: the smaller limit applies right away. The oldest entries are removed over the next runs, up to several hundred every 30 minutes.
- Leaving Ultra: change log entries are removed, synced workspaces stop syncing (their requests stay), the Audit Log page is no longer available, and test runs go back to one environment at a time.
To change plans, contact Collapy support. Self-service billing isn't available yet.
FAQ
Why does the usage number differ from what I expected?
Usage is counted for the whole organization, not just for you. Members, executions and history from every workspace in the organization add up.
Does stored history ever stop me from sending requests?
No. Only the monthly cloud execution limit can block sending. The history limit only removes old entries.