Work with us
Last updated: 1 September 2026
We are a small desk covering cloud platforms and information security. Most of what we publish is written by people who do this work for a living, not by full-time journalists — and that is deliberate.
1. Write for us
We pay for freelance articles. What we want is the thing you actually fixed: the misconfiguration that kept coming back, the migration that went sideways, the detection that finally worked. Specifics beat overviews every time.
What tends to get commissioned
- Field reports. You hardened something at scale and can show the before and after.
- Detection engineering. A query or rule that catches something real, with the false positives you had to tune out.
- Incident post-mortems. Anonymised is fine. What you missed matters more than what you caught.
- Deep platform explainers. A setting nobody understands, explained properly.
- Tool teardowns. Honest, including where the tool falls short.
What we turn down
- Content marketing wearing an article's clothes.
- Roundups assembled from other people's posts.
- Anything reading like a press release, or an AI draft nobody verified.
- Step-by-step exploitation content — we publish defensive framing only. See our Editorial Policy.
Rates and terms
| Standard article (1,200–1,800 words) | [rate] |
|---|---|
| Deep technical piece with lab work | [rate] |
| Payment terms | [e.g. 30 days from publication] |
| Rights | You keep copyright; we take first publication and the right to keep it online |
You get a byline, a short bio and a link. We edit for clarity and house style, and we send edits back before publishing — you will never be surprised by your own article.
How to pitch
Email [[email protected]] with three or four sentences: what happened, why it matters to someone running the same stack, and what the reader will be able to do afterwards. A rough outline helps. Please do not send a finished draft before we have agreed the angle.
We reply to every pitch within [5] working days, including the ones we pass on.
2. Open roles
[List real vacancies here, or say "No open roles right now — send a speculative pitch instead." An empty page with "coming soon" is worse than an honest one.]
3. How we work
- Remote. The desk is distributed; we care when you file, not where from.
- Named bylines. Everything carries the author's name and the date.
- Sources are checked. Every claim needs a vendor advisory, a CVE record, published research, or your own reproduction.
- Corrections are public. If we get it wrong we say so, on the page. See our Corrections Policy.
- Conflicts get disclosed. If you work for, consult to, or hold equity in a company you are writing about, we print that with the article.
4. Sending a tip instead
Not everything needs to be an article. If you have seen something we should be reporting, our contact page explains how to reach us safely. We protect our sources and we will not publish your name or employer without your explicit permission.
Please do not send credentials, customer data, or malware samples by email. Describe what you found and we will arrange a secure channel if we need more.
5. Contact
Pitches and applications: [[email protected]]
Advertising enquiries: Advertise with us
Everything else: contact form