> 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/technology/2.-technology-overview/2.1-platform-architecture.md).

# 2.1 Platform Architecture

Cryptic is built as a connected product stack across **Mobile, Desktop and SDK**

Each layer has a clear role: the SDK provides the protocol foundation, Desktop creates the power-user workspace, and Mobile delivers the everyday consumer experience.

**1. Consumer Layer — Cryptic Mobile**\
Cryptic Mobile is the consumer-facing application.

It gives users access to secure communication, wallet functionality, payments, QR flows, card access, and everyday crypto-native use

Mobile keeps the experience simple while connecting users to the broader Cryptic product stack.

**2. Power-User Layer — Cryptic Desktop**\
Cryptic Desktop is the native desktop client built on top of the SDK.

It combines post-quantum secure communication with wallet actions, token swaps, lending, privacy tools, permanent file storage, encrypted notes, and ecosystem integrations in one application.

Desktop is designed for users and teams that need more than a mobile chat experience: traders, developers, DAO operators, community managers, power users, and enterprise teams.

**3. Protocol Layer — Cryptic SDK**\
The Cryptic SDK is the foundation of the product stack.

It handles post-quantum cryptography and server transport, allowing developers, applications, protocols, teams, and future agent-based systems to create encrypted direct messages and group rooms without building cryptographic infrastructure from scratch.

The SDK is intentionally headless. It does not own user interface, storage, wallets, push notifications, or business logic. Those remain with the host application.

#### **Infrastructure Components**

**Post-Quantum Communication**\
Cryptic uses modern post-quantum cryptography, including ML-KEM and ML-DSA based primitives, to support encrypted communication and key exchange.

**Blockchain & Payment Infrastructure**\
Solana provides fast, low-cost transaction infrastructure, with additional blockchain and payment integrations supported through the broader product roadmap.

**Key Management**\
Cryptic is designed around non-custodial key control, secure identity handling, and platform-specific secure storage where applicable.

**API & Transport**\
Authenticated REST APIs and WebSocket transport support real-time encrypted communication between clients and Cryptic infrastructure.

**Storage & DeFi Integrations**\
Desktop integrations can support workflows across swaps, lending, privacy tools, encrypted storage, and other ecosystem services.

> *Cryptic’s architecture is designed to separate the application experience from the protocol layer, allowing the same secure communication foundation to power Mobile, Desktop, and third-party integrations.*


---

# 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:

```
GET https://cryptic-documentation.gitbook.io/cryptic-documentation/technology/2.-technology-overview/2.1-platform-architecture.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.