Aeion Bridge — Local Hardware + GPU AI for Cloud Aeion OS

Run Stable Diffusion image generation, TTS, video synthesis, code execution, Docker management, and terminal access — all from cloud Aeion OS via MCP. No port forwarding. Outbound WebSocket only.

Bridge Capabilities — 8 Local Services Over MCP

Image Generation

Turn a prompt into a finished product photo in seconds — text-to-image, img2img, inpainting, and upscaling all run on your own Stable Diffusion / ComfyUI rig, so a 500-image batch costs $0 in API fees

Text-to-Speech

Every order-confirmation or IVR voice line generated on your own hardware — zero per-character API fees no matter how much text you narrate

Video Generation

Frames, animation, and motion synthesized locally, so iterating on a video concept doesn't rack up a per-second cloud-rendering bill

Music Generation

Background scores and audio beds generated on your own GPU instead of billed per-generation by a third-party API

3D Rendering

Scenes rendered and exported locally — no upload-wait-download round trip to a cloud render farm

Code Execution

Compile, test, and deploy code directly from the Admin UI, on hardware you control, without shipping your source to a third-party sandbox

Native Capture

Screen, camera, microphone, and system info are one MCP call away — the same agent drafting a reply can also grab the screenshot that explains the bug

GPU Compute

One local GPU powers every capability above — image, TTS, video, music, and 3D all share the same hardware instead of needing separate accounts and separate bills

10 Admin Views Across 4 Groups

Dashboard

Bridge Status — See at a glance which devices are online and ready to take a job — before you try to run one and it fails

AI & Compute

AI Models, GPU Compute, MCP Tools — Every generative capability — image, TTS, video, music, 3D — plus code execution, run from the same admin panel you already use for everything else

DevOps

Terminal, Docker, Git — Remote shell, container management, and repo operations without leaving the Admin UI for a separate SSH session or CI dashboard

Hardware

System Monitor, Media Capture, File Sync — CPU/RAM/disk health, screen/camera/mic capture, and local-cloud file sync — the operational visibility that used to mean logging into the machine directly

MCP-Native — AI Agents Control Local Hardware

Model Context Protocol integration:

```typescript // Bridge MCP tools are standard MCP tools — AI agents discover and invoke them:

// AI agent requests tools: { "method": "tools/list", "params": {} } // Response includes Bridge capabilities: { "tools": [ { "name": "compute.image.generate", "description": "..." }, { "name": "compute.tts.generate", "description": "..." }, { "name": "bridge.docker.list_containers", "description": "..." }, { "name": "bridge.terminal.exec", "description": "..." }, // ... 50+ Bridge tools ] }

// Agent calls a tool: { "method": "tools/call", "params": { "name": "compute.image.generate", "arguments": { "prompt": "futuristic city at sunset", "model": "flux-schnell", "width": 1024, "height": 1024 } } } // → Bridge client receives call // → Executes on local GPU // → Returns image as base64

// Same interface as cloud tools — agent can't tell the difference ```

AI agent workflow with Bridge:

``` User: "Generate product photos for our new shoe line" AeionClaw → Bridge image generation → "flux-schnell" model on local RTX 4090 → 4 images in 8 seconds → Images stored in Aeion Files → Thumbnails generated via Bridge native capture → Results shown in Admin UI

User: "Print shipping labels for today's orders" AeionClaw → Bridge native capture / device tools → Connects to USB label printer → Generates ZPL commands → Prints 50 labels in 30 seconds

User: "Deploy the new Docker container to staging" AeionClaw → Bridge MCP tools (bridge.docker.*) → Remote terminal over WebSocket → docker-compose pull && up → Logs streamed back to Admin UI ```

Image Generation — Local Stable Diffusion / ComfyUI

Every image operation is a Bridge MCP tool call:

```typescript // Text-to-image const result = await bridge.call("compute.image.generate", { prompt: "professional product photography, white background, studio lighting, shoe", negativePrompt: "blurry, watermark, text, logo", model: "flux-schnell", width: 1024, height: 1024, steps: 20, batchSize: 4, // Generate 4 variations });

// img2img const transformed = await bridge.call("compute.image.generate", { prompt: "oil painting style", model: "sdxl-turbo", sourceImage: base64ProductPhoto, strength: 0.75, // 75% influenced by prompt });

// Inpainting const inpainted = await bridge.call("compute.image.edit", { image: base64ProductPhoto, mask: base64Mask, // White = keep, Black = regenerate prompt: "red sports car background", model: "flux-schnell", });

// Upscaling const upscaled = await bridge.call("compute.image.upscale", { image: base64GeneratedImage, scaleFactor: 4, // 1024 → 4096 pixels model: "real-esrgan", });

// Results: { images: [base64String, ...], model: "flux-schnell", generationTime: 8200, // ms seed: 1234567890, steps: 20, cfgScale: 7.5, } ```

Why local vs API (Replicate, OpenAI DALL-E)?

``` DALL-E 3: $0.04/image × 1000/month = $40/month Flux API: $0.003/image × 1000/month = $3/month Local (RTX 4090): $0/image × unlimited = $0/month + $0.15/kWh × 0.05kWh/image × 1000 = $7.50/month electricity + GPU amortized: $0.03/image (3-year RTX 4090)

Local: $0.03-0.04/image equivalent vs $0.003-0.04 API cost At 10K images/month: $300-400 API vs ~$50 local (GPU+electricity) ```

Text-to-Speech — Zero Per-Character API Fees

Every TTS operation is a Bridge MCP tool call — parameters: `text` (up to 10,000 characters), `voice`, `model` ("kokoro" / "bark" / "f5-tts"), `speed` (0.5–2.0), `format` ("mp3" / "wav" / "ogg"), `sampleRate`:

```typescript // Generate TTS const audio = await bridge.call("compute.tts.generate", { text: "Your order #12345 has been shipped and will arrive by May 15th.", voice: "en-US-Neural2-F", speed: 1.0, format: "mp3", }); // → Returns: { audio: base64MP3, duration: 3.2, format: "mp3" }

// Stream generation const stream = await bridge.call("compute.tts.stream", { text: "Long form content here...", format: "mp3", }); // → Streams chunks as generated (for real-time applications)

// List available voices const voices = await bridge.call("compute.tts.models", {}); // → [{ id: "en-US-Neural2-F", name: "Female US Neural", language: "en-US" }, ...] ```

Comparison:

ElevenLabs: $0.30/1000 characters = $300/month per 1M chars Google Cloud TTS: $0.016/1000 characters = $16/month per 1M chars Amazon Polly: $0.04/1000 characters = $40/month per 1M chars Local Bridge TTS: $0/character + ~$5/month electricity

DevOps — Terminal, Docker, Git from Admin UI

Remote terminal over WebSocket:

```typescript // Admin → Bridge → Terminal // → WebSocket connection to Bridge client // → PTY (pseudo-terminal) running on host machine // → Full ANSI color, history, autocomplete

// Code execution via MCP: const result = await bridge.call("bridge.code.execute", { language: "typescript", code: import { z } from "zod"; const schema = z.object({ name: z.string(), age: z.number() }); const result = schema.safeParse({ name: "Alice", age: 30 }); console.log(JSON.stringify(result, null, 2)); , timeout: 10000, // 10 second timeout }); // → { stdout: '{"success":true,"data":{"name":"Alice","age":30}}', stderr: "", exitCode: 0 } ```

Docker management via MCP:

```typescript // List containers const containers = await bridge.call("bridge.docker.list_containers", {}); // [{ id: "abc123", name: "postgres-db", status: "running", image: "postgres:16" }]

// Start / stop / logs await bridge.call("bridge.docker.start_container", { id: "abc123" }); const logs = await bridge.call("bridge.docker.get_logs", { id: "abc123", tail: 100, });

// Docker Compose await bridge.call("bridge.docker.compose_up", { path: "/workspace/docker-compose.yml", }); ```

Git operations via MCP:

```typescript // Clone repository await bridge.call("bridge.git.clone", { url: "https://github.com/acme/backend.git", path: "/workspace/backend", });

// Commit and push await bridge.call("bridge.git.commit", { path: "/workspace/backend", message: "feat: add user authentication", files: ["src/auth/login.ts", "src/auth/logout.ts"], });

// Status and diff const status = await bridge.call("bridge.git.status", { path: "/workspace/backend", }); const diff = await bridge.call("bridge.git.diff", { path: "/workspace/backend", file: "src/auth/login.ts", }); ```

Zero-Network-Config Setup — Outbound WebSocket Only

How Bridge connects:

``` Bridge Client (your laptop) ↓ outbound WebSocket (port 443, standard HTTPS) → Cloud Aeion OS API (port 4000)

No inbound ports needed. No port forwarding. No ngrok. No firewall exceptions. Works from home, office, coffee shop, hotel. ```

Authentication:

```typescript // Bridge client authenticates with tenant-scoped API key: { "type": "bridge_client", "tenantId": "tenant_acme_corp", "scopes": ["files:read", "files:write", "docker:manage", "terminal:execute"], "expiresAt": "2027-01-01", "key": "sk_bridge_..." }

// Every MCP tool call validated against scopes: // → compute.image.generate → requires "ai:generate" scope // → bridge.docker.* → requires "docker:manage" scope // → bridge.terminal.exec → requires "terminal:execute" scope ```

Auto-discovery:

```typescript // On startup, Bridge client checks: // 1. localhost:4000 (local development) // 2. Configured bridge URL (production) // 3. mDNS/SSDP discovery (local network)

// Bridge client attempts each discovery method in order // → If found: establishes WebSocket connection // → If not found: operates in cloud-only mode ```

Frequently Asked Questions

No. Cloud-only Aeion OS works without Bridge for most use cases. Bridge adds optional capabilities — local AI inference (so AI calls don't leave your network), POS hardware integration, ONVIF camera control, BLE / Wiegand readers, FFmpeg-on-your-GPU for video transcoding. Install it where you need those capabilities.

Outbound WebSocket over HTTPS 443 — same port your browser uses to reach Aeion. No inbound ports, no port forwarding, no ngrok, no firewall holes. Bridge initiates the connection; cloud holds the receiving end.

Yes — one Bridge process serves all the hardware physically connected to that machine. For multi-location operations, install Bridge per location. Each Bridge has its own scoped credentials so a Bridge at Location A can't accidentally drive devices at Location B.

Bridge runs Stable Diffusion (image), Whisper.cpp (transcription), Spleeter (stem separation), Kokoro TTS, and other on-device models via the Bridge AI services. Cloud requests "generate this image" → cloud forwards to your tenant's Bridge → Bridge runs the model on your local GPU → response goes back. Zero API fees for the inference itself.

No — the Bridge client is proprietary and distributed as a signed, ready-to-run installer for Windows, macOS, and Linux, included with your Aeion OS subscription. The WebSocket/MCP protocol it speaks is documented, so it can interoperate with your own tooling.

Idle Bridge uses <100MB RAM + <1% CPU. Active AI inference uses your GPU during the inference call; CPU usage proportional to the request rate. Bridge respects OS-level priority — your interactive apps stay snappy.

Your Hardware. Your GPU. Your Cloud.