OneBox
About Us
The original intention behind this project comes from our first-hand experience running services over the past decade. We have witnessed the rapid growth of third-party client software, and also the decline or disappearance of many of those products.
What problems we observed
During that time, a large amount of after-sales effort was consumed by issues introduced by third-party clients. Many of them lacked consistent quality control, behaved unpredictably, and kept adding advanced features aimed at a small group of power users directly into general products, which increased the learning and usage cost for ordinary users.
How we chose to build
Those advanced needs are valid and valuable, but most users do not need all of them in their daily workflow. We built OneBox for everyday use and are continuing that work with the native OneBoxN client. We focus on stability and usability, with fewer setup steps and usable defaults. Our support policy sets out the maintenance schedule for each client.
Our product principles
- Stability first: protect predictable core behavior before adding more features.
- Built for ordinary users: reduce setup friction and avoid shifting complexity to users.
- Ready out of the box: usable defaults without requiring deep technical knowledge.
- Continued improvement: refine the reliability and usability of the OneBox family within each client’s published maintenance schedule.