See inside every Raspberry Pi and gateway you run.

A small agent for the Raspberry Pi, gateways and any Linux machine next to your microcontrollers: its web interface from anywhere, the log you choose, memory, load, temperature and disk, alerts, and updates as any file to any command.

Adding it

curl -fsSL https://pinscope.dev/install.sh | sudo sh -s psk_...

What you get

• Its web server from anywhere: an HTTPS address for the HTTP server already on the device, behind your login, a share link or an API token. No port forwarding, no VPN.
• Logs: live and stored, searchable, from the device's normal log output.
• Health: memory, stack, signal, uptime and restarts without code, and your own numbers with one call.
• Crashes: kept across the reboot and decoded with the ELF of the build.
• Updates: from the dashboard, with the platform's own fallback when the new firmware does not come back.
• Alerts: email or webhook when a device goes offline or crashes.

Guides

• Pinscope now runs on Zephyr, Raspberry Pi Pico, Linux and ESP8266
  Remote access, logs, crash reports and OTA updates, as on the ESP32, now for Zephyr, the Pico 2 W, Linux and the ESP8266. About 9 KB of RAM.
• Reaching a Raspberry Pi behind NAT, CGNAT or 4G
  Reach a Raspberry Pi or Linux gateway on someone else's network: port forwarding, VPNs and tunnels compared, plus logs, health and updates.
• Memfault, Golioth, nRF Cloud and Pinscope compared
  Device management and observability for embedded fleets compared: Memfault, Golioth, nRF Cloud and Pinscope, by features, platforms and pricing.
• The Cyber Resilience Act, for the devices you ship
  What the EU Cyber Resilience Act asks of device makers, and when: an SBOM, handling vulnerabilities, security updates, a support period, reporting. What Pinscope does for it, and what it does not.

Other platforms: ESP32 · Zephyr · Raspberry Pi Pico · ESP8266