OctopusOS Supported Platforms Analysis

An analysis of the full platform matrix covered by OctopusOS, based on adapter implementations, build configurations, and contract definitions in the codebase.

1. Server Platform

Production Environment: Ubuntu Linux

Code evidence:

• docs/milestone_node_v1.md — octopus-os node runs Ubuntu
• kernel/core/orchestration/central_orchestrator.py — reads memory info from /proc/meminfo (Linux-specific)
• 9 systemd service units — Linux systemd dependency

Supported Host Hardware

Runtime Environment

2. Desktop Platforms (Tauri + ScreenOS)

2.1 Native Application (Tauri 2.x)

Tauri compiles to native binaries via Rust, supporting all three major desktop operating systems.

Code evidence: products/desktop/package.json

2.2 ScreenOS Desktop Adapters

Through the ScreenPort abstraction, different underlying automation technologies are used on different desktop operating systems.

Code evidence:

2.3 Platform Definitions in ScreenOS Contracts

# kernel/contracts/screen_os.py
# Supported values for ScreenSnapshot.platform
platform: Literal["macos", "windows", "linux", "android", "ios"]

3. Mobile Platforms (Expo + ScreenOS)

3.1 Native Application (React Native / Expo)

Code evidence: products/mobile/package.json

Responsive Adaptation

Code evidence: products/mobile/App.tsx

3.2 ScreenOS Mobile Adapters

Code evidence:

Mobile UI Node Roles

ScreenOS defines dedicated NodeRole values for mobile platforms:

# kernel/contracts/screen_os.py — Mobile roles
NodeRole = Literal[
    ...,
    "activity",      # Android Activity
    "snackbar",      # Mobile notification bar
    "bottom_sheet",  # Bottom sheet panel
    "fab",           # Floating action button
    ...
]

Mobile Action Types

# kernel/contracts/screen_os.py — Mobile-specific actions
ActionType = Literal[
    "click", "type_text", "scroll", "drag",  # Universal
    "tap",     # Mobile tap
    "swipe",   # Mobile swipe
    "back",    # Android back key
    "home",    # Home key
]

4. Web Platform

4.1 Web Console

Code evidence: products/web/

4.2 ScreenOS Browser Adapter

Code evidence:

ARIA role mapping: 40+ ARIA roles mapped to 28 NodeRole values

# screen_playwright.py
# ARIA role → NodeRole mapping examples
"button" → "button"
"textbox" → "text_field"
"checkbox" → "checkbox"
"dialog" → "dialog"
"menu" → "menu"
"tab" → "tab"
# ... 40+ mappings

5. Terminal Platforms

5.1 CLI Product

Code evidence: products/cli/

5.2 TUI Product

Code evidence: products/tui/

6. Cloud Platform Integration

Capability Package Coverage

Code evidence: server/shared/capabilities/ capability packages

MCP Cloud Servers

Cloud API Routes

Code evidence: server/shared/adapters/http/_routes_cloud.py

GET  /api/cloud/aws/ec2/instances       # EC2 instance list
GET  /api/cloud/aws/cloudwatch/metrics  # CloudWatch metrics
GET  /api/cloud/aws/cost/summary        # Cost summary
GET  /api/cloud/azure/vms               # Azure VM list

7. External Service Platform Integration

Communication Platforms

Business Platforms

Database Platforms

DevOps Platforms

8. Security Testing Platform

Kali Linux Node

Code evidence: MEMORY.md kali-node.md

9. Platform Baseline (21 Platform Baselines)

The kernel includes built-in baseline definitions for 21 platforms, used for skill maturity assessment.

Code evidence: kernel/contracts/platform_baseline.py

# PlatformBaseline — 21 platforms, ~230 service families
# Each platform defines core services, security requirements, monitoring needs

10. Platform Support Overview