Architecture Direction

Customer-Owned Data Plane

Customer operational field data should not need to live in a vendor-controlled SaaS database for the system to work.

ARCHITECTURE DIRECTION

Not all layers shown here are available in the current Fenwix mobile release. This page describes the target Business / Enterprise architecture.

Target architecture

FIELD CLIENT
- Local DB
- Evidence
- Workflow
- PDF
- Verification
        ↕
FIELD DATA PROTOCOL
        ↕
STORAGE ABSTRACTION
        ↕
CUSTOMER-CONTROLLED STORAGE
        ↕ optional
CUSTOMER RELAY
        ↕
CUSTOMER SYSTEMS

Every layer sits outside a vendor data plane. Fenwix keeps a control plane licensing, updates, content-free telemetry, while the customer's field records live in storage the customer controls.

Why this matters

Inspection records are operational and often sensitive: sites, defects, people's signatures, timestamps. The default industry model routes all of it into the vendor's database because that is convenient for the vendor. Fenwix's architecture direction treats that convenience as a liability to design out: collaboration rides on the customer's own storage, and the platform is the data protocol rather than the vendor's database.