Upstash
VerifiedVerified limits for Upstash, each with its official source, last-verified date, and what the rule means in practice.
What we can show
for Upstash
Each row pairs a number with its official source and last verified date. Where the registry has not yet produced a limit value, the metric appears below the table as Not certified yet rather than a guess.
Monthly commands
Monthly commands measures the commands / month reported by the provider. It resets at the start of each calendar month. Treat it as a usage this cycle; once it resets, the count starts over.
request limit reached; provider behavior is plan-dependent
Current storage
Current storage measures the bytes reported by the provider. It never resets automatically. Treat it as a cumulative capacity; once full, it does not reset automatically.
storage limit reached; provider behavior is plan-dependent
Limit not available yet
Monthly bandwidth
Monthly billing
These metrics are registered but do not yet have a dashboard-reconciled limit value with a verified source. They will move up into the verified table as reconciliation completes.
What we can read
and what we cannot
BeforeRed tracks a small, deliberate set of capabilities per provider. The table below shows the registry state for Upstash today. A Certified row is one we can defend in front of a customer; the other states are honest about what is still in progress.
How BeforeRed reads
that number
The integration page for this provider explains the connect flow, the read-only OAuth scopes we request, and what we do once a sync finishes. It is the bridge between this limit and the dashboard the user sees.
Tell us. A limit that has drifted between the provider and this page is a high-priority fix and we treat it as one. If a row is missing a source, that is a publish-grade bug in our eyes too.