Ecosystem & Roadmap

KSP Platform Roadmap: Gateway → Browser → SDK

Instead of generic placeholder timelines, KSP follows a strict 5-stage architectural progression designed to bring custom binary framing from low-level Rust daemons right to standard browser clients.

Core Deployment Pipeline & Milestone Progression
Q4 2026Stage 01

Edge Gateway Proxy

Rust `tokio`/`hyper` TLS 1.3 reverse proxy terminating HTTPS into KSP binary frames.

Priority: Highest→ Next
Early 2027Stage 02

Browser Preview

WebRTC / WASM client runtime allowing standard web applications to speak KSP natively.

Priority: Sequential→ Next
Mid 2027Stage 03

Core SDK Suites

Idiomatic async client libraries for Rust (`tokio`), Python (`asyncio`), Go, and TypeScript.

Priority: Sequential→ Next
Q3 2027Stage 04

Browser Extension

DevTools inspection plugin for inspecting multiplexed KSP frames right in Chrome/Firefox.

Priority: Sequential→ Next
Q4 2027Stage 05

Native Client Daemon

OS-level system daemon for transparent 0.0.0.0:9876 socket forwarding on Linux/macOS.

Priority: SequentialComplete

Core

SDKs

Tools

Future RFCs