Crypto Exchange Gateway

Crypto Exchange Gateway is an archived, self-hosted open-source gateway that streams real-time market data from supported cryptocurrency exchange APIs over…

  • Crypto Currency
  • Development
  • Productivity
Crypto Exchange Gateway is an archived, self-hosted open-source gateway that streams real-time market data from supported cryptocurrency exchange APIs over WebSockets so developers and homelab users can build local dashboards and trading bots.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

31/100 Low

Maintained
0GitHub repository is archived
Popular
56609 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
60no serious findings, 19 minor, tests

Based on 4 of 5 factors.

Availability: platform listings confirmed today, links checked 41 days ago

GitHub stars
609
Open issues
0
Last commit
2023-11-11
Latest release
1.13.2
Activity
stale

Checked 18 days ago - source: GitHub (aloysius-pgast/crypto-exchanges-gateway)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Replace {URL} with exchange API host In API examples, swap {URL} for the actual Crypto.com exchange host you're connecting to. If this placeholder isn't filled correctly, the gateway can't reach the exchange and all calls will fail. source
  • Test connection with a public ticker Before setting up trading keys, call GET /public/get-tickers for an instrument like BTCUSD-PERP. It returns live price data and confirms the gateway can reach the exchange correctly. source
  • Initial configuration Download config.sample.json, save it as config.json, change the bind address from 127.0.0.1 to 0.0.0.0, and add API keys for the supported exchanges. source
  • Source build If building from source, use Node.js 14.x; the README states the project will not build without it. source
  • Source build – Node.js version Building from source requires Node.js 14.x; the project is archived and unlikely to receive further updates. source
  • Sample configuration A sample configuration file is included in the repository at config/config.sample.json; use it as the starting point for the initial setup. source

Fetched 2 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What should I change in the sample configuration for a first self-hosted instance?

Download config.sample.json, save it as config.json, change the bind address from 127.0.0.1 to 0.0.0.0, and add API keys for supported exchanges.

Does it provide a unified REST API for exchange automation?

It provides a unified REST API to various exchanges that can be used to automate trading or build bots.

Does it support real-time data?

Yes, the gateway provides a WS endpoint.

What should I check if the gateway cannot reach an exchange?

Replace {URL} with the actual Crypto.com exchange host, then test the connection with GET /public/get-tickers.

Answers sourced from exchange-docs.crypto.com, hub.docker.com, raw.githubusercontent.com, www.reddit.com

Community

Collected 48 days ago - public community threads