DELIVERY ROADMAP

Capability follows evidence—not presentation.

The phases are ordered by risk reduction and architectural leverage. Profiles, recordings, and broader access wait for leases, gateways, revocation, and egress controls.

Phase 0

Complete

Research and boundary

Define the independent product, security posture, and clean-room identity.

Capability map
Architecture and trust model
Signal Yard brand direction

Phase 1

In validation

Private single-worker slice

Prove one operator can allocate, inspect, and release an isolated browser on Echo.

Private Compose stack
Session API and console
Runtime isolation evidence

Phase 2

Safe worker pool and gateway

Add leases, independent workers, scoped tokens, and authenticated browser transport.

Atomic allocation
Signed CDP/viewer grants
Reconciliation and egress policy

Phase 3

Planned

Profiles and observability

Introduce encrypted identity, artifacts, event timelines, and controlled human takeover.

Profile leases
Artifact storage
Redacted browser telemetry

Phase 4

Planned

Agent runs

Run bounded browser tasks with budgets, approvals, traces, and structured results.

Runner adapters
Run and step ledger
Independent cancellation

Phase 5+

Deferred

Browser tool platform

Build reusable browser jobs and broader platform controls only after the core is proven.

Rendered fetch and scrape jobs
Retries and quotas
Optional broader tenancy

EXPLICITLY DEFERRED

Not every possible feature belongs in the first yard.

KubernetesPublic raw browser endpointsGlobal proxy networkGuaranteed CAPTCHA solvingUndetectable fingerprint claimsGeneral-purpose serverless codeBilling and organizations