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:
Why .orb?
Embedded systems are traditionally hard to manage:
.orb solves this by introducing a standard, reliable application model:
How does it work?
From a developer perspective, the workflow is simple:
The runtime handles:
What can an .orb app do?
Applications can interact directly with the device through the OrbitOS APIs:
Isolation & Security
Each .orb application runs in a controlled environment:
This ensures that applications remain safe and predictable — even in production environments.
More than just packaging
.orb is not just a file format.
It is the foundation for:
It enables Orbit OS to behave like a true application platform for embedded devices.
What’s next?
In upcoming posts, we’ll cover:
How to build your first .orb application
Packaging structure and tools
Deploying apps through the dashboard
With .orb, devices stop being static systems — and become programmable platforms.
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)
Why .orb?
Embedded systems are traditionally hard to manage:
- Manual deployments
- Inconsistent environments
- Difficult updates
- Limited isolation
.orb solves this by introducing a standard, reliable application model:
- Install apps in a consistent way
- Update them safely
- Run them in isolation
- Manage them remotely
How does it work?
From a developer perspective, the workflow is simple:
- Build your application using the Orbit OS SDK
- Package it into an .orb file
- Install/Update it on device
The runtime handles:
- Execution
- Restart on failure
- Resource access
- Security enforcement
What can an .orb app do?
Applications can interact directly with the device through the OrbitOS APIs:
- 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
Isolation & Security
Each .orb application runs in a controlled environment:
- Defined permissions
- No direct system access unless allowed
- Secure communication between components
This ensures that applications remain safe and predictable — even in production environments.
More than just packaging
.orb is not just a file format.
It is the foundation for:
- Application distribution
- Remote deployment
- Version control
- Device-level orchestration
It enables Orbit OS to behave like a true application platform for embedded devices.
What’s next?
In upcoming posts, we’ll cover:
How to build your first .orb application
Packaging structure and tools
Deploying apps through the dashboard
With .orb, devices stop being static systems — and become programmable platforms.