Contact Dedicated AI Hardware
One address, read by one person. Corrections and sources get priority; everything else gets read when there is time.
This is a small site about a specific engineering argument. It has no support desk and no ticketing system. What it does have is a genuine interest in being right, which means the most valuable message you can send is one that shows a page here is wrong and explains why.
What to send
Corrections
If a figure is wrong, a specification has changed, or a claim has been overtaken by newer hardware, say so plainly. The most useful corrections include the page name, the exact sentence that is wrong, what the correct fact is, and where you read it. A correction with a source gets acted on. A correction that is only an assertion usually gets checked and then set aside.
Sources and measurements
If you have measured a machine and the numbers disagree with what this site claims, that is interesting. Include the model, the quantization, the prompt length, the measured tokens per second after warm-up, the time to first token, and the idle draw. Measurements from someone else's machine are treated as evidence, not as gospel, but they are exactly the kind of material that improves a page.
Questions about the argument
Disagreement is welcome when it engages with the reasoning. If you think the case for dedicated hardware is overstated, say which part and why. The site already publishes its own list of limits; a good counterargument extends that list or shows that one of the entries is wrong.
Suggestions for pages
Topics that fit the existing argument are the ones most likely to be written. Storage design for model weights, network configuration for a local endpoint, backup strategy for a private knowledge base, and cooling in small rooms are all fair game if there is enough substance to say.
What this site cannot help with
Being clear about this saves everyone time.
- Product support. This site does not sell or service anything. If a machine will not boot, the vendor is the right destination.
- Purchasing advice for a specific budget. The reasoning here is general and durable. Which exact part to buy this month depends on local prices and availability that change weekly.
- Licensing questions. Model licenses vary enormously and change often. Read the license that ships with the weights you download.
- Legal, medical, or financial interpretation. The site discusses privacy as an engineering property. It does not give advice in regulated fields and should not be read as doing so.
- Anything requiring access to your machine. Nobody here will ask for remote access, credentials, or a token. Treat any message that does as an attempt at fraud, whatever it claims to be.
How to write a message that gets a reply
Short and specific beats long and general, every time.
- Name the page. Homepage, bandwidth article, power article, ownership article, or this one.
- Quote the claim. A few words are enough to identify the sentence in question.
- State what you believe instead. One sentence, no preamble.
- Give the source or the measurement. A link, a datasheet, or your own logged numbers.
- Skip the pleasantries. They are welcome, but they are not needed. A blunt correction is appreciated, not resented.
Messages that follow that shape are usually answered within a few days. Messages that arrive as a long unstructured complaint about a vendor usually are not answered at all, because there is nothing in them that can be acted on.
Privacy of correspondence
Anything sent here is read by a person, not ingested into a training pipeline, and it is not published, quoted, or attributed without permission. If you send measurements and want them credited, say so. If you want to stay anonymous, that is equally fine and no explanation is required.
The site itself collects nothing. There are no analytics, no cookies, and no third-party scripts on any page. The only external request any page makes is a single font stylesheet from Google Fonts, which is a deliberate and slightly grudging exception: it is the one dependency the design was not willing to give up, and readers who block it will see the same pages in a system monospace face with no loss of content.
What happens after you write
Corrections that check out cause the page to change, usually within a week, with the sentence corrected rather than deleted. If a correction invalidates a larger claim, the surrounding paragraph is rewritten rather than patched, because a page that contradicts itself is worse than one that was merely wrong. Where a change is significant, the revised wording stands on its own without a note about what it used to say; the point of the page is to be right now, not to keep a history of its mistakes.
If a message raises something genuinely interesting, it often becomes a new page rather than a reply. That is a better use of the material and it is how most of the sections on this site were first suggested.
Before you write
Two of the most common questions are already answered on the site, and checking them first saves a round trip.
If you are wondering whether a dedicated machine is worth it for your usage, the arithmetic is laid out in the ownership article, including the volumes at which renting is genuinely cheaper. If you are wondering why a machine with impressive specifications feels slow, the answer is almost always in the bandwidth article. And if you are wondering why an idle box matters so much, the power article covers the standby regime in detail.
The address for editorial mail is editor@dedicated-ai-hardware.com. There is no phone number, no live chat, and no form, because a form on a static site either collects your data or pretends to work, and neither is worth building.