--- title: The product site, web renderer, and desktop delivery are separate description: How to distinguish informational web pages, browser rendering, and Mac package channels without implying deployment or release guarantees. url: https://docs.thegram.one/ko/architecture/web-and-distribution/ lang: en requested_lang: ko fallback_from: https://docs.thegram.one/architecture/web-and-distribution/ tier: current status: component: Thegram Desktop (macOS), Thegram for iOS, Vault web app, and Web viewer deployment: Mac distribution route not publicly verified; iOS App Store; Vault at vault.thegram.one; viewer endpoint unverified applies_to_version: Latest status: Unverified last_verified: null owner: thegram-one/thegram-web public_evidence: [] rationale: Canonical r10 records that viewer.thegram.one and thegram-web-render were retired on 2026-10-16; the page still cites a public DMG endpoint, but https://thegram.one/download/mac returns 410 Gone, and the remaining desktop and App Store claims have no public evidence. source: https://docs.thegram.one/sources/web-and-distribution.gram date_published: "2026-10-12T08:09:40.263Z" date_modified: "2026-10-15T21:34:28.617Z" evidence: Canonical source SHA-256: fbee491f1d1d72eec0b4b1f42e82d07c4145502202d93334aa793bbd999dd0d4 Canonical source: thegram-blog/content/web-and-distribution.gram Selected revision: r10 2026-10-15T21:34:28.617Z thegram-viewer-retirement Live publication before migration: r9 2026-10-12T13:08:42.318Z --- # The product site, web renderer, and desktop delivery are separate
## Three web surfaces and the native clients {#h0-1} **Retirement notice — 2026-10-16:** `viewer.thegram.one` and `clab-one/thegram-web-render` have been retired. The renderer discussion below is a historical source comparison, not a current service or download route. Open .gram files at https://vault.thegram.one/ or in a native Thegram app. Thegram has the product and installation site, the account-backed Vault web app at vault.thegram.one, and native Mac and iOS clients. The retired `viewer.thegram.one` renderer was a separate ephemeral submission surface, distinct from Vault's account-backed access. These surfaces have different identity, persistence, and delivery boundaries; statements about one do not establish availability, privacy model, or release status of another. The `thegram-web` README describes a static site with pages for product information, install instructions, legal terms, privacy, and download guidance. Static content can explain how to obtain an application, but does not itself build or ship that app. Its README documents an intended cluster route and deployment setup alongside the source; repository configuration is not independent proof that a particular deployment is currently healthy or accessible. ### Browser reading is a request, not a hosted workspace {#h0-4} The retired `thegram-web-render` source documented a no-login, ephemeral viewer. At the time described by that source, a user could paste or upload a .gram file, inspect its document or dashboard view, and navigate history. It described submission via POST, ephemeral processing, and no retention for later retrieval. This is historical source material, not an available route; the current web route for opening account documents is Vault at vault.thegram.one. ### Native package routes {#h0-6} The primary desktop repository README states a public Mac version and points to the public DMG endpoint. The separate sandboxed Mac App Store edition is in preparation, with App Store entitlements, a privacy manifest, and installer-signing work; no App Store release is evidenced. Its README and acceptance file are inherited from the desktop line and retain a Source-r2 TEST/UNRESOLVED-license boundary, not a statement of App Store release status. Use the generated [platform release reference](/platform/platform-release/) for current desktop release fields. Core license status remains UNRESOLVED; notarization does not imply license review. These facts must remain separate. A public download URL in a README does not by itself establish current status of every package, its license conditions, or store availability. For iOS, the reviewed feature branch describes a read-only iPhone/iPad viewer, including read-only account documents from Thegram Vault and Google Drive. That revision is on `frontend/figma-mobile-refinement`, not `main`; the product homepage labels the current route a TestFlight beta. Website wording is time-sensitive; readers should follow the current official page rather than infer an App Store release. iOS import behavior differs from desktop editing and from the renderer’s upload flow. ### Example: choose the right route {#h0-9} A Mac user preparing a decision brief can edit the canonical file in Desktop, preserving its history. A reviewer can open account documents through Vault or a native Thegram app. A link to the public product page is for instructions and discovery, not a private document URL. A team that needs shared storage should evaluate Vault authorization separately. ### Distribution and evidence boundaries {#h0-11} A distribution claim should name its channel (public DMG, App Store edition in preparation, TestFlight invitation, account-backed Vault web app, or native app), owning source revision, and evidence date. The renderer description below is a historical source comparison, not evidence of a current service. A website may be static source; a package may be signed but blocked from release; a service may have deployment manifests without a live health check. These are different evidence classes. Do not turn a package README into a live availability claim, or write that a site or service was deployed unless deployment evidence was actually checked. ### Evidence {#h0-13} Source records below identify the public product page and the reviewed Desktop, App Store, iOS, and retired renderer material. Repository configuration alone does not prove current deployment or release availability. ### Sources {#h0-15} The comparison follows the checked website, native clients, sandboxed App Store edition in preparation, iOS, and historical renderer source material. ## Source
**Source:** Static product website README Internal source reviewed at revision 944ad8fb276bf14c50268816a85b779856b90406 on branch main (README.md); not publicly available.
**Source:** Desktop product README Internal source reviewed at revision b6c769a0365166ba943d8501abb639bd09c00c6e (main: README.md); not publicly available.
**Source:** Mac App Store edition README; not release evidence Internal source reviewed at revision b3389ce165fa80d46873df3f4fb6951d98fbeb60 (main: README.md; inherited from the desktop line); not publicly available.
**Source:** App Store acceptance text; not release evidence Internal source reviewed at revision b3389ce165fa80d46873df3f4fb6951d98fbeb60 (main: docs/acceptance.md; inherited from the desktop line); not publicly available.
**Source:** iOS read-only viewer and account document flow Internal source reviewed at revision df70e4593da82cfae107e989bf029c21bbd42580 on branch frontend/figma-mobile-refinement (not main; README.md; App/Sources/Account/VaultAccount.swift); not publicly available.
**Source:** Current public product homepage Reference: [https://thegram.one/](https://thegram.one/)
**Source:** Existing renderer API contract Internal source reviewed at revision 971a0474fb4b97c3d23d6687be80664461f43a2f (main: docs/api.md); not publicly available.
## Knowledge
**Knowledge:** Product site, renderer and native clients have different roles Product-site information, account-backed Vault web documents, byte-submission rendering, and local application workflows have distinct persistence and delivery boundaries.
**Knowledge:** Distribution labels can conceal different release gates Public DMG, sandboxed Mac App Store edition in preparation, TestFlight beta, account-backed Vault web app, and ephemeral browser renderer are different channels; identify each source and date. Reference: [→ Supports: Product site, renderer and native clients have different roles](#e0-surface-separation)
**Knowledge:** Do not infer deployment from configuration alone Public availability requires current service or release evidence, not only a repository URL or manifest. Reference: [→ Supports: Product site, renderer and native clients have different roles](#e0-surface-separation)