Private alpha online/Cloud since June 2026

Algorithmsin orbit.

The operating system between a strategy idea and live capital. Test, gate and execute across seven perpetual venues—without handing over withdrawal access.

07perpetual venues
01free live instance
00withdrawal permissions
2.0Apache SDK licence
Scroll to travel
01Control loop

Every order passesfour gates.

Charts suggest. Infrastructure decides. Lyrithm keeps the path from connection to reconciliation explicit and observable.

01

Connect

Connect + Vault

Encrypt trade-only venue keys. Withdrawal access never enters the system.

02

Prove

Sandbox

Replay real candles and paper-trade away from the live engine.

03

Gate

Core

Evaluate loss, position and cooldown limits before every order.

04

Execute

Ledger + Pulse

Route, reconcile and raise an alert the operator can act on.

02Runtime constellation

One core.Eight responsibilities.

The centre is deliberately small. Inputs, execution and operations remain separate so a failure is visible before it becomes a mystery.

CoreStrategy runtime

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.

ConsoleOperational command surface

Accounts, running strategy instances, fills, and risk overrides on one screen.

ConnectExchange adapters

One normalised order, position, and candle contract across seven perpetual venues — centralised books and on-chain perps alike.

VaultCredential protection

Exchange keys encrypted at rest under a master key and scoped to trading only. Withdrawal permission is never requested.

SandboxBacktest and paper trade

A separate service from the live engine. Replay real candles, compare runs, and promote a strategy only when the behaviour earns it.

PulseAlerts you can act on

Telegram alerts for fills, errors, and blocked entries, with inline Close, Reload and Retry buttons plus a Mini App console.

LedgerReconciliation watchdog

Continuously compares intended position state against what the exchange actually holds, and raises the gap instead of hiding it.

KitSDK for Stargazers

Apache-2.0 Python SDK and CLI. Write against a typed strategy contract, backtest locally, then package and publish.

BinanceCentralisedBybitCentralisedOKXCentralisedBitgetCentralisedAsterDexOn-chainHyperliquidOn-chaindYdX v4On-chain
03Lyrid trajectories

Strategies witha visible lineage.

Two Lyrids ship today. Reserved stars are honest naming slots—not pretend products. Every live strategy declares its source boundary.

αLive on Cloud

Vega / α Lyrae

Lyrid alpha

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-source
γShipped

Sulafat / γ Lyrae

Lyrid gamma

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-source
β
SheliakSheliak is an eclipsing binary. Fittingly, β is the slot earmarked for pairs trading.
δ
RR LyraeRR Lyrae is the prototype of variable stars. δ is held for volatility strategies.
ε
AladfarThe famous double-double. ε is the slot for hedged, multi-leg execution.
04Stargazer protocol

Your code staysyour code.

Lyrithm 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 0
05Choose your gravity

Managed cloud.Or your machine.

LiveC

Cloud

Sign in and trade. We run the engine, the database, and the upgrades.

  • Browser console, sign in with Google or GitHub
  • Subscription billing with per-tier instance and template caps
  • Lyrid α (Vegas + ADX) bundled from the free tier
  • Managed upgrades on blue-green slots — no maintenance window
Start free
v1.0 · checkout opening soonP

Personal

Own your trading bot. Pay once, run it on your own machine or VPS.

  • Four Docker containers on your box — engine, console, worker, Postgres
  • No Clerk, no Stripe, no SaaS account. A signed license.json is the credential
  • Every licence is Ed25519-signed offline; tampering means the bot refuses to start
  • Version-locked — buy v1, run v1. Major bumps unlock a 50%-off renewal
View Personal release
06Access coordinates

Start free.Scale when ready.

Cloud Free is live. Paid Cloud checkout is not open yet. Personal is a one-time licence, with checkout opening soon.

Free

$0forever

Run one strategy for real, with the sandbox to prove it first.

  • 1 running strategy instance
  • Built-in Vegas + ADX (Lyrid α)
  • Backtest and paper trade in Sandbox
  • Lyrithm Vault credentials
  • Telegram Pulse alerts
Start free

Constellation

Custom

For desks that need scale, closed-source hosting, and a direct line.

  • Unlimited running instances
  • Unlimited custom templates
  • Closed-source strategy hosting
  • Direct support channel
  • Early access to new venues
Talk to us

Paid Cloud checkout is not open yet. The Free tier is live now, and nothing built on it is reset when billing opens.

07Signal clarity

No black boxaround the truth.

01Does Lyrithm have access to my funds?

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.

02Do you guarantee returns?

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.

03How finished is this, honestly?

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.

04Which exchanges are supported?

Seven perpetual venues: Binance, Bybit, OKX, Bitget, AsterDex, Hyperliquid and dYdX v4. Spot markets are not supported — the engine trades perpetual futures only.

05Can I write my own strategy?

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.

06What does closed-source mean here?

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.

07Do I need to know Docker?

Only for Personal Edition, which is four containers you run yourself and reach over an SSH tunnel. Cloud Edition needs nothing but a browser.

08Open channel

Put your strategyinto orbit.

Start with one free live instance, or leave a coordinate for Personal, paid Cloud tiers, institutional access or strategy publishing.