RESOURCES

Docs, routes, and local workflows for the Lunatrix stack.

Start locally. Integrate cleanly. Extend carefully.

The resources layer should make the product usable, not ornamental. Everything needed to run the frontend, backend, and model services locally should be easy to scan and easy to follow.

Open API docs Open schema

/docs

Interactive API docs

Inspect the backend gateway routes that are exposed to the frontend and downstream consumers.

/redoc

Reference documentation

Use the Redoc view when you want the contract laid out like a product reference instead of a tester.

/openapi.json

OpenAPI schema

Pull the raw schema directly when you need to generate clients or inspect the gateway surface programmatically.

Local startup

Run the services separately.

Each Lunatrix layer is designed to start on its own port and talk to the others over localhost.

# model
cd model-service
python scripts/runAiEngine.py

# backend
cd backend-ts
npm run dev

# frontend
cd frontend
npm run dev

Frontend

The standalone frontend serves the Lunatrix pages and proxies API traffic through the backend gateway.

Backend

The NestJS layer stays on `127.0.0.1:8000` and forwards model-facing work to the Python service.

Model

The model service continues to own live inference, trained artifacts, and published signal outputs.