I run Roon Server on an M1 Mac mini.
I would like the ability to be able to gracefully close down the Roon Server, as opposed to having to go into Activity Monitor and kill: Roon Server, Roon Appliance and RAATServer.
This is a basic function that should be available so that Roon can be completely closed down in an orderly manner.
Put it in as a feature request in the feature request section.
Or use launchctl to control the Roon service. (I no longer use macOS but assume this is still how macOS starts | stops | loads services.)
I’ve moved your post to the Feature Suggestions category of the forum. Don’t forget to vote for your own suggestion by using the Vote button.
Thanks, I have run out of votes now, otherwise I would. 
I second this, as launching Roon from launchctl has been disabled from latest versions, seeing that this kind of starting the program results in “No access to Local Network” - but when it is launched manually, it does have access to Local Network.
So, until this new “no access to Local Network” when launched from launchctl is solved, or more general, I would like a timed “switch on and off” feature, if only to “release and clean” memory and handle resources on the computer.
The RoonServer does not have Access to Local Network anymore,
this started with the last version,
when started Roon.app from launchctl 
From the macOS UI there are no issues.
I guess nobody tests this kind of thing at Roon …
05/18 00:13:42 Debug: connecting to server attempt number: 21
05/18 00:13:43 Debug: connecting to server attempt number: 22
05/18 00:13:43 Debug: connecting to server attempt number: 23
05/18 00:13:44 Debug: connecting to server attempt number: 24
==> RoonServer_log.txt <==
05/18 00:13:44 Debug: [easyhttp] [17] POST to https://api.roonlabs.net/discovery/1/register returned after 183 ms, status code: 200, request body size: 1 KB
05/18 00:13:44 Trace: [inetdiscovery] registered 1 devices, 3 services
==> Roon_log.txt <==
05/18 00:13:44 Debug: connecting to server attempt number: 25
05/18 00:13:45 Debug: connecting to server attempt number: 26
05/18 00:13:45 Debug: connecting to server attempt number: 27
05/18 00:13:46 Debug: connecting to server attempt number: 28
05/18 00:13:46 Debug: connecting to server attempt number: 29
05/18 00:13:46 Info: [stats] 405566mb Virtual, 677mb Physical, 211mb Managed, 466mb estimated Unmanaged
05/18 00:13:47 Debug: connecting to server attempt number: 30
05/18 00:13:47 Debug: connecting to server attempt number: 31
05/18 00:13:48 Debug: connecting to server attempt number: 32
05/18 00:13:48 Debug: connecting to server attempt number: 33
==> RoonServer_log.txt <==
05/18 00:13:49 Debug: [easyhttp] [18] GET to https://api.roonlabs.net/push-manager/1/connect returned after 171 ms, status code: 200, request body size: 0 B
05/18 00:13:49 Debug: [push2] push connector url received from push manager: ws://push-connector-v2-0.prd-roonlabs-1.prd.roonlabs.net/
05/18 00:13:49 Trace: [push2] connecting to push2 connector at ws://push-connector-v2-0.prd-roonlabs-1.prd.roonlabs.net/
==> Roon_log.txt <==
05/18 00:13:49 Debug: connecting to server attempt number: 34
==> RoonServer_log.txt <==
05/18 00:13:49 Trace: [push2] connected to push2 connector at ws://push-connector-v2-0.prd-roonlabs-1.prd.roonlabs.net/
==> Roon_log.txt <==
05/18 00:13:49 Debug: connecting to server attempt number: 35
05/18 00:13:50 Debug: [easyhttp] [4] POST to https://api.roonlabs.net/device-map/1/register returned after 179 ms, status code: 200, request body size: 1 KB
05/18 00:13:50 Trace: [devicemap] device map updated
05/18 00:13:50 Debug: connecting to server attempt number: 36
05/18 00:13:50 Debug: connecting to server attempt number: 37
05/18 00:13:51 Debug: connecting to server attempt number: 38
05/18 00:13:51 Debug: connecting to server attempt number: 39
==> RoonServer_log.txt <==
05/18 00:13:52 Info: [stats] 407134mb Virtual, 2386mb Physical, 1222mb Managed, 1164mb estimated Unmanaged
==> Roon_log.txt <==
05/18 00:13:52 Debug: connecting to server attempt number: 40
05/18 00:13:52 Debug: connecting to server attempt number: 41
05/18 00:13:53 Debug: connecting to server attempt number: 42
05/18 00:13:53 Debug: connecting to server attempt number: 43
05/18 00:13:54 Debug: connecting to server attempt number: 44
05/18 00:13:54 Debug: connecting to server attempt number: 45
05/18 00:13:55 Debug: connecting to server attempt number: 46
05/18 00:13:55 Debug: connecting to server attempt number: 47
05/18 00:13:56 Debug: connecting to server attempt number: 48
05/18 00:13:56 Debug: connecting to server attempt number: 49
Don’t you have the menu option to quit Roon Server? This will close both Roon Server and Roon Appliance.
RAATServer is a background process that is associated with Roon and will be closed when you quit Roon.