InfraPlaybook is a small editorial operation, not a support desk. That shapes what we can answer well and what we cannot — the sections below are ordered by how quickly you will get something useful.
General inquiries
Corrections, questions about something published here, syndication and reprint requests, and speaking or collaboration enquiries all go to the same address:
editorial@infraplaybook.com
Corrections get priority over everything else in the queue. If you can show that a figure, command or licensing claim on this site is wrong, send the evidence and we will fix it in place and note the correction. You do not need to be polite about it.
What we cannot do is act as free technical support for a live incident. We do not have access to your cluster, your tenant or your ticket history, and an answer given without them is worse than no answer. If your pool is full or a migration is failing right now, the article you landed on will serve you better than an email thread will.
Research submissions
The research desk wants three things in particular:
- Benchmark data. Measurements from your own hardware, especially where they contradict ours. Include the host specification, the guest configuration, the commands you ran and the date. A result we cannot reproduce the shape of is a result we cannot publish.
- Pricing and cost inputs. Real seats-per-engineer figures, loaded labour costs and per-seat tool spend, including regional adjustments. These feed the cost model behind our per-seat pricing buildup.
- Field failure modes. The migration or offboarding failure that cost you a weekend and is not yet documented anywhere findable.
Submitted data is handled on these terms unless you agree otherwise in writing: contributions are aggregated and published as medians and ranges with the sample size stated, never as an individual figure attributable to you or your company. We will not name your employer, your clients or your seat count. If a contribution is too distinctive to anonymise, we will come back to you before publishing anything rather than publish it carefully-worded.
Please do not send client-identifying data, credentials, tenant identifiers, log bundles containing user names, or anything under NDA. Strip it before it leaves your side; we would rather have a thinner dataset than hold something we should not.
Response times
The editorial desk aims to respond to every message within 48 business hours. Corrections are triaged ahead of the rest of the queue. Research submissions are acknowledged inside the same window, though the analysis behind them takes considerably longer and we will tell you if a contribution is going into a piece.
Vendor and PR pitches are read, and are answered only where there is a genuine fit. Unsolicited guest posts and link-insertion requests are not accepted, and are not answered.
More about who publishes this and how the numbers are produced: About InfraPlaybook and our testing methodology.