Skip to main content

Usage and Limits

Corrected — the original page was inaccurate

The original listed "Users" and "Spaces" as tracked/limited metrics, and described specific email notification rate limits. Verified against apps/platform-ui/src/components/UsageInfo.tsx and the subscription/usage services in starhive-development:

  • There is no user (seat) limit today. Usages still has a users field, but nothing validates or caps it, and the current UI doesn't display it.
  • Spaces are tracked internally but not limited or shown in the current usage page either.
  • The email notification rate-limit figures below could not be confirmed anywhere in the codebase — no rate limiter matching those numbers exists in the notification delivery path. They may be configured in the external email provider rather than in Starhive's own code, but that couldn't be verified either way. Treat them as unconfirmed until someone who owns notifications/lifecycle email can confirm the real numbers.

Usage​

Total usage:

  • Objects
  • Storage (MB)
  • Custom domains

Monthly usage:

Limits​

LimitEnforcement
ObjectsNotifies as you approach/reach your plan's object limit.
StorageHard-enforced — file/attribute uploads that would exceed your plan's storage cap are blocked.
Custom domainsEnforced when adding a domain to a Site.
AI creditsEnforced per the monthly allowance on your plan.
Automation creditsEnforced per the monthly allowance on your plan — see
Automation credits.

Email notification limits (unconfirmed figures)​

caution

The figures in this subsection could not be verified against the current codebase (see the correction note above). They may be stale, or may reflect a setting outside this repository. Confirm with whoever owns notification delivery before treating these as accurate.

Starhive is described as limiting how many notification emails one person's activity, and one workspace overall, can generate in a short window — protecting inboxes from a flood that a single widely-watched object change, a bulk import, or a busy automation rule could otherwise cause.

Applies toIn any 5 minutesIn any 24 hours
One person's activity20 emails200 emails
Everyone in one workspace500 emails5,000 emails

When a limit is hit, the remaining emails for that window are described as being skipped, not delayed. Nothing is lost in the app itself: every notification still appears in the in-app Inbox as usual, and the affected person is said to see "Some email notifications were not sent" under Inbox → System messages.

If you're relying on these figures, contact Starhive support to confirm current values rather than trusting this page.