Support, sources, and release policy
Official references for AtomOS operators, security reporters, and procurement. Elemento does not publish response-time SLAs in this documentation set — contractual support terms are agreed separately with sales@elemento.cloud.
Official documentation
| Resource | URL | Scope |
|---|---|---|
| AtomOS docs (this site) | docs.atomoslinux.cloud/docs | Install, architecture, operations |
| AtomOS product page | elemento.cloud/atomos | Product overview and positioning |
| Electros user guide | docs.electros.cloud | Fleet UI, organizations, VM workflows — authoritative for Electros |
| Install & CLI reference | CLI & ports reference | Ports, flags, bootstrap |
| Feature availability | Feature availability | Capability status snapshot |
When Electros UI behavior and AtomOS host behavior both matter, cross-check Electros docs for control-plane steps and this site for host install, networking, storage, and upgrades.
Contact Elemento
| Need | |
|---|---|
| Product support (AtomOS, Electros integration, production incidents) | support@elemento.cloud |
| Sales, proof-of-concept, licensing, multi-node design | sales@elemento.cloud |
| General enquiries | hello@elemento.cloud |
Postal address
Elemento Srl
Via Virginio Allione 2
12100 Cuneo (CN), Italy
Web: www.elemento.cloud
Vulnerability reporting
Report suspected security vulnerabilities in AtomOS or related Elemento software to support@elemento.cloud with:
- Affected product (AtomOS host,
atomos-cli, Electros integration point, etc.) - Version evidence from
atomos-cli --version(do not guess stable release numbers) - Reproduction steps and impact assessment
- Your contact for coordinated disclosure
Do not include live ELEMENTO_CLUSTER_SECRET values, license files, or customer data in initial reports. Elemento will coordinate remediation and disclosure timing with you where applicable.
Operational hardening: Security architecture.
Release and capability policy
AtomOS evolves through published milestones (for example the 0.9 HTTPS / AtomOS GUI milestone documented in Overview and Networking). This documentation does not assign or guarantee a specific stable package version label for every capability.
| Question | Where to look |
|---|---|
| Is feature X production-ready for us? | Feature availability — then validate on a staging host |
| What is installed on this server? | sudo atomos-cli --version and --info |
| What changed recently? | Elemento release communications via support/portal — not inferred from local RPM trees alone |
| What is deprecated? | e.g. legacy monolithic pre-0.6 package — Upgrades |
Documentation vs warranty
Statuses on the feature availability page are engineering documentation classifications, not a warranty of general availability on every platform. Confirm behavior with atomos-cli --help, release notes from Elemento, and support before fleet-wide rollout.
When Elemento publishes a verified stable public release, update internal runbooks and align with .vitepress/release-meta.ts on this docs site (maintainers).
Related operational pages
- Troubleshooting
- Diagnostic commands
- Upgrades
- Sources for migration and import (workload movement)