We’re excited to launch our first HomelabAddiction printable 🎉 Become an early supporter and get 20% off withEARLY20GET NOW
contact // homelabaddiction
One inbox handles all of it — corrections to a guide, a project you want in the self-hosted directory, and every commercial enquiry below. There is no form and no ticket queue. Put the subject line we suggest on your message and it lands in the right pile.
This site does not provide individual troubleshooting or paid consulting on your own lab. Replies depend on availability and can take time.
Write to
[email protected]Clicking any button on this page opens your mail client with the subject already filled in.
Start a partnership enquiryPick a subject line
A command that no longer works, a version that moved, a spec that is wrong. Tell us which guide and what you saw — corrections get priority over everything else on this page.
Report a correctionSubject: Correction — [guide URL]
A project that belongs in the directory, or a guide you wish existed. Include a repository link for projects, or the problem you were trying to solve for a guide.
Suggest somethingSubject: Suggestion — [project or topic]
Product promotion, sponsored reviews, and link placements. Everything in the section below starts with this subject line. Rates are quoted per request.
Start a partnershipSubject: Partnership enquiry — [company or project]
Press, licensing, takedowns, privacy requests, and anything the categories above do not cover. Plain question, plain answer.
Send a messageSubject: General enquiry
Work with us
Readers arrive here mid-problem, from a search result, with a terminal open on the other screen. That is who a placement reaches. Everything below is quoted per enquiry — there is no fixed rate card.
Placements and links
Placement inside guides that already rank for the problem your product solves. We only place a product in a guide where it is a genuine answer to what the reader came for.
Your product written into a relevant, already-published guide — named in context, with the setup notes a reader needs to actually try it. Not a banner bolted onto an unrelated page.
A permanent in-content placement in the body of a guide — your product named and linked where it makes sense to the reader. It stays for the life of the article rather than expiring on a term.
A full entry in the self-hosted directory: verified resource requirements, ports, volumes, a Compose file readers can copy, and links to your repository and documentation.
Your project or product carried on the homepage, a system-area hub, or the top of a category archive, where readers browsing rather than searching will meet it first.
Content collaborations
Work that gets written after the thing has been installed and run. We test first and publish what we found — including the parts that bit us.
Send hardware or a licence and we build with it on a real lab, then publish what we found. Findings are ours; you get a tested review rather than a rewritten press release.
A dedicated guide for deploying, configuring, or migrating to your product — written in the site voice, with the Compose file, the ports, and the caveats a reader needs.
Inclusion in the comparison tables readers use to choose between tools, with your specs, license, and pricing model stated accurately alongside the alternatives.
Pitch a guide you are qualified to write. We accept a small number of contributed guides from people who actually run the setup, edited to the same standard as everything else.
Audience and ongoing
For teams who want more than a single placement. Ask for current audience figures and we will send what we actually measure — we do not publish numbers we cannot source.
A placement in a newsletter issue that goes to readers who opted in for homelab and self-hosting work. One sponsor per issue, clearly marked.
First-party ad slots served from our own campaign system rather than an ad network — no third-party tracking scripts, and a click count you can reconcile against your own.
A standing arrangement across guides, the directory, and the newsletter, planned quarterly instead of negotiated one placement at a time.
Affiliate or referral terms for hardware and services we would recommend anyway. Affiliate links are disclosed on every page that carries them.
Before you send
A brief with these five things gets a real answer instead of a round of questions.
Saves us both time
These are settled, and a budget does not move them.
How paid work is labelled is set out in the editorial policy and the affiliate disclosure.
No budget needed
Most of what lands in this inbox costs nothing and always will. Nothing here is behind a payment.
Actively maintained, self-hostable without a paid licence for the core features, and documented well enough for us to test? Send the repository link and it goes in the queue at no cost.
Browse the directoryFound a command that broke, a spec that drifted, or a version that moved on? Corrections are free, always welcome, and handled before anything commercial.
Read the editorial policyNo budget and no product to place, but a guide you wish existed? Tell us the problem you were stuck on. It costs nothing and it shapes what gets written next.
See what is publishedIf a guide saved you a rebuild and you would rather send a tip than a brief, there is a Ko-fi page. Entirely optional, and nothing on the site is gated behind it.
Support the labBefore you write
Email is the only channel we monitor properly, so it is the one on this page. Responses depend on availability and can take time — if something is time-sensitive, say so in the subject line.
Corrections first, then editorial and directory submissions, then commercial enquiries. Partnership emails that include a target URL, the placements wanted, and a budget get answered fastest, because there is something to answer.
Yes. Sponsored placements, paid reviews, and affiliate links are labelled on the page that carries them, in line with the editorial policy and the affiliate disclosure. This is not negotiable and it is not something we will quietly drop for a larger budget.
No. We will run your product, follow your documentation, and write what happened. If it does not hold up, that goes in the guide. You are buying the placement and the hands-on testing, not the conclusion.
Rates depend on the surface, the guide, and whether the work is one-off or ongoing, so nothing is published as a fixed price list. Ask with your target pages and we will quote against them.
No. Getting listed in the self-hosted directory is free and always has been. If a project meets the criteria it gets added on merit; paid options only exist for placement beyond a standard entry.
Still the right answer for everything above: [email protected]
