Architecture
A commissioned control core, deployed inside the client network — governed by policy, audited by design.
Control Core
Vœrynth runs on a hardened on-prem control core deployed inside the client network. It is designed as infrastructure: stable, inspectable, and commissioned — not consumer automation.
Not a PLC runtime
Vœrynth does not require a PLC runtime. Where PLCs already exist (e.g., vendor machinery or legacy subsystems), Vœrynth integrates at the boundary via standard interfaces — without replacing safety-critical logic.
Local-first operation
Core control does not require internet access. The system remains operational in local-only conditions, with explicit degraded-mode behavior and recovery procedures.
Certified deployments
Only validated hardware and tested release builds are commissioned into production environments. This reduces breakage, limits drift, and keeps long-lived systems maintainable.
The Control Path
Every actuation follows a single, auditable path — so “clever” never bypasses “safe.”
Interface issues an intent
(owner / staff / engineering)
Policy Gate authorizes or denies
based on role, state, and invariants
Translation Layer maps intent
to protocol-safe actions (wired, mesh, and telemetry interfaces)
Devices execute
results return to state
Audit Ledger records
the full chain with correlation IDs
Muted note: No direct device control from the UI. No silent bypasses.
Core Layers
Vœrynth is layered so hardware churn and protocol differences do not ripple into operations.
A restrained operator interface with role-safe surfaces: owner, staff, and engineering are not the same user.
A deterministic authorization boundary. It decides what is allowed, when, and by whom — before any action reaches the environment.
An explicit model of the environment: modes, invariants, and transitions. Automation is based on declared state — not assumptions.
Protocol adapters and normalization. Devices are integrated without leaking protocol complexity into the operator experience.
Field hardware and gateways commissioned as a system: validated topologies, known failure modes, defined replacement procedures.
Operational Guarantees
- Internet is not required for core control.
- All actuation is routed through a single policy boundary.
- Role-based access is enforced by design.
- Commissioning includes offline, degraded-mode, and recovery acceptance tests.
- Updates are controlled, validated, and rollback-capable.
- Hardware in production is curated and version-pinned.
Guarantees apply to the commissioned scope and validated hardware set.
Common Questions
Does Vœrynth run on PLCs?
No. Vœrynth runs on a hardened on-prem control core. Where PLCs exist, Vœrynth integrates at the boundary without replacing safety-critical logic.
Is this a smart-home hub?
No. Vœrynth is commissioned infrastructure for complex environments. It prioritizes stability, auditability, and operational clarity over novelty.
Do you need cloud services?
Core control is local-first and does not require cloud connectivity. Optional external services, if used, are explicit and isolated — never a hidden dependency.
What happens when something fails?
The system is designed with fault domains. When a subsystem fails, affected functions degrade predictably while the rest remains stable. Recovery procedures are part of commissioning.
Ready for a commissioned pilot?
If you’re evaluating a residence, estate, yacht, or facility, we can scope a pilot with measured outcomes, acceptance tests, and a clean handover package.