generated: '2026-08-15'
method: searched
source: >-
  https://tuva-health.github.io/tuva_empi/docs/getting-started/local-demo-environment +
  https://github.com/tuva-health/demo +
  https://github.com/tuva-health/cms_synthetic_connector
note: >-
  Tuva publishes no hosted sandbox (there is no Tuva-operated API to sandbox).
  What it does publish - and what fills the same role - is a runnable LOCAL demo
  for each product line: a Docker Compose stack for Tuva EMPI with published demo
  credentials, and a synthetic-claims dbt project for the Tuva Project. Every
  value below is copied verbatim from the provider's own documentation; none was
  invented, and none is a live credential.
environments:
  - id: tuva-empi-local-demo
    product: Tuva EMPI
    type: local-docker-compose
    docs: https://tuva-health.github.io/tuva_empi/docs/getting-started/local-demo-environment
    setup:
      - git clone git@github.com:tuva-health/tuva_empi.git
      - cp .env.example .env
      - cp backend/config/local.json.example backend/config/local.json
      - docker compose up -d
    url: http://localhost:9000
    credentials:
      username: user
      password: test1234
      note: >-
        Published demo credentials for the bundled Keycloak realm, verbatim from
        the getting-started docs. Local-only; not a Tuva-hosted account.
    identity_provider:
      backend: keycloak
      realm: test-realm
      client_id: test-client
      note: The example config ships a throwaway local Keycloak realm.
    api_base: http://localhost:8000/api/v1
    frontend_port: 3000
    ports_note: >-
      Backend API listens on 8000, frontend NextJS on 3000; the demo stack
      fronts them on 9000 through oauth2-proxy.
  - id: tuva-project-demo
    product: The Tuva Project (dbt package)
    type: local-dbt-project
    repo: https://github.com/tuva-health/demo
    dataset: 1,000-patient synthetic claims and clinical dataset
    setup:
      - clone https://github.com/tuva-health/demo
      - set the dbt profile in dbt_project.yml
      - dbt deps
      - dbt build
    warehouses: [BigQuery, Databricks, DuckDB, Redshift, Snowflake, Microsoft Fabric]
  - id: integration-tests-synthetic
    product: The Tuva Project (dbt package)
    type: in-repo-synthetic-fixtures
    repo: https://github.com/tuva-health/tuva-core
    variables:
      use_synthetic_data: true
      synthetic_data_size: small
    source: https://github.com/tuva-health/tuva-core/blob/main/AGENTS.md
    note: >-
      The provider's own AGENTS.md instructs contributors to validate against
      the shipped synthetic data on local DuckDB using these dbt vars.
  - id: cms-synthetic-connector
    product: Tuva Connectors
    type: public-synthetic-source
    repo: https://github.com/tuva-health/cms_synthetic_connector
    note: Maps the CMS synthetic (DE-SynPUF lineage) dataset into the Tuva Input Layer for dev and testing.
test_mode_separation:
  key_prefixes: []
  note: >-
    There is no test-vs-live key model - authentication is the customer's own
    identity provider, and the "test" environment is a separate local deployment
    rather than a mode flag.