Sharing in case it helps others: I had a login error after changing password, but it was local session cache.

After clearing session data and authenticating again, everything worked.

Thanks to support for the quick and objective response.

I used ioflow with serial-console in a prototyping project and it worked very well.

Installation through the Store was simple, and integration between apps was stable from day one.

Great job on the curation of recommended apps.

I have worked with embedded stacks for years and I really like OrbitOS architecture.

It is modular without being complicated, and components communicate with clear separation of concerns.

Congrats to the team for the technical clarity.

Quick validation results to share:

- clean install on Pi 4
- deployment of 3 Store apps with no errors
- updates applied with controlled reboot
- rollback tested successfully

The simplicity of the update flow helped a lot during QA.

Hi everyone! I am Bruno and I just started using OrbitOS in a lab setup.

First impression: very simple setup and documentation that is direct and clear.
I was able to bring up the core services in under 20 minutes.

Congrats to the team for a smooth onboarding experience.

Hi all,

For production deployments, what baseline firewall profile are you using on OrbitOS nodes?

I am aiming for:
- deny by default
- explicit allowlist for app ports
- remote management only via VPN

Any recommended defaults from the team?

Hello everyone,

I deployed OrbitOS on a Raspberry Pi 5 to monitor a small electronics workshop.

Current stack:
- serial-console for MCU logs
- webcam-preview for workspace checks
- ioflow for event routing

If useful, I can share the wiring diagram and app config.

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