48 posts tagged with "features"

Most trading strategies are designed for one market condition — and quietly bleed when the market changes. An EMA crossover bot that performed well during a strong bull trend will churn through fees in a sideways consolidation. An RSI mean-reversion bot that thrives in ranging markets will get steamrolled by a breakout. Market regime detection is the filter that sits above your entry logic and tells your bot which condition the market is actually in.

Your trading strategy is intellectual property — an algorithm that took months of backtesting, tuning, and real-capital validation to develop. VolatiCloud's passphrase encryption changes who can read it: after setup, neither an insider nor an attacker with full database access can decrypt your strategy code without your passphrase.

Your trading strategy's logic is a competitive asset. A finely tuned MACD divergence filter, a multi-timeframe confluence signal, a DCA ladder calibrated to your risk tolerance — that intellectual work has real value. It lives in your account on our servers, and until now you had to trust that we would keep it safe. With passkey-bound strategy encryption, you don't have to.

Every cloud trading platform faces the same architectural problem: to run your bot, the server must read your strategy code and exchange credentials. VolatiCloud already encrypted API keys at rest with AES-256-GCM, but the encryption key was still platform-controlled. Strict mode changes that — your strategy code, bot configs, and exchange secrets are now protected by a passphrase the platform never holds.

A profitable trading strategy is worth protecting. When you build an edge — a set of conditions, indicator parameters, and logic that consistently outperforms the market — that code represents months of research and backtesting. The question is: once it's deployed to the cloud, who else can see it?

Server-managed encryption protects your exchange API keys from database dumps — but it still means the platform holds both the ciphertext and the decryption key. If the key management system is ever compromised alongside the database, that protection collapses. VolatiCloud's organization passphrase feature adds a second, independent layer: a key derived entirely from something only you know, using an algorithm designed to make brute-force infeasible. Your API keys are encrypted before the platform ever sees the raw values.

Most traders can articulate their strategy in plain English: "buy when the trend is up, momentum is building, but the market isn't yet overbought." Converting that into a running bot is where most people get stuck — not because the idea is wrong, but because turning mental rules into executable code requires a skill set that has nothing to do with trading.

This walkthrough builds a complete three-indicator confluence strategy using VolatiCloud's visual editor — from blank canvas to deployable bot — without writing a single line of code.

Giving a third party access to your exchange account sounds risky. In the worst-case scenario you can imagine, the platform gets hacked, your API keys are stolen, and your funds disappear. That scenario is real — but it is also completely preventable with one setting that costs you nothing to enable: withdrawal-disabled API keys. This post explains what that restriction actually does, the additional layers VolatiCloud enforces on top of it, and how to generate keys that even a full database breach cannot turn into stolen funds.

You're writing a Python trading strategy. You've defined a stoploss, computed RSI in the indicator pipeline, and written your entry conditions. But did you assign the indicator column the same name in populate_indicators and populate_entry_trend? Without inline feedback, the answer waits until your backtest produces zero trades and you spend twenty minutes debugging a typo a linter would have caught in milliseconds.

A bot running on the 5-minute chart has no idea what the 1-hour trend is doing. It will buy breakouts that fight the prevailing trend, hold through reversals that a higher-timeframe RSI would have flagged, and miss entries that only make sense once you zoom out. Multi-timeframe analysis is one of the most effective ways to add context to a strategy — and VolatiCloud now supports it natively, both in code and in the visual builder.