You've built the perfect TradingView indicator. The alert fires exactly when you want to trade. Then you spend the next two minutes manually opening a position on your exchange — and the candle you timed perfectly has already closed. VolatiCloud's new webhook integration changes that: a TradingView alert can now directly force-enter or force-exit a pair on your live bot, with no intermediary step.
Cross-organization forking has been removed from VolatiCloud. A fork now always lands in the organization you are working in: the Fork Strategy drawer shows that organization without a selector, and you choose which of its workspaces receives the fork. The Organization dropdown, the cross-organization scenarios and the target-organization permission checks described in this post no longer apply. For the current flow, see the Strategy Forking documentation.
You've tuned a BTC/USDT mean-reversion strategy that consistently performs well in your main organization. Now you want to run it for a second account on a different exchange — but under a separate organization so billing, API keys, and team members stay isolated. Without cross-org forking, your only option is to copy the strategy code by hand, which immediately creates two diverging copies you'll have to maintain forever. VolatiCloud's cross-org strategy forking solves this by letting you fork any version of a strategy directly into a different organization or workspace you belong to, in one click, with no manual code copying.
Your bot's all-time profit chart can look healthy for months while the bot quietly stagnates or loses ground in the background. The 7-day PnL block on every bot card was built to surface exactly that signal — not what your bot has done since it launched, but what it has done in the last seven days.
Your bot's Overview tab says "1 open position." You click over to the Trades tab to examine it — and the table says "No trades found." The position is right there, live, consuming capital, and the Trades tab acts like it doesn't exist.
That gap is now closed. The Trades tab on every bot detail page shows live open positions in a dedicated table above your closed-trade history, refreshes automatically on every trade event, and all three filter states — All, Open, Closed — now work correctly.
Your Kubernetes bot is running — you can see it in the list, the uptime counter is climbing — but every live monitoring tab shows a banner: "Live monitoring is currently unreachable. The bot may still be running." The trades feed is empty. The equity curve is blank. You have a running bot and no visibility into it.
You reach over to stop last night's paper-test bot, click the one at the top of the list, and realize a beat too late that it was your live Binance bot holding 0.4 BTC. Nothing broke this time. But a single flat list of every strategy, bot, exchange, and runner you own is exactly the setup where that mistake eventually costs real money. As your portfolio grows — multiple assets, separate environments for testing and live trading, different risk profiles for different market conditions — that flat list stops being convenient and becomes a liability. Workspaces are VolatiCloud's answer to that problem.
Your bot closes a winning trade at 3 AM. The exchange confirms the fill. Freqtrade logs it. And then the Kubernetes node gets recycled during a cluster upgrade — and the trade disappears. No history. No PnL record. No data for the next backtest.
VWAP — Volume Weighted Average Price — is the benchmark that institutional desks use to evaluate every trade they make, yet most retail crypto bots run entirely without it. If your strategy only uses price-based moving averages, you're missing the signal that professional traders watch most closely.
Before you deploy real capital, it's worth spending five minutes understanding how platform costs work. VolatiCloud uses a two-layer billing model — a monthly subscription that unlocks features, and a credit balance that fuels compute — and the two layers work independently. Understanding them prevents surprises and helps you pick the right plan from the start.
Managing a crypto trading organization means balancing two things that rarely cooperate: operational speed (bots that restart automatically, sessions that stay unlocked so backtests can run overnight) and data security (passphrase-gated decryption, runner isolation, per-action proof of key knowledge). Until now, configuring that balance required setting five or six independent flags — and nothing stopped you from reaching a state that was technically impossible, like enabling Strict mode without passphrase encryption first.