Proposal: Modern graphical WebUI for ADAMANT TradeBot (private self-host + public subscription)

[metalisk]

Context

The current WebUI experience is largely text-based (messenger-style command replies). We want a modern graphical interface: charts, order book, balances, open orders, trade-parameter forms, and module-aware control panels.

Rule: the WebUI never connects to exchanges. All data flows from the bot API.

Two deployment models

A) Private self-hosted WebUI (one-time purchase)

• Operator runs WebUI behind HTTPS (reverse proxy)
• WebUI maintains a fleet registry of bots (http://host:port per bot)
• Shared private_webui_secret_key; WebUI signs JWT after operator login (local users + 2FA on WebUI side)
• WebUI server calls each bot directHttp (/api/v1/*)
• One WebUI address → many bots in tabs

B) Public subscription WebUI

• User authenticates via external payment/auth service
• User puts a license token in bot config; bot connects outbound to a public relay (no inbound bot port)
• Browser → public WebUI → relay → bot (API tunneled 1:1)
• License scope: one exchange + one pair per license

MVP scope (scenario A first)

• Vite + React 18, new stack (no legacy WebUI)
• Transport abstraction: DirectHttpTransport then RelayWsTransport
• Bootstrap via GET /bot (capabilities drive visible UI blocks)
• Params via WS params:updated + REST
• Market/account via REST polling (~10s initially); push from bot cache later
• Legacy WebUI not supported

Non-goals (this thread)

• Payment/billing implementation details
• Bot API design (see companion discussion on Bot API)

A tracking issue will be opened in adamant-tradebot-webui referencing this discussion.

[adamantmm]

This is a really strong and important feature for MarketMaking.app.

A modern graphical WebUI can make market-making much more accessible and practical for real projects. Today, many bot operations are still understandable mostly to technical users: command replies, logs, text tables, and manual configuration checks. A proper UI with charts, order book view, balances, open orders, module-aware controls, and clear trade-parameter forms would make it much easier to monitor liquidity, understand bot behavior, adjust strategy, and explain the setup to project teams.

For token projects, this can become a major advantage. Market making is not only about running a bot — it is also about visibility, confidence, and control. A graphical WebUI can help teams see what is happening with their market in real time, react faster, avoid misconfiguration, and better understand how liquidity support affects the chart and order book.

I also think it is very important to make this available not only for the private self-hosted paid version, but also for users of the free bot version https://github.com/Adamant-im/adamant-tradebot — at least through a public subscription model. This would lower the entry barrier for smaller projects and communities that cannot immediately buy a full private WebUI, but still need a professional interface for market-making operations.

A free trial would also be very useful. Many teams need to see the product in action before they understand its value. Letting projects try the WebUI for a limited time could make adoption much easier and help convert interested users into long-term subscribers.

Overall, this feature can significantly improve the usability and commercial value of ADAMANT TradeBot / MarketMaking.app.

[adamantmm]

Issue to track: Adamant-im/adamant-tradebot-webui#1