Connect
Connect + VaultEncrypt trade-only venue keys. Withdrawal access never enters the system.
The operating system between a strategy idea and live capital. Test, gate and execute across seven perpetual venues—without handing over withdrawal access.
Charts suggest. Infrastructure decides. Lyrithm keeps the path from connection to reconciliation explicit and observable.
Encrypt trade-only venue keys. Withdrawal access never enters the system.
Replay real candles and paper-trade away from the live engine.
Evaluate loss, position and cooldown limits before every order.
Route, reconcile and raise an alert the operator can act on.
The centre is deliberately small. Inputs, execution and operations remain separate so a failure is visible before it becomes a mystery.
The live trading engine. Tenant-scoped execution, risk gates evaluated before an order leaves, and blue-green deploy slots so a release never lands mid-position.
Accounts, running strategy instances, fills, and risk overrides on one screen.
One normalised order, position, and candle contract across seven perpetual venues — centralised books and on-chain perps alike.
Exchange keys encrypted at rest under a master key and scoped to trading only. Withdrawal permission is never requested.
A separate service from the live engine. Replay real candles, compare runs, and promote a strategy only when the behaviour earns it.
Telegram alerts for fills, errors, and blocked entries, with inline Close, Reload and Retry buttons plus a Mini App console.
Continuously compares intended position state against what the exchange actually holds, and raises the gap instead of hiding it.
Apache-2.0 Python SDK and CLI. Write against a typed strategy contract, backtest locally, then package and publish.
Two Lyrids ship today. Reserved stars are honest naming slots—not pretend products. Every live strategy declares its source boundary.
Vega / α Lyrae
Vegas + ADX, the flagship lineage. Runs live today on the founder's own accounts. Bundled with Cloud from the free tier; on Personal it stays invite-only.
Closed-sourceSulafat / γ Lyrae
Bollinger mean-reversion, long only. Buys the lower band when RSI is oversold and the regime is range-bound. Read it, fork it, change the periods.
Open-sourceLyrithm Kit is the Apache-2.0 Python SDK and CLI. Build against a typed strategy contract, test locally, and declare what the runtime may expose.
Strategies you author keep the licence you choose. Java and Pine are planned, not shipped.
# Lyrid γ (Sulafat) — Bollinger mean-reversion
from lyrithm_sdk import Strategy, Candle
from lyrithm_sdk.indicators import (
BollingerBands,
RSI,
)
class SulafatBbMr(Strategy):
def __init__(self, config):
self.bb = BollingerBands(
config["bb_length"],
config["bb_stdev"],
)
self.rsi = RSI(config["rsi_period"])
def update(self, candle: Candle) -> None:
self.bb.update(candle.close)
self.rsi.update(candle.close)
def check_long_entry(self) -> int:
oversold = self.rsi.get_value() < 30.0
at_band = self.bb.at_lower_band()
return 1 if oversold and at_band else 0Sign in and trade. We run the engine, the database, and the upgrades.
Own your trading bot. Pay once, run it on your own machine or VPS.
Cloud Free is live. Paid Cloud checkout is not open yet. Personal is a one-time licence, with checkout opening soon.
Run one strategy for real, with the sandbox to prove it first.
For Lyrithmers running several instances and uploading their own code.
For desks that need scale, closed-source hosting, and a direct line.
Paid Cloud checkout is not open yet. The Free tier is live now, and nothing built on it is reset when billing opens.
No. Lyrithm never requests withdrawal permission. Funds stay in your exchange account while the engine trades through scoped, trade-only API keys, encrypted at rest in Lyrithm Vault. On Personal Edition the keys never leave your own machine.
No. Algorithmic trading involves substantial risk, including total loss of capital. Lyrithm provides infrastructure and workflow controls — not financial advice, and not a performance promise.
Cloud Edition has been live since June 2026 and is in private alpha. Sign-in, accounts, the engine, sandbox and Telegram alerts work end to end. Subscription billing, public strategy upload and the Observatory marketplace are built but still feature-gated. Personal Edition images ship publicly, but checkout is not open yet.
Seven perpetual venues: Binance, Bybit, OKX, Bitget, AsterDex, Hyperliquid and dYdX v4. Spot markets are not supported — the engine trades perpetual futures only.
Yes. Stargazers build against Lyrithm Kit, the Apache-2.0 Python SDK: a typed Strategy class, a lyrithm.yaml manifest, and a config_schema.json for the tunables. Test it with the lyrithm CLI or in Sandbox, then declare source_visibility as open or closed. Java and Pine are planned, not shipped.
A closed-source Lyrid exposes configuration and runtime behaviour without exposing the algorithm source. You can run it, tune it and monitor every fill — you just cannot read or fork the internals.
Only for Personal Edition, which is four containers you run yourself and reach over an SSH tunnel. Cloud Edition needs nothing but a browser.
Start with one free live instance, or leave a coordinate for Personal, paid Cloud tiers, institutional access or strategy publishing.