Contact
The fastest way to reach me is by email. I read every message. Replies usually go out within a few days — sometimes sooner, sometimes slower depending on what's on fire that week.
For questions, corrections, or topic suggestions
Tried something from a post and hit an edge case I didn't document? Found a typo or a dead link? Have a strong opinion about which backup tool actually deserves the number-one slot? I'd like to hear it.
Email: hello@createinnovateexplore.com
If you're writing about a specific post, please include the URL — it's much faster than me hunting through the site to figure out which piece you meant.
For brand partnerships and review units
I'm selective about who I work with. Create, Innovate, Explore is built on trust, and every published recommendation is for a piece of gear I actually own. If you represent a brand I'd genuinely install in my own rack, I'd love to talk. If you're sending a cold pitch for a "premium VPN partnership," please don't.
Email: hello@createinnovateexplore.com with the subject line "Partnership"
For licensing or syndication
If you want to republish an article or diagram from Create, Innovate, Explore — ask first. The answer is usually yes, with attribution and a canonical link back. The answer is sometimes no, and I'll tell you why.
Email: hello@createinnovateexplore.com with the subject line "Licensing"
For guest post services and SEO agencies
I do not accept guest posts, sponsored articles, link insertions, or "content partnerships" from third-party SEO shops. Please don't ask. If your pitch contains the phrase "high DR website," we are not a match.
Dispatch, the newsletter
If you want regular updates without having to remember to visit the site, Dispatch is the answer. One email every Sunday, one-click unsubscribe at the top.
What I can't help with
A few things, just so neither of us wastes time:
- I can't give professional, medical, or legal advice — please consult a qualified expert
- I can't give live support when your homelab is on fire at 3am. File an issue in the actual project's GitHub, or check their Discord — the maintainers are faster than I am
- I can't debug your specific setup over email. Posts here are written to be reproducible; if a guide isn't working for you, note the version numbers and I'll update the guide
For everything else, I'm at hello@createinnovateexplore.com and I'd like to hear from you.
— Theo