Skip to content
Fenwix
TRVisit Fenwix.app

Enterprise direction

Enterprise field inspection architecture

Fenwix enterprise architecture is a staged direction, not a currently available enterprise suite. Today's Solo product provides offline local records, evidence context, revisions and reports. The next layer targets a customer-owned data plane; organization policy, RBAC, SSO, relay services and regulated deployment controls come later.

Enterprise architecture map for identity, policy, storage connectors and a customer relay around field records.
ARCHITECTURE DIRECTION

This page describes a layered target architecture. Only capabilities marked current are available in the Solo product; no enterprise plan, workspace or integration is being offered as production-ready here.

CURRENT, SCOPED

Current foundation

Offline field record, local evidence, report identity and scoped verification.

ROADMAP

Next data plane

Encrypted local surfaces and customer-controlled synchronization through a versioned protocol.

ENTERPRISE ROADMAP

Enterprise control plane

Organization policy, role authorization, identity federation, relay and governance.

Architecture flow

CURRENT SOLO FOUNDATION
          ↓
CUSTOMER-OWNED DATA PLANE
          ↓
ORGANIZATION POLICY + RBAC
          ↓ optional
CUSTOMER RELAY + ENTERPRISE SYSTEMS

Layer 1: What exists in the current Solo foundation?

CURRENT, SCOPED

The current product is an Android, local-first inspection workflow. It creates structured inspection records, keeps evidence context, follows findings and corrective action, generates PDF reports and performs supported verification from the local source record.

  • Offline-first core workflow
  • App-private local operational data
  • Checklist, finding, evidence and corrective-action records
  • Report number and controlled revision
  • No required Fenwix account for core use
  • No shared enterprise workspace

Layer 2: What must the Customer-Owned Data Plane add?

ROADMAP

The next architecture layer must synchronize authorized devices without making Fenwix the default owner of shared inspection content. It requires protocol identity, encrypted local storage, portable bundles, provider-neutral connectors, explicit conflict handling and tested recovery.

  • Stable record and evidence identities
  • Version-aware Field Data Protocol
  • Customer-controlled repository
  • Resumable and idempotent transfer
  • Explicit offline conflict and branch semantics
  • Entitlement rules that do not erase historical access

Layer 3: What belongs to enterprise governance?

ENTERPRISE ROADMAP

Team operation introduces authorization and policy questions that storage access controls alone cannot answer. Organization identity, role boundaries, approval, template governance, retention, trusted time and audit export require a distinct control model.

  • Organization and workspace model
  • RBAC and separation of duties
  • SSO and lifecycle provisioning
  • Controlled template distribution and multilingual governance
  • Retention and legal-hold policy
  • Actor-grade audit history and export

Layer 4: Where does Customer Relay fit?

LONG-TERM

An optional Customer Relay can provide policy distribution, credential brokering, event integration and controlled connection to customer systems while operational content remains in the customer's data plane. It is not a backdoor vendor repository.

  • Optional deployment component
  • Customer-network integration boundary
  • Content-minimized vendor control plane
  • Explicit support and diagnostic access
  • No current production service claim

What should an enterprise buyer verify today?

Evaluate the current Solo product only for current needs, and treat each later layer as a gated architecture proposal. A future-state diagram should never substitute for an implemented security review, data-flow test, recovery exercise or contract.

  • Which marked capabilities can be demonstrated now?
  • What customer content reaches Fenwix infrastructure?
  • What fails when the vendor or provider is unavailable?
  • Which component owns identity, encryption keys and retention?
  • What must be completed before a pilot can start?

Frequently asked questions

Does Fenwix offer an enterprise workspace today?

No. The current product is Solo and local-first; shared enterprise workspace capabilities are roadmap scope.

Are RBAC, SSO or SCIM currently available?

No. They belong to the enterprise governance direction and are not current product claims.

Will Fenwix store shared inspection content?

The target Zero-Custody direction places operational content in customer-controlled storage rather than a default Fenwix repository.

Is Customer Relay required?

The planned relay is optional and intended for deployments that need customer-network policy or integration services.

Can an organization pilot the architecture now?

No production-ready enterprise pilot is claimed. Required identity, encryption, protocol, connector and recovery gates must be implemented first.

Related architecture and product surfaces

Zero-Custody architecture →Customer-Owned Data Plane →Storage architecture →Security approach →Connector roadmap →

Buy the current layer; evaluate future layers as gates

Use the current Solo workflow for what it demonstrably does. Require implementation evidence, security review and recovery tests before treating any enterprise architecture layer as deployable.

Evaluate the current Solo field app →

Content status: ARCHITECTURE_DIRECTION · Last reviewed: 2026-08-16

Claim basis: Fenwix Zero-Custody master plan · Fenwix product decision record · Fenwix.net aligned master brief