Hi team,

I am testing OrbitOS on Raspberry Pi 4 and would love an official Home Assistant bridge app from the Store.

Main use cases:
- expose device telemetry as entities
- trigger install/update actions from automations
- lightweight auth token flow

If there is already a roadmap item for this, I can help with testing.

MCP Server introduces a new way to interact with OrbitOS devices — built for automation, AI, and modern developer workflows.

- The first version is already available in the store and ready to install remotely on your devices.

Here



It exposes the device through the Model Context Protocol (MCP), enabling tools like Cursor and other compatible AI assistants to interact with the system using structured, well-defined capabilities — no custom scripts, no manual glue code.

• Query system status
  
• Install packages
  
• Reboot the device
  
• Read or control GPIO
  

• Hardware info, OS details, metrics, API versions
  

• List installed apps
  
• Install packages
  
• Remove packages
  

• Install OTA updates
  
• Perform factory reset
  

• Reboot or shut down with context
  

• Read/write pins
  
• Change direction
  
• Access by name or ID
  

• "What’s the current status of the device?"
  
• "List installed applications"
  
• "Install this package from file"
  
• "Reboot the device"
  
• "Set GPIO 17 to HIGH"
  
• "Check system metrics"
  

- Orbit OS Architecture — Platform Overview

Orbit OS is a secure distributed operating system for embedded Linux devices. It transforms hardware into managed compute nodes where applications and services execute within a unified, high-performance runtime.



### Gravity RT (The Execution Engine)
At the heart of Orbit OS is **Gravity RT**, the secure execution core.
  **Isolation:** Enforces strict process isolation and resource limits.
  **Unified API:** All system interactions go through Gravity RT regardless of origin.
  **Security:** Validates cryptographic signatures for every process before execution.

### The .orb Package Model
All software is distributed as **.orb** packages. These are atomic, signed units containing:
  * Executable code & manifests.
  * Explicit resource and permission declarations.
  * Mandatory cryptographic signatures.

### Trust Model & Security
Orbit OS uses a certificate-chain trust model:
  **Store-Signed (Production):** Fully trusted, eligible for auto-updates and fleet-wide deployment.
  **Development-Signed (SDK):** Verified for local testing and rapid iteration, but isolated from production fleet policies.

### Real-Time Developer Workflow
One of Orbit OS’s unique features is **Developer Mode**.
  **Direct Execution:** Developers can execute logic directly on live devices via the SDK without packaging `.orb` files first.
  **Unified API Surface:** The exact same API used by production `.orb` packages (via UDS) is exposed to remote development tools (via TCP), ensuring "it works on my machine" translates perfectly to the device.

### Key Design Principles
  1. **Everything is a signed .orb.**
  2. **Gravity RT is the single source of truth** for execution.
  3. **Store as Control Plane:** Centralized management for updates and fleet status.
  4. **Real-time first:** Development against real hardware is a first-class citizen.


 **View the full documentation at https://www.orbit-os.org/docs.html

At the core of Orbit OS is a simple idea:

Everything runs as an application.

These applications are packaged using the .orb format — the standard way to build, distribute, and run software on Orbit OS devices.


What is an .orb?

An .orb file is a self-contained application package.

It includes everything needed to run:

• Application code (Go, Python, Java, C++, etc.)
  
• Configuration
  
• Permissions
  
• Metadata (name, version, dependencies)
  

• Manual deployments
  
• Inconsistent environments
  
• Difficult updates
  
• Limited isolation
  

• Install apps in a consistent way
  
• Update them safely
  
• Run them in isolation
  
• Manage them remotely
  

• Build your application using the Orbit OS SDK
  
• Package it into an .orb file
  
• Install/Update it on device
  

• Execution
  
• Restart on failure
  
• Resource access
  
• Security enforcement
  

• Control Peripherals, GPIO, I²C, UART, PWM etc.
  
• Configure network, time etc.
  
• Communicate over network protocols
  
• Process data locally (including AI models)
  
• Integrate with external services
  

• Defined permissions
  
• No direct system access unless allowed
  
• Secure communication between components
  

• Application distribution
  
• Remote deployment
  
• Version control
  
• Device-level orchestration
  

Orbit OS was created to solve a problem that many developers quietly accept:

Building for embedded Linux is harder than it should be.

Fragmented tools, complex setups, and the lack of a unified ecosystem slow down innovation.
Developers end up spending more time managing systems than building real products.

- Our Motivation

OrbitOS exists to remove that friction.
We want developers to:

• Build and deploy applications with consistency across devices
  
• Use modern tools without unnecessary complexity
  
• Integrate AI and advanced features directly on edge devices
  
• Focus on creating value instead of fighting infrastructure
  

• Our goal is to create the missing ecosystem for Embedded Linux
  
• A platform where:
  
• Applications are easy to develop, distribute, and run
  
• Devices are manageable at scale
  
• The App Store model works for embedded systems
  
• Developers can move fast and iterate quickly
  

• Orbit OS is not just another Linux distribution.
  
• It is a complete ecosystem designed around:
  
• Application-centric architecture
  
• Built-in distribution and deployment model
  
• Isolation and security by design
  
• Seamless integration between services and devices
  

• Embedded systems power the world — from IoT to industrial infrastructure — but the developer experience hasn’t kept up.
  
• Orbit OS aims to change that.
  

• This is just the beginning.
  
• Whether you're building apps, experimenting with hardware, or exploring new ideas, you are part of this ecosystem.
  

Welcome to the Orbit OS Community Forum!

Before getting started, please take a moment to read these simple rules and guidelines to help keep the community helpful and friendly for everyone.

Forum Rules

• Be respectful to all members. No harassment, hate speech, or toxic behavior.
  
• Stay on topic and post in the appropriate forum section.
  
• Do not spam, advertise, or promote unrelated content.
  
• Avoid duplicate posts — search before creating a new topic.
  
• Do not share illegal content or sensitive information.
  

• Introduce yourself in the Member Introductions forum.
  
• Check Official Announcements for the latest updates.
  
• Use the correct section when asking questions (Development, Hardware, etc.).
  
• When asking for help, include as much detail as possible (logs, device, setup).
  

• Clearly describe your issue or idea.
  
• Include relevant details (board, version, logs, steps to reproduce).
  
• Be patient — the community will help you.
  

Hello and welcome to the official Orbit OS Community Forum!

We’re excited to have you here, whether you’re a developer, maker, or just curious about Orbit OS. This forum is your central place for updates, announcements, and news related to Orbit OS.

What you can do here:

• Stay up-to-date with the latest Orbit OS releases and features.
  
• Learn about new SDKs, tools, and developer resources.
  
• Connect with other members of the community, share projects, and ask questions.
  
• Get official news directly from the Orbit OS team.
  

• Be respectful and follow the rules outlined in the “Rules & Quick Start” forum.
  
• Keep discussions on-topic within each forum.
  
• Use proper threads for feedback, questions, and suggestions.