Plan limits
Quota limits across plan tiers, plus a definition of what counts as a 'signal in' vs a 'delivery out'.
Plan tiers
Signalync offers four plan tiers. The Free Trial gives you full Advanced-plan features for 14 days with no credit card required. After the trial ends without a subscription, the account downgrades to the free tier, signal routing stops but the dashboard remains readable.
| Feature | Free Trial | Starter | Advanced | Professional |
|---|---|---|---|---|
| Monthly price | $0 (14 days) | $19.90 / mo | $49.90 / mo | $149.90 / mo |
| Annual price | , | $15.90 / mo | $39.90 / mo | $119.90 / mo |
| Account connections | 4 | 2 | 4 | 10 |
| Signals | Unlimited | Unlimited | Unlimited | Unlimited |
| Signal sources | All | All | All | All |
| AI credits / cycle | 1,000 (trial) | 200 | 1,000 | 5,000 |
| Analytics | Detailed | Basic | Detailed | Detailed |
| Strategy Builder | Yes | Yes | Yes | Yes |
| Strategy Lab (AI) | Yes | Yes | Yes | Yes |
| Symbol mapping | Yes | Yes | Yes | Yes |
| Developer API | , | , | , | Yes |
| Outbound webhooks | , | , | , | Yes |
| Cloud VPS | , | Add-on | Core included | Performance included |
| Backtest reports | 10 | 10 | 30 | 50 |
| Support | Priority email | Dedicated |
Free trial
Signals in vs deliveries out
Signalync meters usage along two independent axes: signals in and deliveries out.
Signal in
One inbound HTTP request that reaches a Source, regardless of how many Routes or Targets that signal fans out to. A TradingView alert firing once, a Telegram message arriving, or a single REST API call each count as exactly one signal in.
Delivery out
One (signal × Target) dispatch attempt. If a single signal fans out through a Route to three Targets, for example, an MT5 account, a Telegram channel, and a Discord webhook, that is one signal in and three deliveries out. Both axes are metered independently.
The practical implication: a single high-fan-out Route (one Source → many Targets) can consume deliveries faster than signals. Check your Usage dashboard to see both counters in real time.
Rate limits
In addition to monthly quotas, inbound signal endpoints are rate-limited per minute to protect system stability.
| Plan | Signal endpoint (per min) | General API (per min) |
|---|---|---|
| Starter | 60 | 120 |
| Advanced | 300 | 300 |
| Professional | 1,000 | 600 |
Requests that exceed the per-minute rate limit receive a 429 Too Many Requests response. The limit resets at the start of the next minute.
Quota reset
Monthly quotas (AI credits, backtest reports) reset at the start of each billing cycle. For monthly subscribers, the cycle resets on the same calendar day each month, the day you first subscribed. For annual subscribers, it resets monthly on the same day of the month.
Connection limits and rate limits are not subject to monthly reset, they are fixed properties of your plan tier. Upgrading your plan immediately increases these limits; downgrading takes effect at the end of the current billing cycle.
Overage behavior
Signalync does not silently continue processing after a quota is exhausted, signals are rejected with an explicit error so you know exactly when a limit was hit.
AI credit exhaustion
Any Step or feature that calls the Claude API (score.ai, filter.ai_probability, Strategy Lab) returns an error when AI credits reach zero. The signal itself is not dropped, only the AI-dependent Step fails. The dashboard shows a credit-exhausted banner.
Rate limit hit
Inbound requests that exceed the per-minute rate limit receive 429 Too Many Requests immediately. The signal is not queued or retried, the sender (TradingView, your script, etc.) must implement retry logic if needed.
Connection limit reached
Attempting to create a new Target when you are already at your plan's connection limit returns a 402 PLAN_LIMIT_CONNECTIONS error. Existing connections are not affected. Upgrade your plan or remove an unused Target to free a slot.