Rowy · Rate Limits

Rowy Rate Limits

Rowy does not publish its own API rate limits. Its webhooks and Rowy Run services run on Google Cloud Run inside the user's own GCP project, and its data lives in the user's Google Cloud Firestore. Any effective rate limits, quotas, or throttling therefore come from the underlying Google Cloud Platform services (Cloud Run concurrency/instances, Cloud Functions invocation limits, Firestore read/write quotas), not from Rowy. Specific values are not reconciled in this artifact.

Rowy Rate Limits is the machine-readable rate-limit profile for Rowy on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests, invocations, and operations.

The profile also includes 2 backoff/retry policies defined.

Tagged areas include Low-Code, Backend, Firestore, Firebase, and Webhooks.

3 Limits
Low-CodeBackendFirestoreFirebaseWebhooksCloud FunctionsRate LimitingQuotasThrottling

Limits

Webhook Throughput (Cloud Run) gcp-project
requests
governed by Google Cloud Run
Webhooks run on the rowy-hooks Cloud Run service in the user's GCP project; throughput follows Cloud Run concurrency and instance limits.
Cloud Function Invocations gcp-project
invocations
governed by Google Cloud Functions
Cloud Functions deployed via Rowy follow GCP invocation and build quotas.
Firestore Reads / Writes gcp-project
operations
governed by Google Cloud Firestore
Table data operations are bounded by Firestore quotas for the user's project.

Policies

Underlying GCP Limits
All practical rate limits derive from the user's own Google Cloud Run, Cloud Functions, and Firestore quotas rather than a Rowy-imposed limit.
Backoff Strategy
Clients integrating via webhooks should implement retries with exponential backoff and honor Cloud Run / Firestore error responses.

Sources