We’re gonna use monorepo+turborepo
Turborepo itself is JS/TS-only tooling — it caches and pipelines builds/tests across npm/yarn/pnpm packages. Your Python AI microservice won't get any benefit from Turborepo's actual machinery (no caching, no task pipeline for it) — it'll just sit in the repo as a folder Turborepo doesn't touch.
So what we’ll do is:
Still use a monorepo folder structure (good idea, keep it), let Turborepo manage just the two JS pieces (frontend + backend) where it actually helps, and let the Python service live alongside as its own independent folder you run separately: ⭐