Limits and fair use

GitStack prices plans by the members on your private repos. Repos, storage, sync operations, and API traffic are fair use: each has a ceiling that keeps one namespace from slowing the service down for everyone else, and this page lists them. For prices, member counts, and how billing works, see Billing and plans.

These are ceilings, not meters. Crossing one slows you down; it never produces a surprise invoice. If your work needs more, email [email protected] and we can raise it.

API rate limits#

Rate limits are per account and apply to API tokens: requests made with a token, such as the gs CLI or an agent. An account gets the highest rate among its own plan and the plans of the organizations it belongs to, so a member of a Pro organization gets 300 requests per minute even on a Free personal account. All of an account's tokens share its pool, so issuing a second token does not buy more throughput. Browsing the web UI with a signed-in session does not count against the pool, and neither do git operations: pushes are bounded by the sync-operation and storage limits below, and clone and fetch are not metered.

Sync operations#

Sync operations are counted per namespace. One sync operation is one push or one GitHub mirror event. A push counts once no matter how many reviews it updates.

At the limit, requests are throttled. Sync operations are never billed as overage.

Repos#

Storage#

Git objects count toward storage. The namespace allowance is pooled across its repos, and any one repo still stops at the per-repo cap.

GitStack stores source history. Hosting build artifacts, datasets, or model weights is unsupported on every plan.

Traffic and automation#

Clone and fetch are not metered, and public repos are free to clone. A repo whose traffic looks like a download mirror or CDN rather than development, or automation that pushes or calls the API far beyond what a team of people would, falls outside fair use even when it stays under the numbers above. For traffic like this, we email you before limiting anything.

What a member is#

A member is an account with access to a namespace's private repos. Every plan counts members per namespace for access, while billing counts organization members, so a personal namespace is one seat.

Accounts are always free. Anyone can sign up, work in public repos, and run the full workflow solo. Public repo participation never counts toward a member limit. See Billing and plans for the member count on each plan and how members are billed.

Where each limit applies#

Enforcement#

Going over a limit means throttling. Requests are slowed or refused until usage drops back under the limit or we raise it for you. Nothing is deleted and nothing is billed as overage. A namespace that drops to Free while it is over the Free limits also goes read-only for pushes; those rules are in Billing and plans.

Abuse is separate from a quota. Abuse means spam, malware, cryptomining on GitStack infrastructure, artifact dumping, and circumventing metering. We respond in three steps: a warning, then suspension, then deletion after 30 days. Export stays available at every step, so you can always take a full copy of your repositories before anything is removed.