Skip to content

Getting Started

Jump to bottom
rowpacmal edited this page Sep 9, 2026 · 2 revisions

Getting Started

Edge Studio turns a Raspberry Pi into a local workbench for connecting devices, automating data, and creating verifiable proof records — all from a browser on your own network.

This guide gets you from a fresh Raspberry Pi to your first proof record.

Prerequisites

  • A Raspberry Pi (or another ARM/Linux host) with network access
  • SSH or terminal access to that machine
  • A modern browser on a device that can reach the Pi's local IP address

Docker and Docker Compose are installed automatically by the installer if they're missing.

1. Install Edge Studio

Run the one-line installer on the Pi:

curl -fsSL https://raw.githubusercontent.com/edge-studio-technology/edge-studio/main/install.sh | sudo bash

The installer will:

  • Check that it's running as root/sudo on a Linux host
  • Install Docker if it isn't already present
  • Download the Edge Studio runtime bundle to /opt/edge-studio
  • Verify the bundle's signature before unpacking it
  • Generate a self-signed TLS certificate
  • Start the app with docker compose up -d --build

Optional: check the installer before running it

The command above pipes a script straight into sudo bash. If you'd rather look before you leap, download a released version, check it against its published checksum, and read it first:

# 1. Download the installer at a release tag (not main)
curl -fsSL https://raw.githubusercontent.com/edge-studio-technology/edge-studio/v0.40.0/install.sh -o install.sh

# 2. Fetch that release's checksum and compare
curl -fsSL https://raw.githubusercontent.com/edge-studio-technology/edge-studio-manifests/main/edge-studio/release/install.sh.sha256 -o install.sh.sha256
sha256sum -c install.sh.sha256

# 3. Read it, then run it
less install.sh
sudo bash install.sh

Step 2 should print install.sh: OK. If it prints FAILED, stop — don't run the script.

Hardware flags work the same way here, e.g. sudo env ENABLE_GPIO=true bash install.sh.

Two things worth knowing:

  • Use a release tag, not main. The checksum is published per release, so it matches the installer at that tag. Checking main against it will fail whenever main has moved ahead — that's expected, not a sign of tampering.
  • This detects a modified file, not a forged one. The checksum comes from the same project that publishes the installer, so it catches corruption and casual tampering, not someone who controls the project's accounts. SECURITY.md explains the limits and what would close them.

This step only covers the installer itself. Everything it downloads afterwards — the runtime bundle and the container images — is signature-verified automatically, whichever way you install.

Optional hardware support can be enabled at install time by setting an environment variable before bash, for example sudo env ENABLE_GPIO=true bash:

Flag Enables
ENABLE_GPIO=true GPIO input devices (buttons, PIR motion sensors)
ENABLE_CAMERA=true Raspberry Pi Camera capture
ENABLE_SENSORS=true I2C environmental sensors (BME280 / BME680)
ENABLE_MQTT_BROKER=true A built-in local MQTT broker

Leave these off unless you need that hardware — they're disabled by default.

2. Open Edge Studio

In a browser, go to:

https://<pi-ip>:8080

(or https://localhost:8080 if you're on the Pi itself).

Your browser will warn about the self-signed certificate — this is expected for a local install. Choose Advanced → Continue to proceed. Traffic is still encrypted.

3. Complete first-run setup

On first launch, Edge Studio walks you through a short setup wizard:

  1. Create a local admin credential — a 6-digit PIN, or a password with at least 8 characters (uppercase, lowercase, a number, and a symbol).
  2. Create or connect an Integritas Connect account — this is what lets Edge Studio create proof records.
  3. Review and finish — confirm the connected account and enter the dashboard.

There's a single local admin account (no username), so future sign-ins just need your PIN or password.

4. Take a quick tour

Once you're in, the sidebar covers everything you need:

  • Devices — connect HTTP services, webhooks, MQTT, GPIO, environmental sensors, and Pi Camera as inputs, capture devices, or outputs.
  • Automation — build workflows from triggers, data steps, logic, and actions, with a live preview of the data flowing through.
  • Integritas — stamp files or workflow data to create a proof record, and check on-chain status.
  • Minima — monitor your local Minima node, wallet, peers, and tokens.
  • Diagnostics — review device reads, workflow runs, and proof history in one place.

5. Create your first proof

The fastest path to a proof record with no extra hardware:

  1. Go to Devices → Add device or source and add an HTTP JSON Source pointing at any reachable JSON endpoint.
  2. Go to Automation and create a workflow: Manual run → Fetch data source → Show preview.
  3. Attach Stamp data to the Fetch data source block.
  4. Run the workflow and check Diagnostics — you should see the run, the fetched data, and a new Integritas proof with its UID, hash, and on-chain status.

Next steps

  • Have real sensors, cameras, or an ESP32 board? See Things you can test for a full list of devices and matching workflow blocks.
  • Want to develop locally instead of installing on a Pi? See the README for native dev and full Docker dev setups.
  • Curious about what's off by default and why? See SECURITY.md.

Clone this wiki locally