Notes

Contact: what to send, when to expect a reply

Send hardware, current system, goal and timeline to hello@localdeploy.dev. Also covers reply times, privacy and what this site does not do.

Updated 2026-11-16

One email address, no form

This site does not collect form contents. Everything goes through email:

hello@localdeploy.dev

No formal format needed, but specific information gets a more useful reply.

What to include

  1. Hardware: CPU model, RAM, free disk, GPU and VRAM, upstream bandwidth.
  2. System: what is installed, whether it is virtualised, whether Docker or a NAS is already running.
  3. Goal: which model or service, who uses it, roughly how many people.
  4. Current state: where it is stuck, the error, what you already tried.
  5. Constraints: budget, timeline, whether downtime is possible, whether remote access is acceptable.
  6. Assessment text: if you generated it on the home page, paste it in.

A template you can fill in:

Subject: localdeploy.dev setup

CPU: i5-12400
RAM: 32 GB
Free disk: 500 GB
GPU: 1 × RTX 3060 12 GB
Upstream: 50 Mbps
System: Ubuntu Server 24.04, Docker installed
Goal: shared by 3 people, document Q&A and code completion
Current state: the model runs, but a larger one runs out of VRAM, and services do not come back after reboot
Constraints: weekend downtime is fine, limited budget, start with a review

Reply times

  • The aim is a reply within two business days; busy weeks take longer.
  • If key information is missing, the reply asks for it rather than quoting blindly.
  • No urgent jobs, and no 24/7.

What this site does not do

  • No account takeover, no long-term custody of passwords or tokens.
  • No 24/7 on-call or emergency response.
  • No promise of model speed, or of every version combination working.
  • No hardware sales and no affiliate commission.

Privacy

  • No form contents are collected; the assessment runs in your browser.
  • Email is used to reply to your request; there is no marketing list.
  • Before sending logs or configuration, remove tokens, passwords and public IPs.
  • When temporary access is needed, the default is that you run the commands. If direct access is required, it uses temporary credentials removed afterwards.

Next

Email is the only channel. Questions, corrections or a scope request: hello@localdeploy.dev. This page also exists as Markdown: /en/contact.md.

Not sure where to start?

Run the assessment first, or send your setup and goal by email. The reply says whether it fits and what happens next.