OneBoxN
Native interface. Our own core.
OneBoxN is a commercial client developed by OneOh Cloud LLC. N stands for Native: each Windows, macOS, Android, and iOS version uses its platform’s native components.
OneBoxN is now available, with native interfaces and our own Rust network core.
Native architecture
Rust 1.97.0 / obox
Platform-native components power the interface, while obox, our network core written in Rust, handles networking. Designing the client and core together reduces architectural layers and bridging between technology stacks. OneBoxN uses a proprietary, non-open-source commercial license.
Download signed packages
The latest officially signed package for each platform. Verify the file with its SHA-256 after downloading.
Android
Google-signed APK
- Version
- 0.2.0
- Build
- 131
- Size
- 35.6 MB
SHA-256
f7d6dd5dc6debc02a5c707f0f880a66cae71682822e051c4cd73ac834a53c8f4
macOS
Notarized Developer ID DMG
- Version
- 0.2.0
- Build
- 131
- Size
- 71.4 MB
SHA-256
1ea977704b2d1b76736735c6d3d3178986106aaa7a7707396082dcb635911172
Windows
MSIX signed with Azure Trusted Signing
- Version
- 0.2.0
- Build
- 131
- Size
- 25.8 MB
SHA-256
b3b62d7173838fd009e2eaa79c4bcfa9ea79a8260f9ba2e896c5d2c16754fe3b
Native on every platform.
Each platform uses its own language, interface framework, and system networking APIs, powered by the same Rust obox core.
Windows
C# 14 · .NET 10 · WPF
.NET SDK 10.0.401 · Runtime 10.0.12 · WPF-UI 4.3.0
Native desktop interface
C# and WPF power the desktop interface, with layouts defined in XAML and Fluent styling through WPF-UI components. Windows, keyboard interactions, and the system tray integrate with the Windows desktop.
System service and core
A separate Windows service hosts the network tunnel independently of the interface process. C# calls obox’s native library through P/Invoke to connect to the Rust network core.
macOS
Swift 6.0 · SwiftUI · AppKit
Swift 6.0 language mode; SwiftUI and AppKit are provided by Apple’s platform SDK.
Native Mac experience
Swift and SwiftUI build the interface, while AppKit connects desktop windows, the menu bar, and system interactions. The interface works with macOS window management, appearance, and interaction conventions.
System network extension
NetworkExtension and a Packet Tunnel extension integrate the tunnel with macOS. Swift bindings connect system networking to the Rust obox core, with separate responsibilities for the interface and tunnel.
Android
Kotlin 2.4.10 · Jetpack Compose · Material 3
Compose UI 1.11.4 · Material 3 1.4.0 · Compose BOM 2026.06.01
Native Android interface
Kotlin and Jetpack Compose build a declarative interface with Material 3 components. ViewModel and Kotlin coroutines manage interface state and asynchronous tasks alongside the Android lifecycle.
System VPN service
Android VpnService integrates with the system VPN and tunnel interfaces. Kotlin calls obox through UniFFI-generated native bindings, connecting Android services with the Rust network core.
iOS
Swift 6.0 · SwiftUI · UIKit
Swift 6.0 language mode; SwiftUI and UIKit are provided by Apple’s platform SDK.
Native iPhone interface
Swift and SwiftUI build the interface, with UIKit integration for system capabilities such as camera previews and the clipboard. Apple’s native components handle platform interactions.
System tunnel extension
NetworkExtension’s NEPacketTunnelProvider hosts the network tunnel separately from the app interface. Native Swift bindings connect to obox, while the system VPN framework coordinates connection state and the tunnel lifecycle.
Performance benchmarks
End-to-end Linux network-core benchmarks, excluding the client interface.
| Protocol | obox → obox | sing-box → sing-box |
|---|---|---|
| Shadowsocks · obox client to obox server link wins 38.94% | 13545.02 | 9748.57 |
| VLESS · obox client to obox server link wins 2.97% | 24841.66 | 24125.75 |
| AnyTLS/REALITY · obox client to obox server link wins 26.30% | 14318.83 | 11337.45 |
| Protocol | obox → obox | sing-box → sing-box |
|---|---|---|
| TUIC · obox client to obox server link wins 31.44% | 3595.22 | 2735.31 |
| Hysteria2 · obox client to obox server link wins 37.26% | 3699.48 | 2695.33 |
| Protocol | obox → obox | sing-box → sing-box |
|---|---|---|
| Shadowsocks · obox client to obox server link wins 55.51% | 25.21 | 56.67 |
| VLESS · obox client to obox server link wins 57.17% | 22.41 | 52.32 |
| TUIC · obox client to obox server link wins 51.64% | 32.03 | 66.23 |
| Hysteria2 · obox client to obox server link wins 76.00% | 31.99 | 133.32 |
| AnyTLS/REALITY · obox client to obox server link wins 49.54% | 33.48 | 66.36 |
| Protocol | obox → obox | sing-box → sing-box |
|---|---|---|
| Shadowsocks · obox client to obox server link wins 40.22% | 8947.38 | 6380.86 |
| VLESS · sing-box client to sing-box server link wins 17.22% | 19226.76 | 22538.10 |
| AnyTLS/REALITY · obox client to obox server link wins 24.07% | 9406.97 | 7582.08 |
| Protocol | obox → obox | sing-box → sing-box |
|---|---|---|
| TUIC · obox client to obox server link wins 24.23% | 2594.10 | 2088.20 |
| Hysteria2 · obox client to obox server link wins 51.37% | 2792.99 | 1845.10 |
AWS c6in.large · 16 streams · per direction 30s · sing-box 1.14.1
Comparison: obox as client, obox as server. Reference: sing-box as client, sing-box as server. Blue bars: comparison; gray bars: reference.
Goodput compares the complete link; memory and CPU efficiency measure the client process. Winner labels identify the link. Higher goodput and efficiency, or lower memory, wins. Percentages use the other link as the baseline. Peak memory covers both directions and does not change with direction.
Full data: all four client/server combinations
The client is left of the arrow; the server is right.
Shadowsocks
| Link | Direction | n | Mbps | Client Mbps/core | Server Mbps/core | Client MiB | Server MiB |
|---|---|---|---|---|---|---|---|
| obox → obox | download | 2 | 13545.02 | 8947.38 | 10715.81 | 25.21 | 24.55 |
| obox → obox | upload | 2 | 13539.46 | 11122.05 | 8905.86 | 25.21 | 24.55 |
| obox → sing-box | download | 2 | 11481.74 | 9109.48 | 7610.87 | 24.57 | 58.49 |
| obox → sing-box | upload | 2 | 8887.73 | 15627.30 | 5788.99 | 24.57 | 58.49 |
| sing-box → obox | download | 2 | 9142.92 | 5991.18 | 14429.90 | 56.48 | 23.83 |
| sing-box → obox | upload | 2 | 10963.38 | 7235.72 | 9470.00 | 56.48 | 23.83 |
| sing-box → sing-box | download | 2 | 9748.57 | 6380.86 | 11663.41 | 56.67 | 58.89 |
| sing-box → sing-box | upload | 2 | 10332.13 | 9183.15 | 6725.75 | 56.67 | 58.89 |
VLESS
| Link | Direction | n | Mbps | Client Mbps/core | Server Mbps/core | Client MiB | Server MiB |
|---|---|---|---|---|---|---|---|
| obox → obox | download | 2 | 24841.66 | 19226.76 | 71729.89 | 22.41 | 22.02 |
| obox → obox | upload | 2 | 24826.72 | 77418.12 | 20148.81 | 22.41 | 22.02 |
| obox → sing-box | download | 2 | 24394.15 | 25098.10 | 17563.42 | 22.56 | 70.38 |
| obox → sing-box | upload | 2 | 24826.97 | 76487.05 | 18242.44 | 22.56 | 70.38 |
| sing-box → obox | download | 2 | 24841.49 | 17433.17 | 69201.74 | 51.92 | 21.64 |
| sing-box → obox | upload | 2 | 24802.69 | 60955.10 | 19989.89 | 51.92 | 21.64 |
| sing-box → sing-box | download | 2 | 24125.75 | 22538.10 | 16975.31 | 52.32 | 70.81 |
| sing-box → sing-box | upload | 2 | 24827.36 | 65473.58 | 19479.81 | 52.32 | 70.81 |
TUIC
| Link | Direction | n | Mbps | Client Mbps/core | Server Mbps/core | Client MiB | Server MiB |
|---|---|---|---|---|---|---|---|
| obox → obox | download | 2 | 3595.22 | 2594.10 | 5425.75 | 32.03 | 31.84 |
| obox → obox | upload | 2 | 2893.95 | 3245.90 | 3981.54 | 32.03 | 31.84 |
| obox → sing-box | download | 2 | 3872.14 | 2768.01 | 3012.06 | 33.26 | 64.70 |
| obox → sing-box | upload | 2 | 2519.32 | 3269.26 | 1910.55 | 33.26 | 64.70 |
| sing-box → obox | download | 2 | 2531.07 | 2005.02 | 5383.85 | 65.14 | 33.58 |
| sing-box → obox | upload | 2 | 3717.77 | 3177.99 | 5135.69 | 65.14 | 33.58 |
| sing-box → sing-box | download | 2 | 2735.31 | 2088.20 | 2775.01 | 66.23 | 66.58 |
| sing-box → sing-box | upload | 2 | 2728.36 | 2865.04 | 2027.00 | 66.23 | 66.58 |
Hysteria2
| Link | Direction | n | Mbps | Client Mbps/core | Server Mbps/core | Client MiB | Server MiB |
|---|---|---|---|---|---|---|---|
| obox → obox | download | 2 | 3699.48 | 2792.99 | 5452.08 | 31.99 | 33.61 |
| obox → obox | upload | 2 | 3325.34 | 3394.58 | 4438.73 | 31.99 | 33.61 |
| obox → sing-box | download | 2 | 3973.44 | 2860.53 | 3193.24 | 34.14 | 68.32 |
| obox → sing-box | upload | 2 | 2611.81 | 3413.00 | 1987.22 | 34.14 | 68.32 |
| sing-box → obox | download | 2 | 2827.19 | 1970.96 | 5004.25 | 67.56 | 34.95 |
| sing-box → obox | upload | 2 | 3954.72 | 2992.48 | 4879.12 | 67.56 | 34.95 |
| sing-box → sing-box | download | 2 | 2695.33 | 1845.10 | 2277.75 | 133.32 | 162.23 |
| sing-box → sing-box | upload | 2 | 1767.56 | 1792.79 | 1295.62 | 133.32 | 162.23 |
AnyTLS/REALITY
| Link | Direction | n | Mbps | Client Mbps/core | Server Mbps/core | Client MiB | Server MiB |
|---|---|---|---|---|---|---|---|
| obox → obox | download | 2 | 14318.83 | 9406.97 | 10838.54 | 33.48 | 27.17 |
| obox → obox | upload | 2 | 14523.04 | 10119.19 | 9483.99 | 33.48 | 27.17 |
| obox → sing-box | download | 2 | 11133.98 | 8629.69 | 7361.78 | 32.48 | 65.44 |
| obox → sing-box | upload | 2 | 11475.31 | 11818.42 | 7419.87 | 32.48 | 65.44 |
| sing-box → obox | download | 2 | 11817.06 | 7681.18 | 11004.42 | 64.78 | 26.79 |
| sing-box → obox | upload | 2 | 11220.78 | 7401.85 | 8679.36 | 64.78 | 26.79 |
| sing-box → sing-box | download | 2 | 11337.45 | 7582.08 | 9416.63 | 66.36 | 66.29 |
| sing-box → sing-box | upload | 2 | 11696.84 | 8404.52 | 7581.64 | 66.36 | 66.29 |
Goodput and CPU efficiency show valid-sample averages. Peak memory covers both upload and download.
System requirements
Windows
Windows 10 or later, build 19041 or higher.
macOS
macOS 15 or later.
Android
Android 9 or later, API level 28 or higher.
iOS
iOS 18 or later.
These are minimum runtime requirements. Maintenance for a particular OS version follows the shorter of the OS vendor’s and development toolchain’s official support windows. Paid extensions such as Windows ESU are excluded.
Privacy and ongoing support
Maintenance for OneBox and OneBoxM ends on December 31, 2027. Lifecycle support then continues through OneBoxN within its published Windows, macOS, Android, and iOS platform coverage. All three clients follow the same privacy policy.