Developers

Developer guide & SDK

Accessible Trade Terminal is open source and built to be extended. If you write code, you can add to it — and share what you build with everyone else.

What you can build

  • Data providers

    Connect a new exchange, broker, or market-data source so it shows up alongside the built-in ones.

  • Indicators

    Add your own indicators — with full control over how they look, sound, and read aloud.

  • Analytics sources

    Plug in macro, on-chain, sentiment, or fundamental data for the analytics side of the terminal.

How it works

The platform is a .NET 10 project, and the extension points live in a dedicated SDK. A plug-in is a small .NET class library that implements the SDK's interfaces, compiles to a DLL, and is loaded by the app at startup. Built-in providers and indicators are written the same way — so the existing ones double as working examples to copy from.

Indicators have a second, lighter path too: you can write one in C# from inside the app, compile it on the spot, and share it as a single file — no full project required. Either way, your indicator can declare its own colors, tones, and spoken descriptions so it fits the accessibility model the rest of the platform uses.

For safety, the app verifies plug-ins before loading them and runs your custom code in a sandbox, isolated from the rest of the system.

Getting started

  1. Get the code

    Clone the repository on GitHub (opens in new tab) and open the solution in your editor of choice.

  2. Read the authoring docs

    Start with the SDK & Plugin Guide — the full extension model end to end, with worked examples. For exhaustive field-by-field detail, the repository's docs folder adds PLUGIN_AUTHORING.md (indicators) and PROVIDER_AUTHORING.md (data providers).

  3. Copy a working example

    Start from one of the existing providers or indicators in the Plugins folder. They use the same SDK you will, so they're the fastest way to learn the shape of things.

  4. Build, test, and share

    Drop your compiled plug-in into the app to try it, then publish it so others can use it too.

Other ways to contribute

You don't have to write code to help. Bug reports and feature requests genuinely shape the roadmap — open an issue on GitHub (opens in new tab), or send a note through the contact form. Testing with your own setup and telling us what works (and what doesn't) is just as valuable as a pull request.