Open source personal AI infrastructure

A user-owned cloud OS for apps, agents, identity, and data.

BuckyOS turns a user's own devices into a Zone: a private cloud that can run web services, AI agents, distributed storage, gateways, and system services with a unified identity and permission model.

Start from source Explore the stack

Beta2: active developer release
Rust + TypeScript: native SDK paths
Zone first: for personal and edge clouds

Understand What BuckyOS is A private cloud OS centered on the user's Zone. Inspect System components Kernel services, frame services, apps, gateway, SDK. Build Apps and agents Port Docker services, write native apps, extend AI runtime. Contribute Join SourceDAO Issues, proposals, module work, docs, and governance.

Definition

BuckyOS is not another NAS dashboard.

It is a distributed operating system for personal clouds. A Zone can include one or many devices, expose services through stable gateways, install apps as packages, and give every app and agent a verifiable identity.

A Zone-owned runtime

Users run services on their own devices while BuckyOS manages activation, routing, service discovery, and upgrades.

An app platform

Developers can ship web apps, Docker-backed services, native services, client packages, agents, and system plugins.

A personal AI substrate

OpenDAN, Jarvis, Agent Tool, AI Computer Center, and Message Center make agents first-class system actors.

Architecture

The system is built around one control loop.

system-config stores Zone state, scheduler derives the intended system, node-daemon converges each device, and cyfs-gateway makes services reachable across real home and edge networks.

BuckyOS architecture diagram — Current architecture map from the BuckyOS repository.

system-config

The Zone's source of truth for users, devices, services, permissions, and scheduler results.

scheduler

A deterministic derivation layer that writes node_config, service_info, gateway routes, and RBAC state.

node-daemon

A device-side convergence loop that installs, deploys, starts, stops, and reports service instances.

cyfs-gateway

The networking kernel for ZoneGateway, NodeGateway, service routing, NAT traversal, and process-chain policies.

verify-hub + RBAC

The identity and permission path for session tokens, trust keys, and resource-level enforcement.

repo-service

A Zone-local content and package distribution service for ready-first app and system upgrades.

Use cases

What developers can build on BuckyOS

The platform is for applications that should live with the user: private services, local-first tools, AI agents, personal knowledge systems, content networks, and hardware-integrated products.

Port an existing web service

Wrap a Docker service with BuckyOS app metadata, expose it through the ZoneGateway, and let users install it into their own cloud.

Create a native app

Use the Rust or TypeScript SDK to call system services, discover endpoints, and request user-granted capabilities.

Build an agent product

Give agents DID-based identity, tool access, memory, workflow hooks, and controlled runtime isolation.

Ship hardware-compatible software

Target OOD devices, edge nodes, private gateways, and multi-device Zones with a single system model.

Quick start

Build the active source tree.

Source installation is the recommended first step for contributors because it exposes the build, rootfs, gateway, and runtime workflow.

git clone https://github.com/buckyos/buckyos.git
cd buckyos
uv run src/buckyos-build.py --skip-web

Read repository README Architecture guide Contributor guide

Why it exists

The next wave of software should belong to its users and builders.

Modern software became services, but user data, identity, and distribution moved into platforms owned by others. BuckyOS starts from the opposite assumption: the user owns the Zone, the apps run there, and identity travels with the user.

For developers, this creates a new product surface: apps can be modular, AI-friendly, private by default, and distributed through open infrastructure instead of platform tax and lock-in.

User-owned data Services live with the user's files, identity, permissions, and AI context.

Zero-OPS personal cloud Delivery, routing, upgrade, and recovery are part of the OS path.

Open collaboration The SourceDAO model rewards code, docs, ideas, bug reports, and module leadership.

Community

Join as a developer, contributor, or module owner.

Start with an issue or pull request, propose larger changes under proposals, and use the architecture docs as the source of truth before coding.

Repository GitHub

Read code, open issues, send pull requests, and follow active discussions.

Governance SourceDAO

Explore contribution rewards, DAO rules, and long-term project governance.

Documentation Architecture docs

Understand the current system before changing scheduler, gateway, identity, or delivery paths.