Ownership, privacy, and recoverability become the core
GoreeCloud begins as a personal-cloud effort centered on direct control of infrastructure, data, software, identity, and long-term preservation.
GoreeCloud Archive
Preserving the evolution of GoreeCloud.
A curated public record of major milestones, architectural eras, product transitions, and the long-term development of the GoreeCloud personal and family cloud platform.
Services become a coherent ecosystem
Networking, storage, backups, monitoring, identity, productivity, and public-facing services are organized into defined system roles and architecture boundaries.
Upstream applications become stepping stones
Early GoreeCloud development uses maintained forks and upstream applications to accelerate capability, preserve continuity, and learn product requirements. Over time, first-party domain models, interfaces, data contracts, release engineering, and application logic increasingly move into GoreeCloud-owned source while attribution and migration paths remain preserved.
Focused first-party applications multiply
Projects for Mail, Music, Photos, Video, Drive, Sync, Location, Launcher, Calendar, Tasks, Contacts, Notes, Monitor, Network, DNS, Browser, Backup, Identity, Changelogs, Messenger, AI, and other roles establish a broader GoreeCloud Suite with deliberately separated responsibilities.
Storage, transfer, location, and device software gain first-party foundations
Drive advances beyond planning into an authorization-first native file platform, Sync establishes a native secure-transfer foundation, Location develops a private multi-user tracking model, Launcher grows into a first-party Android HOME experience, and upstream-derived media and device projects become explicit native-rebuild targets.
Glaze UI becomes the shared design language
GoreeCloud standardizes visual hierarchy, interaction states, accessibility, adaptive layouts, and recognizable product-family presentation across web, mobile, tablet, desktop, and TV experiences. Glaze UI 1.4 becomes the current Stable production target; older consumer pins require controlled migration rather than grandfathered production exceptions.
Wardveil Security, Privacy Shield, and Everkeep gain distinct platform roles
Security presentation, privacy controls, and long-term resilience receive separate identities so each can evolve without blurring technical authority or product responsibilities. Together with Glaze UI, they are integral platform systems rather than decorative branding.
Current contracts and evidence become part of public truth
Formal platform policies establish that Glaze UI conformance follows the current Stable contract and that Privacy Shield, Wardveil Security, and Everkeep claims must remain tied to implemented behavior, current authoritative evidence, and the correct acceptance scope. Unknown, degraded, migration-required, and pending states stay visible instead of being replaced by stronger labels.
Fold identity and the first persistent Drive milestone land
The approved Fold mark becomes Glaze UI's canonical visual identity, GoreeCloud Drive reaches PostgreSQL-backed persistent file/folder metadata CRUD with authorization enforcement, Search advances through RC #09 validation, Notify merges its Linux/Debian and Android client source foundation, and Terminal reaches the 50.2-rc.2 source line. These milestones preserve the distinction between merged source, release candidate, production, and Stable acceptance evidence.
Original GoreeCloud software becomes the required application end state
GoreeCloud formalizes native-from-the-ground-up development as the mandatory product model for every GoreeCloud application. Maintained forks and adopted complete application codebases become controlled transitional migration, compatibility, testing, historical, or reference sources only. Narrow mature technical foundations may remain where replacing them would materially increase security, standards, protocol, codec, rendering, runtime, or interoperability risk. Glaze UI, Wardveil Security, Privacy Shield, and Everkeep become mandatory Stable-release gates.
Bookmarks establishes an original GoreeCloud foundation
An original Go foundation for GoreeCloud Bookmarks is integrated with owner-scoped records, bounded input rules, cross-owner isolation tests, native service boundaries, and PostgreSQL persistence/runtime contracts progressing through validated source work. The Linkwarden-derived application and Browser capture path remain transitional continuity surfaces, and no native production cutover is implied by the source milestone.
Glaze UI makes color a functional language
Glaze UI defines shared semantic roles for interface, status, connectivity, protection, warning, danger, and synchronization meaning while requiring important state to remain understandable without color alone. Security, privacy, and resilience authorities retain ownership of their underlying claims.
GoreeCloud AI becomes the native AI product direction
GoreeCloud AI is defined as the first-party conversation, Workspace, knowledge, RAG, research, files, tools, and orchestration application. Ollama remains the local model runtime and GoreeCloud Search becomes the first-party Internet-research provider. Open WebUI, AnythingLLM, and SearXNG become replacement targets rather than intended long-term AI dependencies.
GoreeCloud Mesh connects platform relationships without taking authority
Mesh advances as the coordination and governance plane for service and capability registration, explicit relationships, dependency context, policy decisions, lifecycle events, and evidence-aware interoperability. Specialized systems remain authoritative for their own state, and Mesh cannot manufacture stronger conformance, privacy, security, or recovery claims.
Stale evidence stops supporting current claims
Glaze UI, Privacy Shield, and Wardveil Security formalize producer-authoritative validity boundaries and CI enforcement for protected or conformant evidence. A previously passing result cannot silently remain current after its validity window expires or the producer can no longer support the claim.
Self-hosted Gitea becomes the planned permanent authority
GoreeCloud selects self-hosted Gitea as the planned permanent authoritative source-control and development platform. GitHub remains a transitional migration source and optional interoperability surface, while GoreeCloud-controlled runners are intended to own routine CI/CD compute and evidence.
AI source, Mesh durability, and native Search contracts become concrete
The first goreecloud-ai repository establishes native Ollama-front-end source designed with Glaze UI and Wardveil Security. Mesh adds fail-closed scoped private API authorization, producer-bound evidence validity, and durable Everkeep recovery-evidence persistence. GoreeCloud Search adds fail-closed native category request and readiness contracts with accessible category controls. These are source and contract milestones and do not automatically imply Stable or production acceptance.
First-party feature systems gain memorable identities
Quill, Waypoint, Beacon, Conduit, Courier, Resonance, and Keepsake organize major application-specific capabilities for Keyboard, Tasks, DNS, Network, Mail, Music, and Photos while keeping the product names intact.
GoreeCloud opens a broader public knowledge surface
The main website plus Projects, Design, Privacy, Security, Roadmap, Blog, and Archive create a coordinated Cloudflare Pages portfolio without exposing private operational records.
Archive policy
Public history is curated, not mirrored.
The Archive preserves selected public milestones and context, including superseded development models when they are necessary to understand the project's evolution. It does not mirror internal change logs, credentials, private topology, operational details, personal information, or historical material that was never approved for public release.