grillo · andygrillo · Oct 1, 2026 · Oct 1, 2026
diff --git a/docs/dashboard/data/data-server.md b/docs/dashboard/data/data-server.md
@@ -28,7 +28,32 @@ Sensors send waveform packets over CoAP on UDP, by default to port 5684. Your se
 - Accept inbound UDP on the port you choose
 - Run software that receives Grillo's waveform packets and passes them to your seismic system
 
-[Contact Grillo Support](/support/contact) for the receiver software and for help connecting it to Earthworm or SeisComP. Set this up and test it before you ask for the switch.
+## Receive the data with coap2seis
+
+[coap2seis](https://github.com/grillo/coap2seis) is Grillo's open-source receiver. It runs on your server, listens for the sensors' packets on UDP port 5684, and writes the data to:
+
+| Output | Use it for |
+|---|---|
+| An **Earthworm** ring, through PyEW | Feeding a real-time Earthworm system |
+| **miniSEED** files, one per station, channel, and day | ObsPy, SeisComP, archiving, and post-processing |
+
+Station, channel, and network codes come from the sensors, so the data arrives named the way it is in Grillo Cloud. You can set a fixed network code and the location code (default `00`).
+
+To install it:
+
+```bash
+git clone https://github.com/grillo/coap2seis.git
+cd coap2seis
+pip install -e .
+pip install obspy          # for miniSEED output
+python -m coap2seis
+```
+
+It asks for the output, port, and codes, with sensible defaults. The repository also includes a systemd service for running it permanently. See its [README](https://github.com/grillo/coap2seis#readme) for the full options.
+
+coap2seis reads the sensors' JSON data format. When Grillo points your project at your server, it also switches your sensors to that format; mention coap2seis in your request.
+
+Set up and test the receiver before you ask for the switch. [Contact Grillo Support](/support/contact) if you need help connecting it to your system.
 
 ## Set the data server
 

diff --git a/docs/dashboard/data/waveforms.md b/docs/dashboard/data/waveforms.md
@@ -70,4 +70,4 @@ A CSV export holds up to 20,000 samples. Shorten the interval or remove traces i
 
 ## Continuous data and standard formats
 
-Grillo Cloud does not export miniSEED from the dashboard. If you need a continuous stream in your own seismic software, [send your sensors' data to your own server](/dashboard/data/data-server).
+Grillo Cloud does not export miniSEED from the dashboard. For a continuous stream into Earthworm, SeisComP, or ObsPy, [send your sensors' data to your own server](/dashboard/data/data-server) and receive it with Grillo's open-source [coap2seis](https://github.com/grillo/coap2seis).
diff --git a/docs/events/event-details.md b/docs/events/event-details.md
@@ -6,6 +6,8 @@ title: Event Details
 
 Select an event in the catalog to open its details.
 
+![Event details in Grillo Cloud, with the Review waveforms button, time, magnitude, depth, location, and links to picks and amplitudes](/img/screenshots/event-details.png)
+
 ## Event information
 
 - Event ID

diff --git a/docs/getting-started/what-is-grillo.md b/docs/getting-started/what-is-grillo.md
@@ -35,7 +35,7 @@ Grillo builds connected sensors and cloud software for earthquake and landslide
 
 ## Your own seismic system
 
-Pulse and One can send their seismic data to a server you run, such as Earthworm or SeisComP, instead of Grillo. Grillo switches this on for your project, and you keep managing the sensors in Grillo Cloud. See [Send Data to Your Own Server](/dashboard/data/data-server).
+Pulse and One can send their seismic data to a server you run instead of Grillo. Grillo's open-source [coap2seis](https://github.com/grillo/coap2seis) receives it and passes it to Earthworm, or writes miniSEED for SeisComP and ObsPy. Grillo switches this on for your project, and you keep managing the sensors in Grillo Cloud. See [Send Data to Your Own Server](/dashboard/data/data-server).
 
 ## Getting help
 

diff --git a/docs/support/faq.md b/docs/support/faq.md
@@ -76,7 +76,7 @@ Remove the base's cover and press **RESET**. The base also surveys every time it
 
 ### Can I download my seismic data?
 
-With the [SISTEM add-on](/events), yes: open the waveform review page and select **Download native CSV + metadata**. See [View and Download Waveforms](/dashboard/data/waveforms). For a continuous feed into your own seismic software, ask Grillo to [send the data to your own server](/dashboard/data/data-server).
+With the [SISTEM add-on](/events), yes: open the waveform review page and select **Download native CSV + metadata**. See [View and Download Waveforms](/dashboard/data/waveforms). For a continuous feed into Earthworm, SeisComP, or ObsPy, ask Grillo to [send the data to your own server](/dashboard/data/data-server) and receive it with the open-source [coap2seis](https://github.com/grillo/coap2seis).
 
 For Slide, use [Exports](/slide-cloud/exports).
 

diff --git a/static/img/screenshots/event-details.png b/static/img/screenshots/event-details.png
Original file line number	Diff line number	Diff line change
Expand Up		@@ -70,4 +70,4 @@ A CSV export holds up to 20,000 samples. Shorten the interval or remove traces i

		## Continuous data and standard formats

		Grillo Cloud does not export miniSEED from the dashboard. If you need a continuous stream in your own seismic software, [send your sensors' data to your own server](/dashboard/data/data-server).
		Grillo Cloud does not export miniSEED from the dashboard. For a continuous stream into Earthworm, SeisComP, or ObsPy, [send your sensors' data to your own server](/dashboard/data/data-server) and receive it with Grillo's open-source [coap2seis](https://github.com/grillo/coap2seis).