Environments
Understand Development and Production environments in Hawcx
Overview
Every Hawcx project runs in one of two environments. Environments isolate your test traffic from real users and control how Config IDs are provisioned.
Development
The default environment for new projects. Use it for building, testing, and staging.
- Config IDs are provisioned instantly, and any Admin or Developer can generate them
- No approval workflow required
- Ideal for local development, CI/CD, and QA
Production
For live, user-facing applications. Production environments have additional safeguards.
- Config IDs require approval before provisioning
- A developer submits a request with the target platform and a reason
- The request is reviewed and approved or rejected
- If rejected, the developer sees the rejection reason and can resubmit
Switching Environments
Use the Environment Switcher in the console top bar to toggle between Development and Production. The switcher applies to dashboard analytics, Config ID lists, and project views.
Enabling Production
Production environments are not available by default. To enable production for your project, contact the Hawcx team or request access through your admin.
Best Practices
| Practice | Why |
|---|---|
| Use Development for all testing | Keeps production metrics clean |
| Use separate Config IDs per platform | Easier to revoke and track usage |
| Rotate Config IDs when team members leave | Prevents unauthorized access |
| Request production Config IDs early | Approval may take time |