Opscotch 3.1.5 brings true write-once-run-anywhere capability. From this release, opscotch publishes native binaries and runs on Linux x86-64, Linux ARM64, Windows x86-64, and macOS Apple Silicon.

Opscotch is now a genuinely portable platform.

Opscotch publishes native binaries for four platforms. Each release includes:

• The runtime (opscotch-agent) - the core execution engine
• The test runner (opscotch-testrunner) - for running automated tests

Native binaries are the choice when you want bare-metal or VM execution without Docker.

• Linux x86-64 - Standard Linux servers and workstations
• Linux ARM64 - ARM servers, RaspberryPi64, and Apple Silicon under Linux
• Windows x86-64 - Native Windows desktops and servers
• macOS Apple Silicon - M1, M2, M3 and later Macs

Each platform gets both the runtime and test runner binaries.

Why this matters

Previously, opscotch was primarily a Linux technology. The choice to standardize on Linux containers already gave you cross-platform Docker deployment, but native execution was limited.

With 3.1.5:

• You can run the opscotch binary directly on any of the four target platforms without container overhead.
• Your packaged .oapp applications are portable across all supported architectures.
• Dev teams can develop on their preferred platform and deploy anywhere.
• The same bootstrap and configuration works uniformly across platforms.

This closes the gap between "it works in my container" and "it runs natively where I need it".

Linux ARM64 and RaspberryPi

Linux ARM64 support includes RaspberryPi64 boards. If you are running Raspberry Pi OS 64-bit (or any other 64-bit Arm Linux distribution), opscotch now runs directly:

# Extract the ARM64 ZIP
unzip linux-opscotch-agent-linux-ARM64-3.1.5.zip
./opscotch-agent

This opens opscotch for edge computing, IoT projects, and home-lab automation in a way that was not previously practical.

[PLACEHOLDER: Consider adding a real-world use case or example here, such as a home automation project or edge deployment scenario.]

Docker and multi-platform deployment

Opscotch publishes standard Linux container images to GHCR:

docker pull ghcr.io/opscotch/opscotch-agent:3.1.5

These images are:

• Built on Linux
• Cross-platform through Docker Desktop on Windows and macOS
• Available for both x86-64 and ARM64 container hosts

On Windows, you run Linux containers through Docker Desktop or WSL2. This is the standard industry practice, and it means your opscotch deployment behaves consistently regardless of the host operating system.

On macOS Apple Silicon, Docker Desktop runs Linux ARM64 containers natively. Your opscotch workloads travel with the host architecture.

[PLACEHOLDER: Add note here about multi-architecture manifest if applicable, e.g., whether ghcr.io/opscotch/opscotch-agent publishes multi-arch manifests automatically.]

The portability contract

Opscotch defines the portability guarantee at the runtime layer:

Platform	Native Binary	Linux Container
Linux x86-64	Supported	Supported
Linux ARM64	Supported	Supported
Windows x86-64	Supported	Via Docker Desktop / WSL2
macOS Apple Silicon	Supported	Via Docker Desktop

The key insight: container images run on all platforms through Linux container tooling. Native binaries are the choice when you want bare-metal or VM execution without Docker, or when container startup latency matters for your use case.

Getting started

Download from the opscotch releases:

Choose your platform ZIP and extract. Or, if you prefer containers:

docker run ghcr.io/opscotch/opscotch-agent:3.1.5

For the detailed installation options, verification steps, and configuration, see:

• Downloads and Installation

What's next

With the four-platform foundation in place, opscotch becomes a realistic option for:

• Cross-platform development teams
• Edge and IoT deployments on RaspberryPi and similar ARM boards
• Hybrid cloud and on-premises environments with mixed host types
• Consistent developer experience regardless of personal machine preference