Cross-device ecosystem · TitanShare

Your devices.One localworkspace.

Zero-configuration discovery, peer-to-peer file transfer, remote monitoring and secure controls between ArchTitan Linux and Android.

Explore TitanShare ↓See the protocol
ARCHTITAN / LINUXworkstation-01 Available192.168.1.24
LOCAL P2P12.4 MB/s
ANDROID / MOBILEKaveesha's phone Paired192.168.1.41
project-build.tar.zst74%
1.28 GB / 1.72 GB00:31 remaining
C++ serviceKotlin clientTCP transportmDNS discovery

01 / Capabilities

Local-first by design.
Useful by default.

TitanShare turns nearby devices into a coherent developer environment without routing local work through a cloud service.
01

Zero-config discovery

Linux and Android peers announce themselves over mDNS and appear without accounts or manual IP entry.

Native capability ↗
02

Direct file transfer

Files move peer-to-peer across the local network with streaming I/O, progress reporting and integrity checks.

Native capability ↗
03

Remote telemetry

View CPU, memory, thermal and workload signals from the ArchTitan machine on Android.

Native capability ↗
04

Remote controls

Trigger approved system actions through a small, explicit command surface with device-level trust.

Native capability ↗

02 / Connection lifecycle

From nearby peer
to verified transfer.

A small protocol keeps discovery fast, pairing explicit and data movement observable.
  1. 01DISCOVER_titanshare._tcp.local

    mDNS advertises an available ArchTitan peer.

  2. 02PAIRephemeral challenge

    Both devices confirm identity on the local network.

  3. 03NEGOTIATEcapability manifest

    Peers agree on transfer and control capabilities.

  4. 04TRANSFERchunked TCP stream

    Data moves directly with progress and verification.

03 / System architecture

Native at
both ends.

The desktop service owns discovery, transfer and system integration. The Android client provides a focused mobile interface for files, telemetry and controls.
04ExperienceSend · Receive · Monitor · ControlAndroid + Linux UI
03SessionPairing · Capabilities · Progress · RecoveryTitanShare protocol
02TransportChunked streams · Checksums · BackpressureTCP
01DiscoveryService announcement · Peer presencemDNS

04 / Trust model

Nearby does not mean trusted.

01

Explicit pairing

A discovered device receives no privileged capability until both endpoints confirm the pairing.

02

Scoped permissions

File transfer, telemetry and remote controls are negotiated as separate capabilities.

03

Local transport

Traffic stays on the local network and does not depend on an external relay or account.