Install Netdata with kickstart.sh | Installation
Skip to main content kickstart.sh is the recommended way to install Netdata. This installation script works on all major Linux distributions. It automatically detects the best way to install Netdata for your system. What does kickstart.sh actually do? Detects your OS and environment Checks for an existing Netdata installation Installs using: Native packages (preferred) Static build (fallback) Build from source (last resort) Installs an auto-update cron job (unless disabled) Optionally connects your node to Netdata Cloud Quick Overview Task Command / Location Notes Install Netdata Run kickstart.sh Choose nightly or stable release Connect to Cloud Use claim token Connect node to Netdata Cloud Customize install Pass flags to control behavior Directory, release, update control Export config for IaC Copy config from Cloud UI For automation & Infrastructure as Code Run the One-Line Install Command To install and connect to Netdata Cloud in a single step from your terminal: wget curl wget -O /tmp/netdata-kickstart.sh https://get.netdata.cloud/kickstart.sh && sh /tmp/netdata-kickstart.sh Do you want automatic updates? default: enabled Do you want nightly or stable releases? default: nightly Do you want to contribute anonymous statistics? default: enabled Do you want to connect the node to Netdata Cloud? default: disabled curl https://get.netdata.cloud/kickstart.sh > /tmp/netdata-kickstart.sh && sh /tmp/netdata-kickstart.sh Do you want automatic updates? default: enabled Do you want nightly or stable releases? default: nightly Do you want to contribute anonymous statistics? default: enabled Do you want to connect the node to Netdata Cloud? default: disabled tip Pick Stable or Nightly : Check the guide for differences. 🔍 Where to find your claim token Log in to Netdata Cloud Navigate to your Space Go to Space Settings → Nodes Click Add Node → Copy Claim Token Optional Parameters for kickstart.sh Use these flags to customize your installation.
Category Parameter Purpose Directory Options --install-prefix Custom install directory --old-install-prefix Clean previous install directory Interactivity --non-interactive No prompts (good for scripts) --interactive Force interactive prompts Release Channel --release-channel nightly , stable , preview , or default (automatic selection) --install-version Install specific version Auto-Updates --auto-update Enable updates --no-updates Disable updates Synthetic monitoring --install-dem-runtime Explicitly install the optional DEM browser runtime Netdata Cloud --claim-token Provide claim token --claim-rooms Assign node to specific Cloud Rooms Reinstall/Uninstall --reinstall Reinstall existing Netdata --uninstall Uninstall Netdata completely note Managing auto-updates after installation: kickstart.sh enables daily auto-updates by default.
To disable, check, or re-enable auto-updates — including why netdata-updater.conf cannot disable them — see Managing Automatic Updates in the Update guide. To use preview releases, pass --release-channel=preview . This channel includes prereleases and final releases. Without a version pin, preview installs the latest version published to that channel. Native installations use the netdata-preview repository. Static and source builds use only preview artifacts from artifacts.netdata.cloud , with no GitHub fallback.
You can pin a prerelease with --install-version , for example --install-version 2.13.0-rc1 . Optional browser runtime for synthetic monitoring Add --install-dem-runtime to an ordinary kickstart install or update to prepare the browser runtime used by DEM journeys and Lighthouse. Without this option, kickstart does not acquire a browser runtime. The option also works with an existing installation supported by kickstart. sudo sh ./kickstart.sh --install-dem-runtime For local, rootful Docker on Linux, start Netdata with the documented container configuration , including a persistent /var/lib/netdata and the documented AppArmor setting where applicable.
Currently you must set runtime.release_url in the container's dem.conf to the signed metadata URL for its architecture. Run sudo sh ./kickstart.sh --install-dem-runtime --docker-container netdata on the daemon host, using the container's exact name. Kickstart prepares any required host policy and installs the runtime as the container's service account. After the first installation succeeds, run docker restart netdata to activate it.
The host does not need an Agent installation. Rootless, nested and remote Docker need separate administrator setup. For those configurations and retirement, see Docker browser runtime setup . For native package installations, kickstart installs the optional netdata-dem-runtime package using the same package manager and interaction policy as the Agent. Native runtime packages require the named netdata service account. Package hooks qualify the runtime and may restart a previously running Agent.
If package installation or runtime readiness fails, kickstart reports failure; it does not switch to managed delivery. For static and source installations, kickstart calls the installed netdata-dem-runtime.sh host helper. The helper prepares the necessary AppArmor launcher allowance, then runs dem.plugin runtime install --allow-download as the configured nonroot Netdata service user. It reads the installed Agent's normal configuration to find its plugin, administrator/stock configuration and persistent-state directories, including custom installation prefixes.
The CLI reads runtime.release_url from dem.conf and fetches the canonical package keyring from https://repository.netdata.cloud/netdatabot.gpg.key ; kickstart does not provide a substitute trust key or release URL. This managed action downloads the signed runtime matching the Agent and permits companion downloads during future Agent updates. Restart the Agent explicitly after first setup. Kickstart does not perform that managed activation.
The Agent's --no-updates option controls its update schedule. To require explicit runtime inputs or download consent for each paired update, use the installed helper with install --agent /path/to/netdata --allow-download --manual-updates . See browser runtime host setup for paired updates/recovery, offline inputs, policy scope and removal. The browser runtime requires Linux x86_64 or aarch64 , an Agent containing the runtime CLI, and a host where browser sandboxing is allowed.
Native package qualification requires a running systemd host. A missing runtime.release_url for managed setup, an unavailable optional package, or failed browser qualification makes explicit setup fail even if Agent installation succeeded. Kickstart does not inspect live service -c / -u arguments or environment overrides. Such custom launch setups, and plugin paths requiring escaping, must use the runtime CLI directly with the same service identity and configuration as the Agent, after an administrator prepares any required host policy through the helper's policy-only route. --install-dem-runtime cannot be combined with --offline-install-source , --prepare-offline-install-source , --repositories-only , --claim-only , or --uninstall .
For offline static/source installation, run the installed host helper as root with install --agent /path/to/netdata --release /absolute/release.json --archive /absolute/runtime.tar.zst ; provision the offline keyring as described in the host setup guide . Native installations use the package manager's offline provisioning. --dry-run reports the intended action without acquiring or qualifying a runtime. Environment Variables These environment variables provide additional customization options (most users won't need these): Variable Purpose Default Behavior TMPDIR Specify directory for temporary files System default temp directory ROOTCMD Command to run with root privileges Uses sudo , doas , or pkexec (in order) DISABLE_TELEMETRY Disable telemetry when set to non-zero value Telemetry enabled note
The rest of this page is on the live site.