Skip to content

Add AlgoDeploy to Trading & Backtesting - #536

Open
joeschatzman wants to merge 3 commits into
wilsonfreitas:mainfrom
joeschatzman:add-algodeploy
Open

Add AlgoDeploy to Trading & Backtesting#536
joeschatzman wants to merge 3 commits into
wilsonfreitas:mainfrom
joeschatzman:add-algodeploy

Conversation

@joeschatzman

Copy link
Copy Markdown

Adds AlgoDeploy — a self-hosted Python framework to backtest, risk-manage, and go live on your own Alpaca or Interactive Brokers account (US equities, single-leg options, crypto). Build strategies in a no-code UI, YAML, or Python. Commercial, one-time license.

Happy to move it to "Commercial & Proprietary Services" instead if you'd prefer that section.

joeschatzman and others added 2 commits August 2, 2026 19:36

Copy link
Copy Markdown
Owner

Thanks for the contribution. AlgoDeploy is a proprietary hosted/commercial product, so the entry should move from Trading & Backtesting to Commercial & Proprietary Services. Please describe its access terms precisely: the permanent free tier is restricted to users with a valid .edu email and has strategy limits, while broader access is paid or trial-based. Include the applicable limits and payment requirements in concise, factual wording with a stable pricing or documentation link.

…ess terms

Per maintainer review: recategorized from Trading & Backtesting, and
described the .edu free tier limits, one-time license pricing, and 7-day
trial with a stable pricing link.
@joeschatzman

Copy link
Copy Markdown
Author

Thanks Wilson — done. Moved AlgoDeploy to Commercial & Proprietary Services and spelled out the access terms: the permanent free tier requires a valid .edu email and is limited to 3 strategies / backtesting only, while live trading and advanced features are paid via a one-time license (with a 7-day trial), linked to a stable pricing page. Happy to trim further if you'd prefer it shorter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants