Match the product
We choose hosting after we know the application and who will operate it. Nothing is listed because it looks current.
Services
Deployment, integration, and an operating picture your team can explain.
Match the product
The environment follows the work
Connect the records
APIs and databases that agree
Leave a picture
Deploy, watch, recover
Cloud is useful when someone can see what is running, what it costs, and what happens when it fails. We set the environment to match the product, then leave monitoring you will actually look at. AWS and Azure are options we already name on the site. The choice follows the project.
Who this is for. Teams that have a product to host, systems that should share a record, or a deployment that still depends on one person.
What this can include
We choose hosting after we know the application and who will operate it. Nothing is listed because it looks current.
If two systems should share a status, we make that path explicit. Retyping is treated as a defect, not a habit.
A pipeline, a monitor, and a plain path when something fails. The team should be able to explain what is running.