Zero-Dependency Single Binary Architecture
Many modern orchestrators require Node.js runtimes, Python virtual environments, Redis message brokers, or heavy Docker containers just to expose a dashboard or coordinate periodic sync tasks.
Bisync Hub is distributed as a single statically compiled Go binary with zero external runtime dependencies.
Architectural Principles
┌──────────────────────────────────────────────────────────────┐
│ bisync-hub executable │
│ │
│ [ Go 1.24 Runtime ] │
│ ├── Sync Orchestrator & Rclone RC Client │
│ ├── Multi-Analyzer Heuristic Engine │
│ ├── SQLite Engine & POSIX Flock Locks │
│ └── Embedded Web Assets (go:embed) │
│ ├── Tailwind CSS & Alpine.js Dashboard │
│ └── Static HTML & WebSocket Handlers │
└──────────────────────────────────────────────────────────────┘
1. go:embed Frontend Architecture
The complete interactive management dashboard—including Alpine.js components, Tailwind CSS styling, Chart.js telemetry graphs, and WebSocket listeners—is embedded directly into the binary at compile time.
- No
node_modulesdirectory in production. - No external npm CDN requests; runs 100% offline in air-gapped data centers.
- Instant startup (< 15ms) with sub-30MB memory footprint.
For a full visual tour of all dashboard modules and modals, visit the UI Gallery.
2. POSIX Flocking & Atomic File Writes
Process concurrency and state isolation rely entirely on OS-native POSIX advisory locks (syscall.Flock).
- Zero reliance on external lock daemons (Redis / Zookeeper).
- State persistence and telemetry use atomic rename semantics (
.tmp.<pid>+os.Rename) to prevent half-written files during sudden power loss or server restarts.
3. Multi-Platform Cross-Compilation
Compiles cleanly across modern platforms with standard Go tooling:
linux/amd64(Standard servers & workstations)linux/arm64(Raspberry Pi, AWS Graviton, Apple Silicon Linux VMs)darwin/amd64&darwin/arm64(macOS workstations)
You can deploy Bisync Hub to an edge Raspberry Pi, a corporate Linux server, or a NAS box with a single
scpcommand.