HaasOnline: Platform Profile

Overview

HaasOnline is a crypto trading-automation platform with both hosted and self-hosted deployment options.

Its current product spans:

• visual and scripted bot creation;
• HaasScript;
• backtesting;
• paper/simulated workflows;
• exchange integrations;
• cloud deployment;
• self-hosted TradeServer;
• AI-assisted coding and debugging;
• Model Context Protocol access for compatible AI clients.

The most important current distinction is that HaasOnline's AI access does not have one universal permission model.

In the current Cloud MCP workflow, AI agents can inspect and modify a wide range of bot, script, backtest, market, and portfolio information, but HaasOnline explicitly says the cloud MCP toolset does not include tools to:

• place or cancel trades;
• move or withdraw funds;
• start or stop bots.

That is materially different from assuming an AI assistant receives unrestricted live trading authority.

HaasOnline remains trading software.

Current legal/product-classification materials describe it as non-custodial software rather than a broker, exchange, adviser, or CTA.

May fit better for

• technically sophisticated crypto traders;
• users who want more bot depth than a simple Grid/DCA service;
• traders who want HaasScript;
• users who want cloud or self-hosted deployment;
• users who want long backtest windows on higher plans;
• traders who want AI assistance with code, bot logic, and research workflows;
• users who want an MCP interface without giving a cloud AI agent direct trade-placement tools;
• teams requiring high bot counts through TradeServer.

May fit less well for

• beginners seeking a one-click managed portfolio;
• investors seeking fiduciary discretionary management;
• users who do not want crypto-market risk;
• customers who want one simple permanent feature set across every exchange;
• users unwilling to manage API permissions;
• traders who treat a backtest as a forecast;
• users who assume MCP access automatically means the AI can place trades;
• traders who do not need the platform's scripting and automation depth.

---

HaasOnline is non-custodial software

Current product-classification materials describe HaasOnline as software that connects to third-party exchange accounts.

The customer maintains the exchange account and API credentials.

The economic and operational chain is:

user strategy → HaasOnline bot/software → exchange API → exchange execution → assets remain at exchange.

---

Current pricing ranges from $11.99 to $149.99 per month

The current pricing page shows:

• Starter monthly: $11.99
• Standard monthly: $29.99
• Pro monthly: $59.99
• TradeServer monthly: $149.99
• Enterprise: custom

Current bot limits include:

• Starter bots: 3
• Standard bots: 8
• Pro bots: 20
• TradeServer bots: 100+

Current backtest windows include:

• Starter backtest: 1 month
• Standard backtest: 6 months
• Pro backtest: 12 months
• TradeServer backtest: 36 months

The pricing page also shows a 7-day Standard trial without a credit card.

The page currently advertises a 40% annual discount when paid in crypto.

Keep annual-payment amounts attached to the billing term.

---

Plan differences are substantive

Starter is not merely a lower bot-count version of the entire product.

Current plan materials place more advanced capabilities in higher tiers.

Standard currently adds references including:

• Market Intelligence;
• HaasLabs;
• manual trading;
• AI-agent access through MCP.

Pro increases capacity.

TradeServer provides the large-scale and self-hosted option.

---

Cloud MCP has broad research and authoring permissions but no live trade tool

This is the key Batch 43 HaasOnline guard.

Current Cloud MCP documentation says a connected AI agent can access tools for workflows such as:

• reading bots;
• reading positions;
• reading open orders;
• reading profit reports;
• inspecting logs;
• creating and editing HaasScript;
• compiling scripts;
• running backtests;
• using HaasLabs;
• inspecting markets;
• viewing wallet and portfolio information.

But the same documentation explicitly says the cloud MCP interface does not expose tools to:

• place trades;
• cancel trades;
• move funds;
• withdraw funds;
• start bots;
• stop bots.

That boundary matters.

An AI agent can still make destructive changes to code, scripts, configuration, or research artifacts if the user authorizes broad access.

But current Cloud MCP access should not be described as:

Claude can directly trade your HaasOnline account.

That overstates the current tool surface.

---

Self-hosted TradeServer has a different architecture

HaasOnline also supports self-hosted TradeServer.

Self-hosting changes:

• credential custody;
• server responsibility;
• uptime responsibility;
• network configuration;
• backup procedures;
• local security.

The correct editorial rule is:

Cloud MCP permissions and self-hosted TradeServer permissions are separate current-state questions.

---

AI assistants are support and building tools, not investment advisers

Current product-classification materials describe built-in AI personas or assistants used for activities such as:

• technical support;
• code generation;
• debugging;
• platform assistance.

An AI-generated HaasScript can compile and still be a poor trading strategy.

The user remains responsible for:

• strategy logic;
• position sizing;
• exchange choice;
• leverage;
• backtest interpretation;
• live deployment;
• monitoring.

---

API permissions should exclude withdrawals

Current getting-started and exchange-connection guidance tells users to configure permissions needed for reading and trading without granting withdrawal access.

Current Kraken instructions, for example, allow order-management functions while keeping withdrawals disabled.

That is a meaningful security control.

It does not protect against loss from authorized trading.

---

The exchange count is a marketing reference, not a universal product matrix

Current pricing page disclosures show:

• Supported exchange count: 24

Why?

Because individual integration pages can change status.

A product page can advertise a broad integration count while a specific exchange integration is temporarily disabled, deprecated, renamed, or technically different.

across all displayed integrations.

---

Backtesting remains a simulation

HaasOnline offers plan-dependent historical backtesting.

The 36-month TradeServer window can expose more market regimes than a one-month test.

It still cannot guarantee live performance.

Potential live differences include:

• data quality;
• exchange fees;
• spread;
• latency;
• partial fills;
• API outage;
• liquidation;
• funding;
• position limits;
• order rejection.

Assessment

HaasOnline is one of the more technically capable automation products in the current ROIStreet set.

The main value is depth: scripting, bot management, backtesting, cloud and self-hosted deployment, and AI-assisted development.

The key 2026 AI guard is unusually specific:

Cloud MCP can do substantial analysis and authoring work, but the documented cloud toolset does not expose direct trade placement, cancellation, fund movement, or bot start/stop controls.

That distinction is more useful than labeling the product generically as “AI trading.”