Skip to main content
The NSP daemon reads its settings from axon.toml — a TOML file that controls everything from the API port and authentication requirements to how aggressively the daemon scans for new processes. You can also override any setting with an AXON_* environment variable without touching the file, which is especially useful in CI pipelines and containerized environments.

Config File Locations

The daemon looks for axon.toml in three locations and layers them in priority order — later sources override earlier ones, and environment variables always win:
The GUI installer and axon-daemon.exe init both create the system-wide config at C:\ProgramData\Nelieo\axon.toml. This is the file to edit for most deployments.

Full Configuration Reference

Below is a complete axon.toml with every available option documented. All values shown are the defaults — you only need to include the keys you want to change.

Environment Variable Reference

Every axon.toml key has a corresponding environment variable. Variables follow the format AXON_<SECTION>__<KEY> with a double underscore (__) between the section and key names. Environment variables always override the config file.

Example Configurations

CI / Testing Environment

In CI, you typically want no authentication, a fresh schema registry on every run, and verbose readable logs. Set these with environment variables so your config file stays unchanged:

Minimal Development Config

For local development with a single agent, use this minimal axon.toml to get fast refresh cycles and skip authentication overhead:

Startup Warnings

The daemon prints prominent warnings when it starts with insecure settings. These warnings are intentional — they tell you when your configuration is unsafe for a production environment:
Do not suppress these warnings by adjusting log levels. If you see them on a production system, fix the configuration — set require_key = true and remove allow_all_origins = true before exposing the daemon to any agents or clients outside your local machine.