> For the complete documentation index, see [llms.txt](https://cryptic-documentation.gitbook.io/cryptic-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cryptic-documentation.gitbook.io/cryptic-documentation/project/1.-project-overview/1.6-roadmap.md). # 1.6 Roadmap {% stepper %} {% step %} ### Phase I: Protocol Foundation & Product Alignment **Now → Q3 2026** Cryptic’s first priority is to harden the core protocol layer and align the product stack across **SDK, Desktop, and Mobile**. This phase focuses on making the Cryptic SDK production-ready for broader developer adoption, while bringing Desktop and Mobile into tighter alignment with the same post-quantum secure communication architecture. Key priorities include: * publishing the Cryptic SDK for developer use * aligning mobile cryptography with final **FIPS 203 / 204** standards * integrating the SDK as the shared communication layer across products * strengthening cryptographic identity flows across SDK, Desktop, and Mobile * improving encrypted data transfer between supported product surfaces * adding Signal-style Double Ratchet for stronger forward secrecy * improving identity backup and recovery flows * preparing Desktop distribution for macOS and Windows * moving feature-flagged Desktop modules toward production readiness * preparing confidential AI workflows for secure Desktop use cases where applicable The goal of this phase is to strengthen the foundation before scaling adoption. {% endstep %} {% step %} ### Phase II: Ecosystem & Interoperability **Q3 2026 → Q4 2026** Once the protocol layer is hardened, Cryptic expands into third-party integration and ecosystem growth. This phase focuses on making the Cryptic SDK easy for developers, protocols, teams, and agent systems to integrate. Key priorities include: * public SDK documentation and developer guides * React Native and web SDK packages * AI agent room templates for secure human-to-agent and agent-to-agent coordination * encrypted payload transfer between users, teams, applications, and agents * agent identity and permission models for controlled coordination flows * self-hosted deployment guides for enterprise and protocol teams * room permissions, admin controls, and production group management * plugin support for message types such as files, payments, locations, approvals, and agent actions * multi-device sync and encrypted backup improvements * Desktop plugin architecture for custom integrations * integration examples for agent frameworks and crypto-native workflows The goal of this phase is to make Cryptic usable beyond its own apps, allowing partners and developers to build on the secure communication, identity, and payment coordination layer. {% endstep %} {% step %} ### Phase III: Protocol Evolution & Security Hardening **Q4 2026 → Q1 2027** Cryptic then moves into deeper protocol upgrades across SDK, Desktop, Mobile, and server infrastructure. This phase focuses on improving trust, resilience, and long-term security across the full product stack. Key priorities include: * wire format v2 across all products * server-side replay protection and nonce improvements * stronger group epoch enforcement * server-side verification for post-quantum invite signatures * Key Transparency to detect server-side key substitution * sealed-sender style routing to reduce metadata exposure * message padding to reduce traffic analysis * formal key-commitment improvements for encrypted messages * stronger verification flows for cryptographic identity and agent-based coordination * improved controls for encrypted data transfer and permissioned actions The goal of this phase is to mature Cryptic’s security model for more demanding users, developers, partners, agent systems, and enterprise deployments. {% endstep %} {% step %} ### Phase IV: Growth, Monetization & Distribution **Q1 2027+** With the protocol and product layers hardened, Cryptic expands distribution and monetization across consumer, developer, partner, enterprise, and agent-based channels. This phase focuses on turning the product stack into a sustainable ecosystem. Key priorities include: * SDK adoption through npm, documentation, GitHub, and developer outreach * Desktop distribution through macOS and Windows channels * Mobile growth through App Store and Play Store distribution * enterprise self-hosted licenses * priority API access for teams, developers, and agent systems * premium mobile and desktop features * confidential AI workflow plans where applicable * vault storage revenue through encrypted storage workflows * card and on-ramp related revenue streams * partner integrations across wallets, DeFi, storage, payments, privacy, onboarding, AI infrastructure, and agent frameworks * white-label and custom integration opportunities The goal of this phase is to grow Cryptic from a product suite into a broader secure communication, cryptographic identity, and payment infrastructure ecosystem. Roadmap items are indicative and subject to change based on technical, regulatory, product, and market conditions. {% endstep %} {% endstepper %} {% hint style="info" %} *Roadmap items are indicative and subject to change based on technical, regulatory, product, and market conditions.* {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://cryptic-documentation.gitbook.io/cryptic-documentation/project/1.-project-overview/1.6-roadmap.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.