I deployed tazama-stack with the demo frontend (AUTHENTICATED=false), but the admin-service keeps crash-looping or config/network-map calls fail...

There is a known bug in the admin-service environment file (tazama-stack/core/env/admin.env) that causes the admin-service to crash-loop when the Simulation Database environment variable block is present - this shows up particularly when deploying with Authentication disabled (Core Addon 1 unchecked) alongside Relay services (NATS), pgAdmin, and Hasura GraphQL enabled. Workaround: remove the Simulation Database environment variable block from admin.env before re-running the deployment script. The fix has since been regressed into the dev branch, so pulling the latest dev source should let you deploy without the manual edit. Separately, with Authentication disabled, some unauthenticated API calls (e.g., the demo frontend fetching the network map) may still return an “unauthenticated” error even though authenticated Postman calls succeed - this related issue was still being investigated as of July 22, 2026. Source: Tazama Head of Product, #get-help, July 2026.