AI Workflow Platform for Tecnical LLM Trading
TradingGoose Studio is an AI workflow platform for technical LLM trading, it combines both technical + LLM analysis for your trading decision. It is built for analytics, research, charting, monitoring, and workflow automation.
Early Stage Notice
TradingGoose Studio is still in a very early development stage. You should expect rough edges, incomplete features, and a meaningful number of bugs. Breaking changes are normal at this stage and may happen very frequently, including on a near-weekly basis. If you are building on top of the project, expect to update your setup, workflows, and integrations often.
- Bun v1.3+
- Docker (for PostgreSQL)
- Colima or Docker Desktop (macOS)
bun install
docker run --name tradinggoose-db `
-e POSTGRES_USER=tradinggoose `
-e POSTGRES_PASSWORD=<your-postgres-password> `
-e POSTGRES_DB=tradinggoose `
-p 5432:5432 `
-d pgvector/pgvector:pg17
docker run -d --name tradinggoose-redis -p 6379:6379 redis
cd apps/tradinggoose && cp .env.example .env
cd ../../packages/db && cp .env.example .env
cd packages/db
bunx drizzle-kit migrate --config=./drizzle.config.ts
cd ../..
bun run dev:full
If you use Docker Compose, copy apps/tradinggoose/.env.example.docker to
apps/tradinggoose/.env and set the required secrets before running the
compose manifests. The .env must include POSTGRES_*,
NEXT_PUBLIC_APP_URL, NEXT_PUBLIC_SOCKET_URL, BETTER_AUTH_SECRET,
ENCRYPTION_KEY, API_ENCRYPTION_KEY, and INTERNAL_API_SECRET. The
ENCRYPTION_KEY value is shared by both the app and realtime containers, and
API_ENCRYPTION_KEY enables encrypted API-key storage in the app container.
NEXT_PUBLIC_SOCKET_URL should point at http://localhost:3002 for local
Compose runs; production deployments must override it with a browser-reachable
public URL. The prod and Ollama compose files also require IMAGE_TAG and
OLLAMA_IMAGE_TAG respectively.
docker compose --env-file ./apps/tradinggoose/.env -f docker-compose.local.yml up
Pull requests are welcome.
If you want to improve TradingGoose Studio, fix a bug, tighten the docs, or ship an idea that makes the platform better for traders and builders, open a PR. Small, focused changes are preferred and easier to review.
This project is moving quickly and is expected to have bugs and frequent breaking changes. Contributors should expect the codebase, interfaces, and workflows to change often, sometimes week to week.
- Read the Contributing Guide for setup, workflow, and PR expectations
- Review the Code of Conduct before participating in project spaces
- Open an issue first if you want feedback on larger changes or architecture work
| Tech Stack | |
|---|---|
| Framework |  |
| Runtime |  |
| Database |   |
| Authentication |  |
| UI |   |
| State Management |  |
| Realtime |   |
| Flow Editor |  |
| Docs |  |
| Monorepo |  |
| Background Jobs |  |
| Remote Execution |  |
| Charting |  |
| Indicator Engine |  |
| Drawing Tools |  |
Special thanks to the Sim Studio team for open-sourcing the original project this repository is built on top of.
TradingGoose Studio started from Sim Studio v0.4.25.
The combined TradingGoose Studio project is licensed under AGPL-3.0-only - see the LICENSE file for details. This is not because the Sim Studio upstream is Apache-2.0; those upstream notices remain preserved. The combined project is AGPL-3.0-only because TradingGoose Studio integrates PineTS under its AGPL terms, and this project is intentionally kept as free software so users can use, study, modify, self-host, and redistribute it under the same terms. Additional attributions and third-party license texts are in NOTICE and THIRD-PARTY-LICENSES. The Apache-2.0 text preserved for Sim Studio and Lightweight Charts is in LICENSES/Apache-2.0.txt. Those Apache-related notices still stay in the repository because this project is derived from Apache-licensed upstream code and also distributes Apache-licensed third-party components whose attribution notices must be preserved.
The chart drawing tools vendored in apps/tradinggoose/widgets/widgets/data_chart/plugins/
carry their own MPL-2.0 license file at
apps/tradinggoose/widgets/widgets/data_chart/plugins/LICENSE.
Those vendored modified source files remain covered by the MPL-2.0 at the file level.
The project's overall AGPL-3.0-only distribution does not replace or remove the MPL-2.0
terms that continue to apply to that directory.
HONK !