Plan limits

How Signalync meters usage, what counts as a signal in versus a delivery out, and what happens when a limit is reached.

Plans and quotas

Plans and prices are published dynamically on the pricing page, which is always the source of truth for current tiers, prices, and quota numbers. This page explains what the quotas mean and how they are enforced.

Every plan defines two monthly usage quotas: signals in and deliveries out. Both are enforced, so inbound signals and per-Destination deliveries each draw down their own quota. Each plan also sets how many Sources and Destinations your account can have.

Free trial

Every new account starts a 14-day trial with all features unlocked, no credit card required. There is no permanent free tier: when the trial ends without a subscription, the account moves to the expired state described below.

Signals in vs deliveries out

Signalync meters usage along two independent axes: signals in and deliveries out.

Signal in

One inbound signal that reaches a Source, regardless of how many Flows or Destinations it fans out to. A TradingView alert firing once, or a signal sent manually from the dashboard, counts as exactly one signal in.

Delivery out

One successful dispatch of a signal to one Destination. If a single signal fans out through a Flow to three Destinations, that is one signal in and three deliveries out. Both axes are metered independently.

The practical implication: a single high-fan-out Flow (one Source feeding many Destinations) consumes deliveries faster than signals. The Usage page shows both counters against your plan quotas in real time.

Only deliveries that actually go out are metered. A delivery that a Rule filters out, or one that fails to dispatch (for example, because the Destination is offline), does not count against your deliveries quota. Likewise, a signal rejected as unparseable does not count against your signals-in quota.

Rate limits

Separately from monthly quotas, Signalync applies short-window burst limits to sensitive endpoints such as login, registration, and password reset. These burst limits protect platform stability and are not plan-specific.

A request that exceeds a burst limit receives a 429 Too Many Requests response with a Retry-After header telling the client when to try again.

Quota reset

The monthly usage counters, signals in and deliveries out, reset at the start of each calendar month (UTC).

Source and Destination limits are not counters and never reset; they are fixed properties of your plan. Upgrading your plan takes effect immediately with prorated billing; downgrading takes effect at the end of the current billing period.

When a plan expires

When the trial ends without a subscription, or a subscription lapses, the account moves to an expired state. Your dashboard, signal history, and settings stay fully accessible, but signal processing pauses and inbound signals are rejected. Subscribing again restores processing immediately.

Overage behavior

Signalync does not silently keep processing after a quota is exhausted. Signals are rejected with an explicit error so you know exactly when a limit was hit.

Signals-in quota reached

Once the monthly signals-in quota is used up, the inbound endpoint rejects further signals with an HTTP 402 response and the error code QUOTA_SIGNALS_IN. Rejected signals are not stored or processed. Processing resumes automatically when the counter resets, or immediately after an upgrade.

Deliveries quota reached

Signals are still accepted while the signals-in quota lasts, but every dispatch beyond the deliveries quota is blocked and recorded as a failed delivery with the error QUOTA_DELIVERIES. Fan-out can be partial: deliveries that went out before the quota ran out are unaffected.

Rate limit hit

Requests that exceed a burst limit receive 429 Too Many Requests immediately. The request is not queued or retried; the client should wait for the Retry-After interval and try again.