BYOC / OpenComputers

OpenComputers is MIOSA’s bring-your-own-compute path. Install the agent on your own hardware — laptops, desktops, mini-PCs, even Raspberry Pi for light workloads — and it registers with MIOSA over an outbound WebSocket. Your machine becomes a MIOSA computer that you (or your AI agents) can drive through the same API as cloud computers.

Apache 2.0. Local-first scheduling — work runs on your hardware when there’s capacity; cloud overflow when there isn’t.

Why BYOC

Already own the hardware. No reason to pay for cloud capacity for workloads you have machines for.
Local LLMs, local models. GPU on your machine, MIOSA orchestrates the work.
Data residency. Work runs on your hardware, not in our datacenter.
Cloud overflow. Scale beyond your local fleet when needed; MIOSA places overflow on its cloud.
Same API. Your agent code doesn’t care if a job runs on miosa-host-01 (cloud) or dad-mac-mini (your home network).

Install the agent (one command)

# On the host machine
curl -fsSL https://miosa.ai/install | sh

The installer:

Detects your OS (macOS / Linux / Windows; WSL2 supported).
Downloads the OSA agent binary.
Prompts for a registration token (from your MIOSA dashboard).
Starts the agent as a system service (launchd / systemd / Windows Service).

The agent maintains an outbound WebSocket to MIOSA — no inbound ports, no public IP. NAT-friendly.

Three modes

Mode	What’s exposed	Use case
Direct	The host machine itself is one Computer	Use your laptop as a computer for a single agent
VM dispatch	The agent creates Firecracker microVMs on the host; each is a Computer	Run multiple parallel agents on one beefy machine
Slicing	One physical machine partitioned into N independent desktop sessions	Multi-tenant workstation; pre-K12 / kiosk fleet

Most setups use VM dispatch — gives you process isolation, snapshots, and lifecycle the same way cloud computers work.

Use a BYOC computer

// List your hosts
const hosts = await miosa.openComputers.hosts.list()

// Create a computer on a specific host
const computer = await miosa.computers.create({
  name: "local-agent",
  templateType: "miosa-desktop",
  hostId: hosts[0].id,  // optional; scheduler picks if omitted
})

// From here, identical API as a cloud computer
await computer.desktop.screenshot()

The scheduler honors local-first placement by default — if you have available capacity on a BYOC host, jobs land there. Override via explicit hostId or set scheduling preferences per workspace.

Tunnels

When you need direct browser access to a port running inside the host machine (a local dev server, a vendor admin UI, your home Home Assistant), open a MIOSA tunnel:

const tunnel = await miosa.openComputers.tunnels.create(hostId, {
  port: 8123,
  name: "home-assistant",
})

console.log(tunnel.public_url)
// → https://home-assistant.your-workspace.tunnels.miosa.app

The tunnel is authenticated server-side (MIOSA workspace), proxied through MIOSA’s edge, and emerges on your host via the outbound WebSocket. Same security properties as Preview — short-lived tokens for browser-facing access, no public IP needed on your host.

Resource control

You control what your host shares with MIOSA:

# ~/.miosa/agent.yaml
resources:
  max_cpu_percent: 50      # cap MIOSA workloads at 50% of CPU
  max_ram_mb: 8192         # 8 GB ceiling
  max_disk_gb: 100
  schedule:
    - {days: [Mon-Fri], hours: "09:00-17:00", paused: true}  # don't share during work hours

The agent reports available capacity to the scheduler in real time. Workloads are gracefully drained off when you go below limits.

Health and reliability

Hosts emit heartbeats every 30s. After ~2 minutes of missed heartbeats, the scheduler marks the host offline and stops placing new work on it. In-flight work either completes (if the host comes back) or is rescheduled to other hosts.

For production-critical workloads, run multiple BYOC hosts and let MIOSA spread work across them.

Security

The agent runs as a regular user (recommended), not root. Computers are Firecracker microVMs the agent spawns; they cannot escape to the host machine.
The outbound WebSocket is authenticated by a host-specific key tied to your tenant. Compromising one host doesn’t expose other hosts in your fleet.
The agent is open source (Apache 2.0) — auditable.

Pricing

OpenComputers agent: free. Apache 2.0, run as many hosts as you want.
MIOSA scheduling / control plane: per-host fee. Plans range from free (a few personal hosts) to enterprise (hundreds of hosts, fleet management UI).

See Pricing for details.