NDS: an open system for managing devices, servers and teams
NDS, or NDDev Device Sync, is an open system a company runs on its own server to manage employee devices, servers and AI agent tools. It is written in Rust with Flutter and React clients, and is developed in the open in its own GitHub organization: 19 public repositories under AGPL-3.0, one per module. The first alpha is in preparation.
Who it is for
Companies where every employee has several devices and teams and access change often, and teams that keep device management on their own server.
- Your own control server
- Rust, Flutter and React
- 19 open modules
- First alpha in progress
NDS modules
At the base of NDS are the Rust control server and core, with an open protocol described in OpenAPI. Around them work the accounts and organizations modules: companies, invited employees and their access.
- nddev-device-sync: standards, the module catalogue and assembly
- server and core: the Rust control server and core
- protocol: wire contracts and OpenAPI schemas
- accounts and organizations: accounts, companies and members
- agent: the device agent
- vault: encrypted storage
- desktop, mobile and web: clients for computers, phones and the browser
- sysinfo, clipboard, cleaner, updater, gds and rds adapters
- observability: telemetry for the whole system
- opennetwork-design-system: design tokens and the Flutter theme
An agent runs on every device. Through adapters it connects system metrics, the clipboard, cache cleaning, updates, repositories through GitHub Device Sync and RDS remote access.
Employee data has encrypted storage with replicas on devices and in the browser. The clients for computers, phones and the browser are built on the open OpenNetwork design system, and a shared telemetry module shows how the whole system runs.
How to start with NDS
NDS is preparing its first alpha, so we start with a review of your devices.
Your devices
You tell us how many people, teams and devices you have and what runs on them.
Fit with NDS
We explain which NDS modules fit your task now and which come later.
First modules
If ready open parts such as GitHub Device Sync suit you, we help you install them now.
Bringing NDS in
Once NDS is ready for your scenario, we deploy the server and connect your teams and devices.
Questions about NDS
Can we use NDS already?
NDS is preparing its first alpha; its code is open and changes constantly. We discuss bringing it in for your task in person.
Where can we see the code?
In the NDDev-Technocracy-OpenNetwork-NDS GitHub organization: 19 public repositories under AGPL-3.0, one for each module.
How does NDS relate to GitHub Device Sync and RDS?
NDS connects them through its adapters. GitHub Device Sync and RDS remain separate projects and work on their own.
Can NDS run on our own servers?
Yes, NDS is built to be installed on your server. While the alpha is being prepared, we discuss such an installation separately.
Which devices are supported?
NDS clients are written in Flutter for computers and phones, and there is a web client for the browser. We will name the exact operating systems for the release.
Related
Let us talk about bringing your devices and teams into NDS
Describe how many employees and devices you have and what is awkward today. We will tell you which NDS modules suit you first.
We reply within 24 hours