Environments & deployment
Maddict runs in three environments that differ only by configuration — the same code runs in all of them. This page explains what each is for so you know which URL you’re using and what to expect.
The three environments
Section titled “The three environments”| Environment | Purpose | Who uses it |
|---|---|---|
| Local | Development on an engineer’s machine. | Maddict engineers |
| Staging | Internal testing before release. | Maddict team & invited testers |
| Production | The live product. | Agencies (customers) |
If you’re an agency, you use production — your team’s real, live workspace.
Same code everywhere
Section titled “Same code everywhere”Each environment is the identical application, configured differently (different URLs, keys, and data). This “same code, different config” approach means what’s tested in staging behaves the same way in production.
Stability expectations
Section titled “Stability expectations”| Environment | Stability | Data |
|---|---|---|
| Production | Stable, monitored, the source of truth. | Your real audiences and team. |
| Staging | May change frequently; for testing. | Test data; not for real work. |
| Local | Engineering only. | Throwaway. |
Releases
Section titled “Releases”New features and fixes flow local → staging → production. Changes are validated in staging before reaching the live product, so production stays stable. What’s shipped is summarised in the release notes.
Operational notes
Section titled “Operational notes”- Production is monitored for errors and performance.
- Routine, scheduled background jobs keep the catalogue warm and handle renewals so the product stays responsive and access stays current.
- Planned maintenance, if any, is communicated ahead of time.
Architecture overviewWhat runs in each environment.
Release notesWhat's shipped to production.