
Set up a Linux server and Docker application
We set up a new Linux server for an existing Docker application, connecting the domain, HTTPS and a documented deployment process.
VAT-exempt under section 19 of the German VAT Act



We configure operating signals for one Linux host and up to three services, then test whether an agreed alert reaches the responsible person.
Non-binding enquiry
Useful monitoring connects technical signals with someone who can interpret them. We configure the agreed measurements and availability checks, define alert rules with you and test the path from a controlled event through to email in the right inbox.

The application already runs, but your team wants a documented monitoring setup showing its health and availability. It also matters that messages reach the right person.
We review the host and up to three services and discuss which states should trigger a message. This forms the basis for configuring measurements, checks and the existing email channel.
A controlled event checks the path from signal through to delivery. We document the triggered rule and the associated first checks so your team can follow the process later.
Do not send passwords or tokens.
Compare your own assumptions with the costs of analysis and implementation.
Calculate your own scenarioWhat is included, what do you need and what happens after your enquiry?
The process in detailThe package sets up the agreed signals and alerts and tests delivery. Who checks messages day to day, and what support we provide, is agreed as a separate ongoing task.
The scope includes up to three agreed HTTP endpoints or container services on the one host. We establish beforehand which signal meaningfully describes the intended state and is technically accessible.
We agree up to five rules based on the setup and how it is used. Brief high utilisation may be normal, so we also establish how long a condition must persist before a message is triggered.
The package sets up the agreed signals and alerts and tests delivery. Who checks messages day to day, and what support we provide, is agreed as a separate ongoing task.
The scope includes up to three agreed HTTP endpoints or container services on the one host. We establish beforehand which signal meaningfully describes the intended state and is technically accessible.
After reviewing the setup, we agree the start, access and implementation window with you. The schedule is confirmed alongside the scope before work is commissioned.
Credentials must not be included in the enquiry. Details are agreed only after written commissioning.
One written follow-up round is included. The service scope lists the analyses, designs or technical changes covered by the package. We agree additional work with you before it begins.