Chydio Chydio ID

CHYDIO FORGE · RELEASE ROADMAP

Desktop first.
Every screen in time.

The main Chydio Forge public release targets Windows and macOS together. Mobile begins as a responsive, installable web client; native iPhone, iPad, and Android companions come only after the service underneath them is proven.

Sequence, not a date promiseEvery phase has an exit gate. Native mobile apps are the final phase and do not ship with the first public desktop release.
MAIN RELEASE · 01

Windows

Production installer, safe updates, uninstall and repair paths, local service lifecycle, credential-vault integration, and release signing.

MAIN RELEASE · 02

macOS

First-class feature parity with Windows, Keychain integration, signed builds, Apple notarization, safe updates, and platform-specific test coverage.

THE FLIGHT PLAN

Five gated phases.

  1. 01

    FOUNDATION · IN PROGRESS

    Local Forge core

    General Unity package, shared local daemon, typed actions, checkpoints, permissions, receipts, provider adapters, CLI orchestration, packaging, onboarding, and repeatable verification.

    EXIT GATEWindows and macOS parity; signed/notarized release candidates; clean install, update, repair, and uninstall tests; no Kraylet-specific assumptions.
  2. 02

    REMOTE ACCESS

    Responsive web client + PWA

    A phone-, tablet-, and desktop-responsive web client that can be installed as a Progressive Web App. It reaches a user-approved desktop through the secure remote gateway; Unity and provider credentials remain on the user’s machine.

    EXIT GATEDevice pairing, revocation, per-command authorization, encrypted transport, reconnect safety, bounded offline behavior, session shutdown, and independent security review.
  3. 03

    PAID OPERATIONS

    Pro lifecycle + owner operations

    Managed Payments checkout, subscription changes, cancellation, expiry, refund and dispute handling, live entitlement checks, owner analytics, privacy requests, product support, and incident operations.

    EXIT GATEFinal owner/legal policies, eligible launch countries, verified support inboxes, tested billing sandbox, retention controls, observability, rate limits, budgets, and recovery drills.
  4. 04

    COLLABORATION

    Studio

    Hosted team sessions with paid seats, roles, approvals, handoffs, comments, audit history, and explicit project boundaries.

    EXIT GATETenant isolation, least-privilege roles, seat lifecycle, deletion/export, abuse controls, load testing, privacy validation, and an independent security assessment.
  5. 05

    FINAL PHASE · NATIVE MOBILE

    iPhone, iPad + Android companions

    Native companion apps for remote review, approvals, monitoring, and bounded commands after the PWA has validated the mobile workflow. They reuse the same secure gateway and do not become a second control plane.

    EXIT GATEAll earlier remote, billing, Studio, support/privacy, and independent-security gates remain green; Apple and Google store review, mobile threat modeling, secure local storage, push-notification privacy, and device revocation are verified.

PLATFORM LAW

One product.
Different windows.

Desktop does the work. Unity, files, executables, Git, tests, Play Mode, and provider CLIs run on an approved Windows or macOS development machine.

Web and mobile supervise. Remote clients request bounded actions through the gateway. They never receive another user’s provider credentials.

Local remains independent. Community workflows and self-hosted models do not require a paid Chydio subscription or permanent cloud connection.