APPLICATIONSPOS · Admin · Partner API
OPEN ARCHITECTURE FOR THE LAUNDRY INDUSTRY
The laundromat should be defined by software — not limited by hardware.
SDL is an open architecture for connecting machines, payments, controllers, sensors and operational software through one shared model.
CONTROL PLANERegistry · Commands · Events
SDL EDGELocal state · Safety · Offline
ADAPTERSModbus · GPIO · UART · MQTT
PHYSICAL ASSETSWashers · Dryers · Pumps
STANDARD COMMAND
start_cycle → machine.d2hardware mapping stays localHARDWARE-AGNOSTIC LOCAL-FIRST CAPABILITY-BASED EVENT-DRIVEN EXTENSIBLE OBSERVABLE
THE CORE IDEA
Applications communicate with laundromat capabilities — not relay channels.
SDL separates customer-facing software from machine-specific protocols. A POS asks to start a cycle. The local SDL runtime decides how that request is safely executed on the installed hardware.
Read the plain-language introduction →HARDWARE-COUPLED
Implementation detail leaks upward
set output_channel = 4
set output_state = LOW
wait 30 milliseconds
restore output_stateThe application becomes dependent on a specific controller and wiring layout.
→
SOFTWARE-DEFINED
Intent remains stable
{{
"command": "start_cycle",
"target": "machine.d2",
"duration_minutes": 30
}}The edge and adapter translate intent into the correct physical action.
WHY NOW
The industry is becoming software-dependent without a common software model.
SDL creates a shared boundary between applications and physical laundry infrastructure.
Reduce hardware coupling
Replace controllers, protocols or boards without rebuilding every application.
Operate locally
Keep essential site functions available during temporary cloud or Internet failure.
Integrate consistently
Connect payments, machines, pumps and software through clear capabilities and events.
Build an ecosystem
Allow manufacturers and developers to participate at the layer they understand best.
FIVE-LAYER MODEL
A clean boundary from application intent to physical action.
The phase-one architecture explains responsibility, not a mandatory technology stack. Layers may be deployed in the cloud, locally or as a hybrid.
Open Architecture Overview- 01ApplicationsBusiness and user experiences
- 02Control PlaneRegistry, commands and shared state
- 03SDL Edge RuntimeLocal execution, safety and continuity
- 04Device AdaptersHardware and protocol translation
- 05Physical InfrastructureMachines and supporting equipment
PHASE 1 PUBLICATION
A focused set of documents for understanding and discussion.
These documents explain the direction of SDL before the project publishes detailed protocol specifications or software APIs.
START HERE
What is SDL?
A plain-language introduction to the idea and its value.
5 min read → CONTEXTWhy SDL?
The fragmentation and operational problems the project addresses.
7 min read → TECHNICALArchitecture Overview
The five layers, local-first execution and adapter boundary.
12 min read → FOUNDATIONDesign Principles
The rules used to evaluate future SDL decisions.
9 min read → PROJECTProject Charter
Vision, scope, non-goals and relationship with SkyWash.
8 min read → DIRECTIONPublic Roadmap
What is current, next and intentionally deferred.
5 min read →REFERENCE EXPERIENCE
Initiated from real laundromat operations in Vietnam.
SDL is initiated by SkyWash and informed by practical experience connecting commercial machines, controllers, payments, local POS systems, detergent pumps and remote operations across a growing network of 29 laundromat locations.
SkyWash is the first reference environment. SDL is designed so other technology providers can implement the same architecture independently.
JOIN THE DISCUSSION
Help shape a more interoperable technology layer for laundromats.
We welcome feedback from machine manufacturers, hardware developers, payment providers, software companies and system integrators.