Two paths
Why build here
Build for others
Build it once and every firm running Open Meridian can run it: the same roles and the same data model, whoever installs it.
Brokers too: your own connector, FIX or your own API, instead of waiting on each OEMS vendor's integration schedule. Statements and positions connect today; order routing arrives with the order path.
Build for yourself
Keep your edge and get there first. What you build is your code and your IP, running in your own environment from your deployment's own registry, so nothing leaves your hands.
Change it the moment your desk needs to, live with your agent, with no vendor queue or release cycle in the way.
Build and ship
How it works
- 1
The plugin kit
The Python SDK, a template to start from with
meridian plugin new, andmeridian plugin checkto hold your plugin to the framework's rules. - 2
Live development
Run it live on a development deployment while you write it, with
meridian plugin dev. - 3
Its own documentation
Your plugin's documentation shipped inside it, for every firm that installs it. Planned, not built yet.
- 4
Distribution
Your customers install it from their own registry today; the community and verified registries open later.
Shape what comes next
Missing something? Ask in the open, not a vendor's queue.
Request it on GitHub, where every request gets an answer, or book a call; whatever we build goes into the open platform, so share only what you're happy to see public.