Open Protocol · Apache 2.0

AI speaks in goals.
Devices speak in
commands.
DoSync is the bridge.

An open communication protocol that lets AI agents interact with physical devices using semantic intent — no hardcoded rules, no manual configuration per device.

32/32certification tests
2implementations
<100msintent to action
Apache 2.0open source

Existing protocols

lock.unlock()
light.set_brightness(100)
thermostat.set_temperature(21)
// hardcoded, per-device, per-scenario

DoSync

"there is an emergency at home"
"nobody is home — save energy"
"good morning"
// every device resolves its own role

Architecture

Five layers. One semantic bridge.

DoSync is a 5-layer protocol stack. Each layer has a single responsibility and doesn't need to know how the others work.

Layer 5

Intent

AI expresses semantic goals

Layer 4

Semantic

Resolver maps intent → device actions

Layer 3

Registry

Devices self-declare capabilities on join

Layer 2

Security

mTLS, local PKI — no internet required

Layer 1

Transport

WiFi · BLE · Zigbee · Z-Wave · Thread

Demo

From natural language to physical action.

A conversation with Claude AI triggers a physical emergency protocol in real time — 10 Philips WiZ bulbs, SMS notification, audit log. No commands. No rules. No cloud.

user → "there is an emergency at home"
# DoSync hub receives intent
# ensure_safety [emergency]
wiz-living1-01 turn_on brightness=100 ✓
wiz-living1-02 turn_on brightness=100 ✓
wiz-living2-01 turn_on brightness=100 ✓
alarm-test-01 alarm pattern=emergency ✓
notifier-sms-01 notify → +543513... ✓
# 18 actions · 5 devices · 79ms
# audit log updated · SHA-256 chain intact
Watch the demo — 2 min

Raspberry Pi 5 running the hub autonomously · 10 Philips WiZ bulbs via UDP · SMS via Twilio · zero internet dependency

Quick start

Up and running in three commands.

No hardware required. The Docker demo starts the hub and registers 8 simulated devices automatically.

1 Clone the repo
$ git clone https://github.com/
  giulianireg-spec/dosync-protocol
2 Start with Docker
$ cd dosync-protocol
$ docker compose up
3 Open the dashboard
open http://localhost:47200
# hub · devices · audit log

Use cases

Not just for the home.

The same 5-layer stack works anywhere an AI needs to coordinate physical systems.

🏠

Smart home

Emergencies, routines, energy efficiency — orchestrated by intent, not rules.

🛒

Retail store

Cold chain failure at 3am → manager notified, sector locked, maintenance dispatched — before products are lost.

🏨

Hotel

"Guest in 412 has arrived" → room configured to saved preferences, no configuration needed.

🏭

Factory

"Line B failure" → safe shutdown, notifications, tamper-evident audit trail.

Certification

Self-certify your device in minutes.

Three tiers, self-certifiable with the CLI. No manual approval required for Basic and Standard.

Basic

DoSync Basic

Layers 1–3: connectivity, authentication, capability manifest.

  • Connects and authenticates
  • Publishes capability manifest
  • Appears in device registry
Standard

DoSync Standard

Layers 1–4: intent response, events, health reporting.

  • Responds to all intent classes
  • Sends events to the hub
  • Passes explainability checks
Emergency

DoSync Emergency

All layers + emergency override + tamper-evident audit log.

  • Emergency override without confirmation
  • SHA-256 chained audit log
  • mTLS per-device authentication
$ python3 certify.py --host <device-ip> --port 47200 --tier emergency
# generates dosync-cert.json — signed certification report

Project status

Honest about where we are.

v0.3 — reference implementation. Apache 2.0. One person building it. Here's what's real today.

DoneREST API · WebSocket · Dashboard
DoneCertification CLI — 32/32 tests
DonePhilips WiZ adapter (UDP local)
DoneHome Assistant bridge (10 domains)
DoneNative MCP server (Claude, any LLM)
DoneLocal PKI + mTLS per-device auth
DoneRaspberry Pi 5 — autonomous 24/7
Donedosync-node — Node.js implementation
In progressDistributed state — multi-hub
PlannedBLE transport adapter
PlannedThird-party device certifications

Roadmap

Q2 2026 Distributed state multi-hub · benchmark under concurrent load · penetration testing
Q3 2026 Second independent implementation · BLE transport · first external device certification
Q4 2026 IEEE WF-IoT 2026 paper · outreach to device manufacturers · dosync.dev v2
2027+ FamilyOS integration · DoSync as native protocol in commercial devices