What stage is CalmSource at?

Pre-seed. No prior investors, no revenue, one founder, and a working Android runtime in closed beta.

Where is CalmSource based?

Vancouver, British Columbia, Canada (Pacific Time).

What is CalmSource raising?

A pre-seed round on a post-money SAFE. Size scoped with the lead. Proceeds fund 12 months of founder runway plus the first Android runtime engineer hire.

CalmSource

§ 02 — Architecture

Technical OverviewFolio № 02 · Architecture

Runtime engineered for constrained silicon — and any browser.

Three cooperating subsystems, a memory-aware scheduler, and a zero-trust data plane — designed to run inside 48 MB of resident memory on legacy Android devices, with a companion Web build so the same runtime is one click away in the browser.

Data Plane

From manifest to frame

Manifest

Async JSON parse · distributed catalogs

Index

Batched writes · memory-aware workers

Probe

Parallel headless probes · latency + codec score

Route

Optimal path selected · sub-RTT decision

Buffer

Adaptive ceiling · zero-copy handoff

Frame

Hardware decode · presentation queue

Subsystems

Cores and responsibilities

Extension Hub: Asynchronous JSON manifest parser
Resolves community-driven providers and distributed catalogs concurrently at the edge, without a centralized database.
Feed Synchronizer: Batched, memory-aware indexer
Throttles batch-write transactions and maps EPG data via background workers across tens of thousands of live streams.
QoS Router: Parallel probe + latency selection
Races headless probes against distributed content repositories; scores latency and codec fit to pick optimal paths in the first RTT.
Scheduler: Cooperative, RAM-tier aware
Selects worker concurrency based on detected device class; hard caps enforced before OOM watermark.
Observability: Redacted structured events
On-device event ring buffer; opt-in export with automated PII redaction.

Platforms

Where the runtime ships

Android · Mobile: Native runtime · Kotlin / Compose
Primary target. Low-RAM phones and legacy hardware — the tier every incumbent under-serves.
Android · TV: Native runtime · leanback surface
Smart TV sticks, budget TVs, and legacy set-top boxes running Android TV 9+.
Web · Browser: Companion build · same aggregation core
Zero-install browser build of the aggregation runtime — desktop and mobile browsers. Same manifest pipeline, same privacy model.

Non-Functional Guarantees

Contracts we hold ourselves to

Resident Memory: < 48 MB steady state
Enforced by adaptive buffer ceiling; verified across 14 device classes.
Cold Start: < 900 ms to first frame
Median on Android TV 9 · 1 GB RAM reference device.
OOM Panics: 0 observed in 30-day soak
Continuous CI soak on legacy media sticks; regression gate on every release.
Network Egress: Local-first
No server-side session is created; telemetry disabled by default. Same guarantee on Android and Web.