FRAME ANALYTICS

Live hardware demo

One command. One Controller. One LED.

Enter led.on(). The site sends one signed AMQP message to the fixed destination website Controller. The webcam shows whether the physical device responded.

EXACT ALLOWLISTCSRFRATE LIMITEDHMAC SIGNED15-SECOND EXPIRY
BROWSER
RABBITMQ
RASPBERRY PI
FRAME // COMMAND TERMINALARMED

system Public command surface initialized.

target website Controller

allowlist led.on()

authority publish one typed operation

Only the exact command led.on() is accepted. Whitespace around it is ignored.

This is not a remote shell.

The server rejects every other command and never accepts a browser-selected Controller, exchange, queue, routing key, GPIO pin, operation, or argument.

LIVE CAMERAConnecting
Live camera view of the Raspberry Pi demonstration LED
DEVICEwebsite Controller

Physical verification: a queued response proves RabbitMQ accepted the message. The camera is what shows whether the LED actually changed state.

What happens when you press Run

A deliberately narrow control path.

The useful point is not that an LED can turn on. It is that a public request can traverse browser, application, broker, edge validation, and GPIO without becoming arbitrary remote code execution.

  1. 01

    Validate

    Check CSRF, request size, exact command text, per-client quota, and global cooldown.

  2. 02

    Sign

    Create a short-lived HMAC-signed message with a unique command ID and fixed target.

  3. 03

    Publish

    Send only to the durable website Controller queue and require broker publisher confirmation.

  4. 04

    Verify and actuate

    The Pi checks target, signature, expiry, replay state, and operation before touching GPIO.

Read the demo documentation