contact
Two reasons people write
If a system has to stay up: the most useful first message describes what it does, what it runs on, and the failure you're worried about. If you are doing diligence: name the claim you want tested and I will point at the artefact behind it — or say plainly that it is not there. If there's an outage right now, say so in the first line; the mail link is read before the form.
Send a message
- email accounts@codalume.com
- security reports accounts@codalume.com — subject [security]
- response usually within a few working days
- timezone UTC±0 — Europe
A short list beats a long brief:
- What the system does, and who depends on it.
- What it runs on today — cloud, bare metal, or a machine under a desk.
- The failure you're worried about, or the one that already happened.
- Any hard constraint: budget, compliance, a deadline, a vendor you're stuck with.
For an active outage, open your message with OUTAGE — it sorts to the top of the inbox.
If the form endpoint is unavailable — or your browser blocks it — the mail link above always works. Nothing you type is lost: the form builds the same message into a mailto: link when a submission fails.