Fizzlayer
The physical layer for AI agents.
Connect sensors, phones, and Linux devices to your AI agents. Fizzlayer brings their readings into one dashboard so you can ask questions, watch changes, and set alerts. Fizz, the built-in assistant, helps you understand what your devices are reporting.
Website · Documentation · Interactive demo · Self-hosting · CLI guide
What you can do
- See your devices in one place. Stream real readings or explore the dashboard with sample sensors.
- Connect the hardware you have. Pair a Linux device with the CLI, share phone sensors from a browser, push entities from Home Assistant, or send readings over HTTP.
- Give agents access through MCP. Issue revocable tokens to read sensor data and optionally create dashboard alerts.
- Let a browser agent do it for you. Every page exposes WebMCP tools, so an agent pointed at the site can onboard, manage sensors and alerts, and start a plan checkout. Agents that read first can start at
/llms.txt.
- Ask Fizz about your readings. Use typed chat or optional voice conversations to understand measurements and create threshold alerts.
- Act on changes. Track alerts in the dashboard and optionally receive voice calls to US phone numbers.
Fizzlayer includes a static web app, a Rust API deployed as Vercel Functions, a Supabase database and authentication layer, and a Rust device CLI. It monitors sensor data; physical actuator control is not implemented.
Get started
Try the interactive demo without an account. It uses simulated sensors and local example replies to show the dashboard, alerts, and call previews.
Create a free account, start with sample data, then connect a device from the Sensors or Agents page. You can also deploy your own instance.
Fizzlayer CLI
The command-line tool is named fizz. Install it on a Linux device, including a Raspberry Pi:
curl -fsSL https://fizzlayer.com/install.sh | sh
fizz pair
Enter the displayed pairing code on the Sensors or Agents page, or ask a connected agent to claim it. Approve the request at the device, then start streaming:
fizz run --every 60
The CLI reports CPU temperature, system load, memory usage, and disk usage where available. Send custom readings with:
fizz send temperature_c 22.4 humidity_pct 48
fizz status
CLI 0.2.0 can keep one WebSocket open (fizz run --stream), publish the same readings over MQTT (fizz run --mqtt or fizz send --mqtt), and print live readings for this device (fizz tail). HTTPS fizz run is unchanged. The installer selects the newest cli-v* GitHub release, not whichever release GitHub has marked Latest.
For your own deployment, set its origin when pairing:
FIZZ_API=https://fizz.example.com fizz pair
The CLI remembers that origin. The CLI guide covers supported architectures, source builds, configuration, systemd installation, and revoking a device.
Self-hosting
No clone and no compiler. Download the compose file, generate secrets, and start:
mkdir fizzlayer && cd fizzlayer
curl -fsSL https://raw.githubusercontent.com/fizzlayer/fizzlayer/main/deploy/compose.yml -o compose.yml
curl -fsSL https://raw.githubusercontent.com/fizzlayer/fizzlayer/main/deploy/compose.env.example -o .env.example
docker run --rm --user "$(id -u):$(id -g)" -v "$PWD:/out" fizzlayer/fizzlayer-api:latest init --out /out/.env
docker compose up -d
Open http://localhost:8080 and create an account. The self-hosting guide covers every .env variable, sending readings over HTTP, WebSocket, and MQTT 1883, HTTPS with Caddy, Supabase Cloud, backups, and logs. The same page is on the website at /self-host. Cloning the repo and docker compose -f deploy/docker-compose.yml up -d --build is the path for changing the server.
Images: fizzlayer/fizzlayer-api and fizzlayer/fizzlayer-worker. The same tags are on ghcr.io/fizzlayer/.
You can still deploy into your own Vercel and Supabase accounts. The api/*.rs entry points are the Vercel functions; the Docker server calls the same Rust handlers.
-
Clone the repository and install stable Rust, the Vercel CLI, and the Supabase CLI.
-
Create a Supabase project, link it, and apply the database migrations:
git clone https://github.com/nisargap/Fizz.git
cd Fizz
supabase login
supabase link --project-ref YOUR_PROJECT_REF
supabase db push --linked
-
Import the repository into Vercel using the Other framework preset and the repository root. Set SUPABASE_URL and SUPABASE_SERVICE_ROLE_KEY as server-side environment variables.
-
Configure Supabase Auth, email delivery, and redirects for your deployment's domain. Deploy the app and verify that /api/status reports database: "connected".
-
Open /app.html on your deployment and create your first account. Anyone who can reach the deployment can sign up; to close a private instance afterwards, run update public.fizz_instance_settings set sign_up_open = false; in the Supabase SQL editor.
Every account is a customer account; there is no separate administrator role. Keep the service-role key on the server and out of browser assets.
여기까지가 README 앞부분입니다. 나머지는 원문에서 읽을 수 있습니다. README 전문 보기 ↗
