Build Your Own Trading GUI with the Nanoconda Remote API
One of the most common requests we've received from customers is simple:
"Can I build my own GUI?"
Until now, the answer was "yes, but..." You could monitor your trading session remotely, download trade logs, and perform account management actions such as flattening positions or disabling trading.
With the latest release of the Nanoconda Remote API, the answer is now simply:
Yes.
Your remote application can now communicate directly with your colocated trading program, allowing you to build completely custom trading interfaces, dashboards, automation systems, and operational tools without modifying the trading infrastructure itself.
Your Program, Your Interface
Every trading firm has different workflows.
Some want a minimalist control panel. Others want a large dashboard with charts, statistics, risk metrics, strategy controls, or integrations with internal systems.
Instead of forcing everyone to use the same interface, Nanoconda now lets your application define its own.
Your remote application can:
- Build a completely custom or white-labeled trading GUI
- Display proprietary visualizations and dashboards
- Remotely control trading strategies
- Integrate with internal monitoring systems
- Schedule operational commands
- Exchange arbitrary binary messages with colocated algorithms
The trading engine continues running inside the colocation facility while your interface can run anywhere—in your office, at home, or on another server.
Two Communication Models
The new API supports two complementary communication patterns.
Persistent Display API
Your trading program can continuously publish structured or customer-defined reports.
These reports are retained by the DMA session and automatically distributed to connected Remote API clients approximately once per second.
This is ideal for information that should always be visible, including:
- Strategy status
- P&L
- Positions
- Risk metrics
- Parameters
- Health monitoring
- Custom dashboard data
Instead of repeatedly polling for information, your dashboard simply receives the latest published state.
Request / Response API
Sometimes a dashboard needs to do more than display information—it needs to interact with the trading program.
The Request / Response API allows a remote application to send arbitrary binary commands to the colocated program and optionally receive an immediate response.
Typical examples include:
- Start or stop strategies
- Change algorithm parameters
- Query current state
- Execute custom actions
- Trigger operational workflows
- Implement proprietary communication protocols
Because the payload format is completely customer-defined, you are free to design your own protocol without any restrictions imposed by Nanoconda.
Dynamic User Interfaces
One particularly powerful feature is automatic interface discovery.
The Remote API can deliver the complete Nanoconda Algo API schema describing:
- Views
- Controls
- Tables
- Inputs
A remote application can use this information to dynamically construct a user interface without hardcoding layouts or control definitions.
Alternatively, you can ignore the schema entirely and build a completely proprietary interface tailored to your workflow.
White-Labeled Solutions
Many firms want to build their own branded applications.
The new Remote API makes this straightforward.
Create your own desktop application, add your own branding, design your own workflow, and communicate directly with your colocated trading program.
The underlying execution infrastructure remains Nanoconda, while the user experience becomes entirely yours.
Beyond Trading
The Remote API is not limited to graphical interfaces.
Customers can also build:
- Monitoring services
- Automated operational tools
- Reporting systems
- Risk management applications
- Scheduled maintenance utilities
- Integration with existing infrastructure
Any application capable of speaking the Remote API can communicate with the trading program.
Why We Built It
Our goal has always been to separate the performance-critical components from everything else.
Latency-sensitive code belongs inside the colocation facility.
User interfaces, dashboards, reporting systems, and operational tooling do not.
By exposing a flexible communication layer between the two, firms can innovate rapidly without affecting the trading engine itself.
Whether you're building a lightweight control panel, a sophisticated operations dashboard, or an entirely white-labeled trading platform, the new Remote API gives you complete control over the user experience while keeping the execution engine exactly where it belongs.
Get Started
The Remote Algorithm Communication API is available today as part of the Nanoconda Remote Access API.
Whether you're building a lightweight monitoring dashboard, a fully branded trading platform, or integrating your strategies into an existing OMS or internal tool, the API gives you complete control over how your remote applications communicate with colocated trading programs.
The documentation includes the communication model, callback reference, request/response APIs, persistent reporting, and complete C++ interface reference.
Read the documentation: Remote Algorithm Communication Documentation
We look forward to seeing what our customers build with it.