Feocey / DejaOS vs SALTO: Four-layer Open Platform Comparison

In one sentence

SALTO opens at the cloud business layer: via its own hardware and access SaaS, it exposes access-management APIs to third-party enterprise systems.

Feocey / DejaOS opens hierarchically from device to cloud: developers can build apps on the device, connect via MQTT to the standard access app, use Feocey Office SaaS directly, or integrate the SaaS into their systems via Web API.

Feocey / DejaOS four-layer open model

Device layer: devices run DejaOS; developers write different apps on-device in JavaScript, calling face, NFC, QR, GPIO, UI, HTTP, MQTT, SQLite and more.

Protocol layer: standard access App + MQTT. Devices ship with the standard access app exposing an MQTT interface; third parties connect without building a device app.

Application layer: Feocey Office SaaS. Small businesses add devices directly and use standard access, attendance, people management and basic reports.

Platform layer: SaaS Web API. Large enterprises manage people, devices, rights, credentials and records via the Feocey Office Web API, making access part of their own system.

Four-layer comparison

Layer 1 device: devices embed DejaOS; developers write device apps in JavaScript calling face/NFC/QR. SALTO centers on its own/certified hardware, not device-end development.

Layer 2 protocol: Feocey / DejaOS standard access App + MQTT lets third parties connect without device-end code; SALTO mainly integrates cloud APIs with enterprise/PMS/visitor/building systems.

Layer 3 application: Feocey Office SaaS offers access/attendance/people/reports; SALTO offers KS / Space / Homelok cloud or platform access management.

Layer 4 platform: Feocey Office Web API manages people/devices/rights/credentials/records; SALTO exposes users/doors/rights/credentials/events via Connect API / Core API.

Feocey strengths and gaps

Strengths: deeper openness — not just cloud APIs but from the device-end DejaOS, so developers write device apps directly; more adaptation paths — self-built app, MQTT connect, direct SaaS, or SaaS Web API integration.

Gaps: hardware and industry ecosystem — SALTO is more mature in lock categories, installers, integrators, certified partners and cases; SaaS credibility — large customers focus on stability, multi-site, multi-tenant, audit, compliance, DR and SLA.

Final positioning

Feocey should not only claim "we also have SaaS and APIs", which falls into SALTO existing frame. Better: SALTO lets third-party systems connect to an access platform; Feocey / DejaOS lets third-party developers define access apps from device to cloud, layer by layer. That is the key differentiation from traditional access SaaS vendors.

Note: this is an internal strategy and positioning discussion draft. SALTO-related descriptions are based on public information and product understanding; specific partnerships, hardware certification and API rights follow SALTO official policy.