generated: '2026-08-13'
method: searched
source: https://hightouch.com/docs/workspace-management/environments, https://hightouch.com/docs/developer-tools/api-guide
note: 'Hightouch publishes no test-vs-live key mode and no magic test values. Its test story is workspace-level:
  each workspace is an environment, and resources are promoted between them.'
test_mode:
  supported: false
  note: There is no sandbox key prefix or `test` flag on the API key. An API key is scoped to one workspace,
    so isolation comes from pointing the key at a non-production workspace.
environments:
  model: workspace-per-environment
  docs: https://hightouch.com/docs/workspace-management/environments
  typical:
  - development
  - staging
  - production
  - sandbox
  capabilities:
  - Each workspace holds its own sources, models, destinations and syncs.
  - Resources can be LINKED across workspaces (e.g. a Salesforce sandbox in dev linked to production Salesforce
    in prod), and models/syncs are DEPLOYED from one workspace to another.
  - 'Deploys are dependency-checked: Hightouch verifies linked counterparts exist before copying.'
  - RBAC, drafts and approval flows are enforced across the deploy boundary.
  hard_isolation: Use a separate workspace (not an environment) when sources, destinations and users must
    not be shared — https://hightouch.com/docs/workspace-management/workspaces
free_tier_for_testing:
  plan: Basic Reverse ETL
  limits: up to 2 active syncs, unlimited destinations and seats
  source: https://hightouch.com/pricing
debugging:
  live_debugger: https://hightouch.com/docs/syncs/debugger
  note: Live Debugger shows the real outbound HTTP requests Hightouch makes to a destination, with payloads
    and response codes — the closest thing to a request inspector.
  warehouse_sync_logs: https://hightouch.com/docs/syncs/warehouse-sync-logs