Contact

Ask the people who wrote the daemon.

This form reaches the engineers who build atlasd and write these pages, not a sales queue. An adapter for your radio, a configuration key that does not behave as documented, a page that is wrong: it all lands in one inbox, and a person answers it.

Answered by an engineer, usually within a working dayNo marketing list
Who should write

Bring us the question the docs did not answer.

IntegrateIntegrators embedding atlasd in a platform, and adapter authors bringing a new bearer — a radio, a modem, a serial link. Tell us the hardware and how it exposes the link to the host.
ConfigureA key in the configuration reference, a REST API response or a CLI output that does not match what you see. Include the first line of atlasd --version.
EvaluateDownloads, the security documentation and field data are granted together through request access. Write here first if you are not sure what to ask for.
DocsA page that is wrong, unclear or missing. Name the URL and what you expected to find there.
SecurityVulnerabilities follow the disclosure policy. Keep exploit details out of a first message; we agree a channel with you.

If our mail service is unreachable, your email client opens with the same message, so nothing is silently lost. Prefer email? office@nexusatlas.io reaches the same people. Please keep classified or export-controlled information out of this form.

Esc
↑ ↓ navigateEnter — openEsc — close