Developers
Environments
Dev, staging, and production topology with variable layer reference.
Environments
Three environments with clear promotion gates and isolated data boundaries.
Environment Comparison
| Dimension | Development | Staging | Production |
|---|---|---|---|
| Purpose | Feature development, integration testing | Pre-release validation | Live customer workloads |
| Data | Synthetic / anonymized | Production mirror (subset) | Real customer data |
| Uptime SLA | Best effort | 99.0% | 99.9% |
| Access | Engineering team | QA + Product | End users only |
| Deploy trigger | Push to dev branch |
Merge to main + tag |
Merge to main + approval |
| LLM provider | OpenAI (cheaper models) | Bedrock (prod models) | Bedrock (prod models) |
Promotion Flow
Feature branch ──► dev environment ──► PR review ──► main branch
│
▼
staging environment
│
▼
QA sign-off ──► prod deployment
Variable Layer
Each repo has .env (prod) and .env.dev (dev). Workspace .env contains shared infrastructure variables.
| Variable | Scope | Example |
|---|---|---|
AWS_REGION |
All | ap-south-1 |
MONGODB_URI |
Per-env | mongodb://... |
REDIS_URL |
Per-env | redis://... |
LLM_PROVIDER |
Per-env | bedrock / openai |