https://github.com/sidmohan0/alphadb
Cryptocurrency data infrastructure with real-time WebSocket feeds, automated feature engineering, and Grafana dashboards. Built with TimescaleDB + Rust. Deploy w/ Docker Compose.
https://github.com/sidmohan0/alphadb
algorithmic-trading backtesting cryptocurrency data-pipeline docker-compose feature-engineering grafana grafana-dashboard kraken-exchange-api market-data postgresql python rust time-series timescaledb websocket
Last synced: 2 months ago
JSON representation
Cryptocurrency data infrastructure with real-time WebSocket feeds, automated feature engineering, and Grafana dashboards. Built with TimescaleDB + Rust. Deploy w/ Docker Compose.
- Host: GitHub
- URL: https://github.com/sidmohan0/alphadb
- Owner: sidmohan0
- License: mit
- Created: 2023-12-15T00:42:53.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2025-06-13T23:56:28.000Z (about 1 year ago)
- Last Synced: 2025-07-08T23:05:05.907Z (12 months ago)
- Topics: algorithmic-trading, backtesting, cryptocurrency, data-pipeline, docker-compose, feature-engineering, grafana, grafana-dashboard, kraken-exchange-api, market-data, postgresql, python, rust, time-series, timescaledb, websocket
- Language: Jupyter Notebook
- Homepage:
- Size: 199 KB
- Stars: 0
- Watchers: 1
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
Awesome Lists containing this project
README
# AlphaDB
AlphaDB is a prediction-market platform monorepo for backend services, operator tooling, and fast market clients. It currently contains:
- `apps/api` - the production-oriented backend for market ingestion, discovery runs, persistence, and future shared APIs
- `apps/web` - the browser client for the backend-backed discovery workflows
- `apps/tui` - the terminal-first market workspace for Polymarket and Kalshi with search, split view, saved markets, and ANSI charts
- `packages/market-core` - shared provider-neutral market contracts used by the API and TUI
- `packages/sdk` - shared backend client SDK for market reads, user state, and streaming
The repository now combines the legacy Polymarket discovery system and the newer multi-provider market workspace in one codebase, so the TUI and future clients can progressively move onto shared backend APIs without a rewrite.
## Platform Direction
The target shape is:
- one monorepo
- one canonical market model
- one backend service layer for search, trending, history, realtime delivery, and user state
- explicit backend identity for persistent user features
- multiple clients, starting with web and TUI
- shared workspace packages for contracts and client access
Architecture notes and accepted decisions live in:
- `docs/README.md`
- `docs/adrs/README.md`
- `docs/checklists/001-backend-convergence-decision-checklist.md`
- `docs/plans/002-phase-1-backend-convergence.md`
- `docs/plans/003-phase-2-productionization-baseline.md`
- `docs/plans/004-fly-deployment-plan.md`
## Workspace Layout
```text
apps/
api/ Express + TypeScript backend
web/ React + Vite web client
tui/ ANSI terminal client
packages/
market-core/ shared market contracts
sdk/ shared backend client
docs/
adrs/
checklists/
plans/
polymarket/
```
## Local Setup
### 1. Install
```bash
git clone https://github.com/sidmohan0/alphadb.git
cd alphadb
npm install
```
### 2. Start local infra for backend work
The backend discovery stack uses Postgres and Redis:
```bash
docker compose -f docker-compose.discovery-stack.yml up -d
```
Expected ports:
- Postgres: `localhost:5432`
- Redis: `localhost:6379`
- API: `http://localhost:4000`
- Web: `http://localhost:5173`
### 3. Configure environment
```bash
cp .env.example .env
set -a
. ./.env
set +a
```
For ad hoc local sessions, the backend mainly needs:
```bash
export DATABASE_URL="postgres://postgres:postgres@localhost:5432/alphadb"
export REDIS_URL="redis://localhost:6379"
export ALPHADB_API_USER_STATE_BACKEND="postgres"
export DISCOVERY_REQUIRE_SCHEMA=1
```
### 4. Apply backend schema
```bash
npm run markets:ensure-state-schema
npm run polymarket:discovery-migrate
```
This applies:
- `apps/api/src/markets/infra/db/userStateSchema.sql`
- `apps/api/src/polymarket/infra/db/schemas.sql`
## Development
Run the backend and web app together:
```bash
npm run dev
```
Run the TUI separately:
```bash
npm run dev:tui
```
Run the TUI against the backend API:
```bash
ALPHADB_API_BASE_URL=http://localhost:4000/api npm run dev:tui
```
Useful workspace-scoped commands:
- `npm run build` - build api, web, and tui
- `npm run test` - run backend tests
- `npm run typecheck:tui` - typecheck the TUI only
- `npm run markets:ensure-state-schema` - ensure backend user-state schema
- `npm run markets:seed-state` - seed backend saved/recent state
- `npm run polymarket:market-channels` - run the backend Polymarket CLI
- `npm run polymarket:discovery-schema` - ensure discovery schema version state
- `npm run polymarket:discovery-migrate` - apply discovery schema
- `npm run fly:deploy:api` - deploy the API with `deploy/fly/api.fly.toml`
- `npm run fly:deploy:web` - deploy the web app with `deploy/fly/web.fly.toml`
## Fly Deployment
Fly deployment artifacts are now checked in:
- `apps/api/Dockerfile`
- `apps/web/Dockerfile`
- `deploy/fly/api.fly.toml`
- `deploy/fly/web.fly.toml`
- `deploy/fly/release-api.sh`
The web app reads its production API base URL from `ALPHADB_WEB_API_BASE_URL` at runtime, so you do not need to rebuild the web image just to repoint it at a different API hostname.
Use the runbook in `docs/plans/004-fly-deployment-plan.md` for the full sequence.
## Current Product Surfaces
### API
`apps/api` owns the durable backend primitives:
- Polymarket discovery runs
- async orchestration and dedupe
- Postgres persistence
- Redis-backed coordination
- normalized market read APIs for trending, search, unified views, and history
- backend user state for saved markets and recents
- backend SSE delivery for live market updates across Polymarket and Kalshi
- migration and maintenance scripts
### Shared Packages
`packages/market-core` and `packages/sdk` define the shared boundary between apps:
- canonical market contracts shared by the API and TUI
- a reusable backend client for market reads, user state, and streaming
- a cleaner path for the web client to adopt the same backend contract next
### Web
`apps/web` is the browser client around the backend discovery workflows. It remains useful as an operational and product shell while AlphaDB expands beyond the original Polymarket-only flow.
### TUI
`apps/tui` is the terminal-native market workspace:
- Polymarket and Kalshi providers
- unified split mode
- fuzzy search
- saved and recent markets
- ANSI candlestick rendering
Today it can run in either direct-provider mode or backend-backed mode. That is intentional during migration; the accepted direction is to move it behind the backend incrementally until the backend is the default source of truth.
When `ALPHADB_API_BASE_URL` is set, the TUI now uses backend-owned market reads, backend-owned saved/recent state, backend live streaming for Polymarket and Kalshi, and can authenticate to backend user-state APIs with `ALPHADB_API_TOKEN`. Direct-provider mode remains available as a local fallback.
## Docs
- `docs/adrs/` - production architecture decisions for backend convergence
- `docs/checklists/` - ordered decision checklist and accepted answers
- `docs/plans/` - implementation plans
- `docs/polymarket/` - legacy Polymarket discovery implementation notes and generated artifacts
## Status
Phase 1 convergence is complete. Current work has moved into the productionization baseline: explicit auth, observability, provider package extraction, and hardening backend-owned user features.