3Commas Worth It? Fees, Webhook Tutorial vs Direct

You pay $20/month to 3Commas to pipe TradingView alerts (the notifications that fire when chart conditions are met) into its Signal Bot, and your exchange account executes trades. It's genuinely not hard anymore.

Nobody tells you upfront: half of what 3Commas charges is saving you a weekend of wiring webhooks yourself — a webhook is the channel that auto-delivers alert signals to another service — and the other half is letting them custody your exchange API key (the credential that lets programs place orders and query data on your exchange).

You weigh those two costs differently, and so does your decision to pay them.

This article doesn't evaluate whether 3Commas' strategy logic is good or bad, nor does it push you toward "the right bot" — we haven't run that kind of competition. We cover three things: what the official pricing actually buys, the correct sequence for sending TradingView alerts through, and what you save and sacrifice by connecting a webhook directly to an exchange instead.

Fee tier 1: how the three pricing tiers actually work

3Commas' pricing page lays out two prices side by side: the big number is annual ÷ 12, and the crossed-out one is the real monthly price ([3commas.io/pricing](https://3commas.io/pricing) verified 2026-09-15).

This is a common layout, same as Netflix — if you don't notice, you'll assume that's what you're charged each month.

Here's how the three tiers divide labor on a common baseline."The number of simultaneously running bots" is the key metric — it determines whether you can run multiple strategies at once.

This is where Pro becomes the real game-changer: it's the only entry-level tier that unlocks Futures (including Inverse, i.e. coin-margined contracts), and it's where Signal Bot capacity jumps from 2 to 20.

If your strategy only runs spot and you have one or two bots — Starter is fine; once you need futures or want to run multiple different instruments simultaneously, you'll be pushed to Pro.

Fee tier 2: what you're actually buying — the four bot products

3Commas' core products are currently four: DCA Bot, Signal Bot, Grid Bot, SmartTrade. These four names appear exactly like that on each product page at 3commas.io, and the footer navigation matches (verified 2026-09-15).

If you searched "3Commas tutorial" and landed here — you probably want to run the "TradingView signal auto-trade" path — then what you actually need is just Signal Bot.

DCA Bot and Grid Bot are two separate independent products; you don't need to pay for them.

Tutorial: the correct sequence from TradingView alert to 3Commas

The official setup flow on 3commas.io/trading-view has three steps — here listed in order with the exact step names and descriptions from the How it works section's three h3 headings (verified 2026-09-15):

In step 2, the "paste into TradingView Alert" action has athreshold that 3Commas can't control — webhooks are only available on paid TradingView plans, and no amount of 3Commas payment bypasses this.

Which TradingView plan supports webhooks and what the pricing difference is, I wrote a separate article [which of TradingView's five plans supports webhooks](/blog/tradingview-plans-webhook-comparison), so I won't repeat it here.

The payload skeleton that actually gets pasted into the TradingView Alert message box looks roughly like this. When implementing, always use the message auto-generated by your own dashboard Signal Bot page — fields like bot_id, email_token, and trading pair are tied to your account.

{
          "message_type": "bot",
          "bot_id": 12345678,
          "email_token": "xxxx-xxxx-xxxx",
          "delay_seconds": 0,
          "pair": "USDT_BTC"
        }

Gap 1: where your key lives (and a nod to the 2022 incident)

3Commas' architecture — called Sign Center on their official site at 3commas.io/security — isencrypting and storing keys on their servers, with Sign Center signing trades on your behalf.

The official wording is"When 3Commas makes a trade request with an exchange, 3Commas servers ask the Sign Center to sign the transaction. This protocol is similar to how Metamask or Ledger signs a transaction."(verified 2026-09-15).

This mechanism went live on November 16, 2022 — over a month before the API data leak incident was publicly disclosed on December 28 that same year.

On December 28–29, 2022, 3Commas' API data leak became public. In their [notice-on-api-data-disclosure-incident](https://3commas.io/blog/notice-on-api-data-disclosure-incident) post, 3Commas stated that"API keys, secrets and passphrases" — the three credentials needed to connect to exchanges — had been disclosed by a third party.

The same notice asked Binance, KuCoin and other exchanges to revoke all keys connected to 3Commas. To date, 3Commas has not published a total loss figure — their position is that it will be disclosed once the investigation concludes.

The choice of where keys are stored is the biggest structural difference among custodial bot platforms, and it should be read alongside monthly pricing.

Gap 2: the TradingView threshold, outside 3Commas' control

There's a common misconception to separate: paying for 3Commas does not mean webhooks are active.

The signal source is TradingView, and TradingView locks the "webhook notification" feature behind paid plans. The FAQ at the bottom of 3commas.io/trading-view states directly"Yes. Webhooks are available only on paid TradingView subscriptions." — a single sentence that means you need to budget for both sides.

So the real monthly cost adds up: 3Commas $20/$50/$140 (or annual $15/$38/$105) + at least one paid TradingView tier.

I haven't included exact TradingView plan prices because they change frequently; check the current amounts on their site as of 2026-09-15.

Gap 3: connecting webhook directly to an exchange — what you save, what you sacrifice

Within the 3Commas Signal Bot path, "what you're paying them for" breaks down into roughly four things: signal validation (webhook URL carries a token), API key custody, position sizing, and order retry.

You could write all of these on your own server, or use a non-custodial middleman platform — for example, connecting yourself via ccxt (an order-execution library covering 100+ exchanges), or one of the tools from [the crypto alternatives to PineConnector](/blog/pineconnector-alternatives-crypto).

Neither is the "right answer" — they optimize for different goals.

The reason 3Commas charges $20–140/month isn't that they do something you can't, but that they package those engineering details into a ready-to-use product.

A reasonable reason to pay this is "a weekend of engineering time is worth more to me than the monthly fee," not "others can't build it."

An honest section: 3Commas does have its place

We don't intend to paint 3Commas as something you should never use.

Its niche is for people who "don't want to code, don't want to evaluate options, just want signals running"; paying the monthly fee is buying time saved from evaluation. For some people, that's genuinely worth it.

Three situations where it isn't worth it: (a) you already know how to integrate APIs,(b) your key absolutely cannot leave your own machine,(c) the exchange you need isn't on their 9-exchange list.

If any of these apply, this fee becomes "saving you a weekend while tying up other choices."

For that technical question, there's also a middle path: send signals to a non-custodial middleman that forwards them to exchanges.

For example, TVSBot's execution layer resolves position size and account identity at order time, accepting only trade-permission keys (withdrawal disabled) — this is a compromise between "don't want to self-host" and "key location."

Either path works; the key is thinking clearly about why you pay this fee, so you don't look back and ask "what could I have done differently" when 3Commas has another incident.

FAQ