Contact the ClawBox Blog — Get in Touch With Our Editorial Team
Thank you for wanting to reach us. We read every message we receive, even if we cannot always reply to every one. This page explains how to get in touch, how quickly you can expect a response, and what kinds of messages we are best able to help with.
Before you write: many common questions are answered further down this page in the frequently asked questions section. If your question is about the hardware we write about rather than about this blog itself, the FAQ is a good place to start.
How to Reach Us
We keep our contact channels deliberately simple. You can write to us by email at hello@clawbox.blog. That single address reaches the whole editorial team, and we route messages internally from there. If you are following up on a previous conversation, please reply within the existing thread so we can keep the context together.
We do not currently offer live chat or a phone line. We are a small team, and we would rather do email well than spread ourselves thin across a dozen channels. We also read comments and messages left on the platforms where our work is shared, but email remains the most reliable way to get a considered response.
What to Include in Your Message
A little structure goes a long way. When you write, please include:
- A clear subject line — something like "Correction to the Jetson article" rather than "hi".
- Context — which article or page you are referring to, if any, and a link where possible.
- The specific question or request — the more concrete, the faster and more useful our reply will be.
- How you would like us to respond — by email, or whether a public correction is appropriate.
Response Times
We aim to reply to straightforward messages within two to three working days. During busy periods, or when a message requires research before we can answer properly, it may take up to a week. If your matter is urgent — for example, a factual error in something we have published that could mislead readers — please mark it clearly in the subject line, and we will prioritize it.
If two weeks have passed and you have not heard back, feel free to send a short follow-up. We occasionally lose a message to an over-enthusiastic spam filter, and we are never annoyed by a polite nudge.
Frequently Asked Questions
Do you sell any products?
No. This blog is an editorial project, not a store. We write about private AI hardware, including devices made by various manufacturers, but we do not sell anything ourselves, and we do not earn a commission when you buy something we review. If you are looking for where to buy a device we have written about, we usually link to the manufacturer's own page in the article itself — for example, the official ClawBox site.
Can I submit a guest post?
We rarely accept guest posts, and when we do, it is by invitation. The reason is simple: the value of this site depends on its consistent voice and its independence, and both are harder to preserve when many hands are writing. If you have a genuinely useful piece of research or a first-hand account of running AI locally, we are happy to read it and consider it — but please expect a polite decline most of the time.
Will you review my product?
We consider review requests case by case, but our acceptance bar is high. We only review hardware that is relevant to private, on-device AI, and we only review it if we can spend real time with it. We do not publish sponsored reviews, and sending us a product does not guarantee coverage. If we write about it, the piece will be honest — including the parts the maker might not like.
How do I report an error?
Please email us with the subject "Correction", include the article's URL, quote the sentence in question, and explain what you believe is wrong. If you can point us to a source, even better. We take accuracy seriously, and we publish corrections transparently — we do not quietly rewrite history.
Do you offer advice on setting up my own hardware?
We are happy to point you toward the articles and external documentation that will help, but we cannot provide one-on-one technical support. Running AI locally is well within reach of a patient beginner, and our beginner's guide is the best place to start. For very specific troubleshooting, community forums are almost always more helpful than we can be.
Can I reproduce or translate your articles?
Please ask first. Short quotations with attribution and a link back are fine, but full reproductions and translations require our permission. Write to us with details of where the content would appear and how it would be used, and we will respond as quickly as we can.
Do you have a newsletter?
We do not, and we do not plan to start one soon. The site is small and deliberately quiet. If you want to keep up with new articles, the simplest approach is to check the homepage occasionally, or to follow the platforms where our work is shared. We would rather write well than write often.
How do I suggest a topic?
We welcome suggestions. Email us with a short description of the question or subject you would like to see covered, and tell us why it matters to you. We keep a running list of reader questions and use it to decide what to write next, so your note genuinely helps shape the site.
For the Press
If you are a journalist or researcher and would like to cite our work, quote us, or ask about the field of private AI hardware, please use the same email address and mention "Press" in the subject line. We are happy to provide background and clarification on our published pieces, and we can usually respond to time-sensitive requests faster than general correspondence.
Privacy of Your Correspondence
We treat messages we receive as confidential. We do not publish private emails, and we do not add anyone to a mailing list without explicit consent. If you write to us about a correction, we will publish the correction but not your personal details, unless you specifically ask to be credited. In short: your inbox is your business, and we intend to keep it that way.
Topics We Can Help With
To set expectations clearly, here is a sense of what we are best equipped to answer. We are happy to help with questions about private AI hardware, local language models, and the practicalities of running models at home. We are also glad to receive pointers to new open-weight models, interesting efficiency techniques, and hardware we have not yet covered.
We are less useful for general tech support, and we do not provide one-on-one debugging for specific setups. For those, community forums are almost always a better resource — they are faster, more experienced with edge cases, and populated by people who enjoy the puzzle. We will still do our best to point you in the right direction.
Guest Contributions and Licensing
As noted above, we rarely accept guest posts, but we are always open to hearing from people with genuine expertise or first-hand experience. If you have built something, run something for years, or researched something we should know about, a short note describing your idea is welcome. We cannot promise to say yes, but we do read everything.
For reuse of our work, the rule is simple: short quotations with attribution and a link are fine, and anything more — full reproductions, translations, or derivative works — requires our permission first. Write to us with the details and we will respond as quickly as we can. We are generally happy to help when the use is respectful and properly credited.
Working With Us
We occasionally partner with researchers, educators, and other writers whose work overlaps with ours, but we keep such arrangements narrow and transparent. We do not sell links, we do not publish sponsored content, and we do not let outside parties influence what we write or how we write it. If a partnership ever affects our coverage in any way, we will disclose it plainly on the relevant page.
If you are interested in a genuine collaboration — a joint explainer, a research project, or an educational resource — we are happy to talk. The same email address works for this; just say what you have in mind, and we will take it from there.
A Final Note on Tone
We try to keep this site calm, even when the subject is exciting. The internet has enough shouting about AI, enough panic, and enough hype. What it has less of is patient, careful explanation, and that is the gap we try to fill. If you write to us in the same spirit — curious, specific, and kind — you will almost certainly get a thoughtful reply. We look forward to hearing from you.