Why we built it

Working with live markets usually means tiny tutorials that end at a single fetch, or massive frameworks that dictate how you trade. Alpaca API Wrapper sits in the missing middle-a production-grade foundation that you can understand in an afternoon and extend for research, analytics, or algorithmic experiments.

Lower the barrier: plug in a free Alpaca API key, pick up to 30 symbols, and the stack handles streaming, storage, and aggregation.
Stay flexible: iterate on strategies, dashboards, or APIs without fighting rigid abstractions or paid platforms.
Own your data loop: query rich Django models, run Celery tasks, and ship features without reinventing infra.

Developer experience

NX monorepo: unified commands, caching, and task orchestration across frontend and backend.
Hot reload everywhere: Vite for the UI, Django auto reload via Docker volumes, and Flower dashboard for Celery.
Purposeful logging: Docker services surface stdout to your terminal, keeping ingestion and worker activity transparent.
Tooling included: Ruff, Black, Prettier, Pytest, Vitest, and uv ship with sane configs so you can focus on your ideas.

Watchlists & symbol control

Create and manage watchlists without leaving the UI. Store them in Django, sync with Alpaca, and keep everything ready for research or automation.

Real-time candle pipeline

WebSocket ingestion builds 1-minute candles on the fly while Celery resamples into 5m, 15m, 1h, 4h, and daily intervals. Reconnect logic keeps feeds resilient.

Paper trading loop

Experiment with mock orders, visualize P/L instantly, and wire Celery tasks for alerts or strategy execution without touching production capital.

Infrastructure highlights

Docker Compose stack

Backend ASGI app, Celery worker + beat, WebSocket service, Postgres, Redis, nginx-ready configs, and Flower monitoring.

Extendable backend APIs

Prebuilt models for assets, candles, watchlists, and paper trades-ready for new endpoints, scripts, or notebooks.

Ops-ready diagnostics

Health checks warm services in the background, and multitail-friendly logs keep ingestion, workers, and schedulers observable.