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.
Recommended setup
dev: local development and feature testingstage: pre-production QA and release validationprod: 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
- Develop and validate template logic in
dev. - Promote or recreate approved versions in
stage. - Run release checks with realistic payloads.
- Roll out to
prodwith 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
prodtoken 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.