Skip to main content
Products
Software ProductPilotComing SoonPartially Implemented

FcXe Drive

Organization-controlled file access with an evolving synchronization layer.

FcXe Drive combines an existing server-file-access pilot with v2 synchronization-engine work. The current pilot and incomplete v2 work are disclosed separately.

Public delivery, public access, licensing, support commitments, and commercialization remain inactive.

Discuss a Related Project

Illustrative synthetic data — not a live deployment.

Product Fact Sheet

Summary facts

  • Primary storageDocumented
    Organization-controlled server-side storage
  • Broad compatibilityPending
    Unverified
  • CommerceDocumented
    Disabled

Overview

Keep primary file storage controlled while synchronization evolves.

The current pilot provides organization-controlled server-side storage through a mapped-drive and server-file-access model with administration tooling. A v2 Share, device, and cursor architecture and synchronization-engine work exist, but broader integration remains incomplete.

Use and audience

Current use cases and intended users

Primary use cases

  • Mapped-drive and server-file access
  • Administration and existing-share preservation
  • Development of two-way synchronization workflows

Intended users

  • Owner-controlled organizations evaluating self-hosted file workflows
  • Administrators of bounded server-file-access environments

Current scope

Documented capabilities

Implemented / Established Now

Documented
  • Mapped-drive and server-file-access pilot
  • Administration tooling
  • Existing-share preservation with bounded pilot evidence

Implemented — Verification Pending

Provisional
  • Two-way synchronization engine work
  • Engine-level conflict-preservation behavior

In Development

Pending
  • v2 Share, device, and cursor integration
  • Background automatic synchronization
  • Consolidated desktop UX

Parked

Pending
  • Commercial website, licensing, public distribution, support commitments, and commercialization under L17

Technical context

Requirements, compatibility, and data behavior

Requirements

  • Server environmentDocumented

    Organization-controlled and pilot-specific

Compatibility

  • Broader Windows/server coveragePending

    Unverified

Data behavior

  • Application-layer transportPending

    T5.1 remediation remains open

Not current capability

Roadmap

These items remain roadmap items and are separate from documented current scope.

  • Complete v2 integration, automatic synchronization, desktop UX, compatibility verification, and T5.1 remediation.

Scope boundary

Out of scope

  • Backup or disaster recovery
  • Universal compatibility or public commercial access

Current boundaries

Current limitations

  • v2 integration, background synchronization, and consolidated desktop UX are incomplete.
  • Broader compatibility and Product-level transport security are unverified.
  • FcXe Drive is not backup or disaster recovery.

Operational state

Availability and maturity

Bounded pilot evidence exists, while v2 integration, automatic background synchronization, consolidated desktop UX, broad compatibility, and T5.1 remediation remain incomplete.

  • DeliveryDocumented
    Public delivery is inactive
  • LicensePending
    Not established
  • SupportDocumented
    Not active
  • AccessDocumented
    Not Available
  • Production readinessPending
    Not established
  • CommerceDocumented
    Disabled

Governed notices

Important qualifications

Reserved visual evidence

Illustrative Product views

These governed positions are illustrative placeholders. They are not evidence of deployment, availability, compatibility, or production readiness.

  • Synthetic pilot workflow

    Provisional

    Synthetic folders, shares, paths, and devices illustrating a bounded pilot workflow.

    Illustrative synthetic data