Environments: Configure Dev, Staging, and Production

Environments

SendPromptly environments let you isolate notification traffic by lifecycle stage. This is a core safety control for teams shipping transactional email and webhook flows.

Each environment has its own tokens, configuration, and delivery runs, so test traffic never pollutes production logs or reaches live recipients unintentionally.

  • dev: local development and feature testing
  • stage: pre-production QA and release validation
  • prod: live customer traffic

What is isolated per environment

  • API tokens
  • Template activation state
  • Delivery run history and debugging context
  • Provider and endpoint behavior under test

Promotion workflow

  1. Develop and validate template logic in dev.
  2. Promote or recreate approved versions in stage.
  3. Run release checks with realistic payloads.
  4. Roll out to prod with monitoring enabled.

Operational best practices

  • Use separate secrets per environment and store them in your secret manager.
  • Never run local scripts with production tokens.
  • Add guardrails in CI/CD to prevent accidental prod token use.
  • Keep test recipients and test webhooks environment-scoped.

Incident containment

When issues occur, environment separation reduces blast radius. You can pause or adjust a non-production environment without impacting live customer communication.