askmike/gekko

★ 10,171JavaScriptAudience · developerComplexity · 3/5Setup · hard

Mindmap

mindmap
  root((Gekko))
    What it does
      Automate trade strategies
      Backtest on history
      Connect to exchanges
    Status
      Officially archived
      No more updates
      Active forks may exist
    Setup
      Local Node.js app
      User-configured
    Risks
      Unpatched vulnerabilities
      Broken exchange APIs
      Financial risk

mindmap root((Gekko)) What it does Automate trade strategies Backtest on history Connect to exchanges Status Officially archived No more updates Active forks may exist Setup Local Node.js app User-configured Risks Unpatched vulnerabilities Broken exchange APIs Financial risk

Click or tap to explore — scroll the page freely

Things people build with this

USE CASE 1

Study the source code as a learning reference for how a cryptocurrency trading bot and backtesting engine can be architected in Node.js.

USE CASE 2

Backtest a simple technical analysis strategy against historical Bitcoin price data to understand how the platform was designed.

Tech stack

JavaScriptNode.js

Getting it running

Difficulty · hard Time to first run · 1day+

Unmaintained, exchange API compatibility is likely broken and security vulnerabilities will not be patched.

In plain English

Gekko was a Bitcoin trading and backtesting platform written in JavaScript for Node.js. It connected to popular Bitcoin exchanges and allowed users to automate trading based on technical analysis strategies, as well as test those strategies against historical price data before running them with real money. The project is no longer maintained. The original author officially archived it and posted a farewell announcement explaining their reasons. The repository still exists and can be read, but no updates, bug fixes, or security patches will be coming from this author. There may be active forks made by other developers, but those are separate projects. When it was active, Gekko provided a platform for writing and running trading strategies that reacted to price movements on cryptocurrency exchanges. Backtesting let users replay historical market data through a strategy to see how it would have performed, without risking actual funds. The platform had a documentation site, a community forum, and a Discord server for users. Gekko ran as a local Node.js application, meaning users installed and ran it on their own computer rather than accessing it through a web service. Configuration and strategy code were handled by the user directly. Because this project is unmaintained and involves connecting to financial exchanges, anyone considering using it should be aware that security vulnerabilities may exist that will not be patched, and compatibility with current exchange APIs is unlikely to be maintained. The author included a risk warning even during active development.

Copy-paste prompts

Prompt 1

I'm studying the Gekko source code to learn how backtesting engines work. Explain how a custom strategy would receive price data and emit buy or sell signals.

Prompt 2

Based on the Gekko architecture, how should I structure a new Node.js trading bot that keeps strategy logic cleanly separated from exchange API calls?

Prompt 3

What security risks do I need to handle when a trading bot holds API keys for a live cryptocurrency exchange, and how should I store those keys safely?

Prompt 4

What are the main reasons a project like Gekko becomes unmaintained, and what should I check before forking an archived trading bot for my own use?

Open on GitHub → Explain another repo

← askmike on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.