Skip to content

Astromesh Node

Astromesh Node is the native system-level deployment of Astromesh. It installs the astromeshd daemon and astromeshctl CLI as a first-class service on your operating system — integrating with systemd on Linux, launchd on macOS, and Windows Service Manager on Windows.

Astromesh Node packages the Astromesh runtime into platform-native installation artifacts:

  • Linux (Debian/Ubuntu) — .deb package with APT integration and systemd unit
  • Linux (RHEL/Fedora/CentOS) — .rpm package with systemd unit
  • macOS — .tar.gz with install script and launchd plist
  • Windows — .zip with PowerShell installer and Windows Service registration

Each platform installs the same two binaries — astromeshd (the daemon) and astromeshctl (the CLI) — along with a platform-appropriate service manager integration.

Astromesh Node runs as a supervised OS-level service:

  • Linux: systemd Type=notify, Restart=on-failure, watchdog health checks, journald logging
  • macOS: launchd KeepAlive=true, stdout/stderr to /Library/Logs/Astromesh/
  • Windows: Windows Service (astromeshd), registered with the bundled astromeshd-service.py wrapper

astromeshctl provides a unified CLI across all platforms:

Terminal window
astromeshctl status # Daemon status table
astromeshctl init # Interactive configuration wizard
astromeshctl doctor # Health diagnostics
astromeshctl agents list # List loaded agents
astromeshctl providers list # List configured providers
astromeshctl config validate # Validate config files

Starting, stopping and tailing logs go through the platform service manager (systemctl, launchctl, Start-Service) — see Service control.

The astromeshctl init wizard offers 4 roles, each backed by a profile that controls which services activate on the node:

RoleServicesUse Case
fullAll servicesSingle-node, everything on one machine
gatewayapi, channels, observabilityPublic entry point, routes to workers
workerapi, agents, tools, memory, rag, observabilityAgent execution node
inferenceapi, inference, observabilityDedicated LLM inference

The same runtime.yaml configuration works identically on all platforms. Filesystem paths are normalized per OS (see Configuration).

MethodBest ForOS IntegrationOrchestration
Astromesh NodeSingle-server production, edge, on-premNative servicePlatform service manager
From SourceDevelopment, contributingNoneManual
Docker Single NodeContainerized, CI/CDDocker daemonDocker Compose
Helm / KubernetesMulti-node, cloud-nativeNoneKubernetes
Astromesh OrbitManaged cloudNoneGCP Cloud Run

Choose Astromesh Node when:

  • You want a production-ready deployment without containers or Kubernetes
  • You need the daemon to start automatically on boot and restart on failure
  • You are deploying to a bare-metal server, VM, or edge device
  • You prefer CLI-based management over container tooling

Astromesh Node installs the following components:

astromeshd — Agent runtime daemon (HTTP API, agent execution, model routing)
astromeshctl — CLI for service management and configuration
runtime.yaml — Platform-aware config (services, api, providers, memory)
*.agent.yaml — Agent definitions (YAML, same schema as Docker/K8s deployments)

The daemon exposes the same REST API (/v1/agents/{name}/run, /v1/ws/agent/{name}, etc.) regardless of platform. Existing integrations and SDKs work without modification.