What works.
What doesn't.
Yet.

Plenty of platforms describe features that exist only in a slide deck. This page is the corrective: three lists, plainly labelled, so you can tell what you'd actually be building on today.

Working — running on deployed hardware In progress — actively being built Planned — designed, not started
01 / Working today

Running on
real devices.

These aren't demos. They are in production on deployed hardware, which is why the rest of the platform is being built the way it is.

ArdaPlayer runtime

Single Go binary, WebKit surface, full-screen kiosk operation on x86-64 Debian systems, restarting cleanly after power loss.

Working

Encrypted packaging

Signed, AES-GCM encrypted .arda bundles verified and decrypted at load, with device binding.

Working

Control channel

Persistent outbound WebSocket with backoff reconnect, heartbeat, presence tracking and command routing.

Working

Encrypted local store

Hardware-bound key/value database plus a durable outbound queue with at-least-once delivery and server acknowledgement.

Working

Sync profiles

Versioned pull profiles with delta gating, plus binary asset delivery cached to disk for offline operation.

Working

Remote console

Console capture, live JavaScript evaluation, DOM read, single screenshots and change-triggered screen streaming.

Working

Reverse shell tunnel

Operator-initiated, token-authorised SSH to a device behind NAT, multiplexed over its existing outbound socket.

Working

Device telemetry

Distribution, kernel, architecture, CPU, memory, disk, GPU, network interfaces and classified USB inventory on every connect.

Working

Updates

Hash-verified package staging and signature-verified runtime binary replacement with atomic swap, rollback copy and re-exec.

Working

ArdaLive for VS Code

Live HTML preview for the authoring loop — DOM-patched in place, so scroll position, focus and JS state survive every edit. A separate free extension, not part of the platform, and useful whether or not you ever ship a device.

02 / In progress

Being built
right now.

Designed, partly implemented, and moving. These are what early access exists to get feedback on.

ItemStateWhat's left
Public portalIn progressAccount sign-up, fleet views, release management and the operator surface. The internal control panel works; the public one is being built on top of it.
arda CLIIn progressCommand surface is drafted and the device-side half is done. Finalising names, flags and the auth flow alongside the portal.
Printer APIsIn progressUSB thermal printing works today. Generalising discovery, adding standard Linux print paths and real status reporting — paper-out and offline detection need per-printer protocol queries.
GPIO APIsIn progressAPI shape settled. Raspberry Pi support first, then wider board coverage, PWM and interrupt-driven watches.
Camera & QRIn progressCapture and code scanning under active development. Multi-camera selection after that.
Wi-Fi managementIn progressStatus and interface reporting work. Scan, join and secure credential storage are being added.
ARM64 buildsIn progressRuntime builds for ARM64 and Raspberry Pi, with the peripheral matrix tested per board.
API documentationIn progressReference pages are published and will firm up as each API group locks down.
03 / Planned

Designed,
not started.

On the list, thought through, not yet written. Ordering here is genuinely influenced by what early access users ask for.

USB installer image

Debian-based whole-device provisioning with device profiles, so bare hardware becomes a registered appliance in one boot.

Planned

Device simulator

Run and debug an ArdaForm application on your workstation against a simulated device, including fake printers and GPIO.

Planned

Local face matching

On-device detection, enrolment and matching for attendance and identity confirmation, with templates that never leave the hardware.

Planned

Audio APIs

Prompts, chimes, volume and output selection for queue displays and accessibility.

Planned

Peripheral modules

Optional drop-in modules for scales, payment terminals, NFC readers and label printers.

Planned

Fleet alerting

Rules over telemetry — device offline, disk filling, printer down, queue backing up — routed to email, webhook or chat.

Planned

Team accounts

Multiple operators per fleet with roles, scoped tokens and an audit trail of who did what to which device.

Planned

Self-hosted control plane

Run the control plane inside your own infrastructure for customers whose procurement rules require it.

Planned
!
No dates You'll notice there are none. ArdaForm is being built by a small team alongside real deployments, and a date we'd have to walk back is worth less than a list you can trust. Anything marked Working you can hold us to today.
Influence it

Tell us what
you need first.

The ordering of the planned list is not fixed. If your product is blocked on one specific thing, say so — it moves.