GoreeCloud is moving from a collection of self-hosted tools toward a cohesive personal and family cloud whose GoreeCloud application layer is original, native-from-the-ground-up software. Existing upstream applications may remain temporarily for migration, continuity, compatibility, testing, or reference, while narrowly scoped mature technical foundations can remain where replacing them would materially increase security, standards, protocol, codec, rendering, runtime, or interoperability risk. This public roadmap stays intentionally higher level than internal task tracking: dates are not promises, priorities may change, and private infrastructure or security-sensitive work is omitted.
Work already underway across the platform.
The main GoreeCloud site plus Projects, Design, Privacy, Security, Roadmap, Blog, and Archive form the current public Cloudflare Pages portfolio. The current phase is richer information, accessibility, navigation, mobile and desktop refinement, and stronger cross-site consistency.
Every GoreeCloud application now has the same required end state: original GoreeCloud-owned software at the product and application layer. Maintained forks and adopted complete application codebases are transitional migration, compatibility, testing, historical, or reference sources only. Existing production continuity is preserved until native replacements satisfy their separate migration and acceptance gates.
Manager, Notes, Tasks, Calendar, Contacts, Notify, Feed, Mail, Music, Changelogs, GitHub Dashboard, Drive, Sync, Location, Launcher, Messenger, and other focused applications are advancing as original GoreeCloud software rather than one oversized monolith.
Browser, Search, Network, DNS, Backup, Bookmarks, Photos, Video, Vault Server, Terminal, Gallery, Memos, and other upstream-derived lines are controlled native-rebuild targets. Their current upstream-derived code may remain only where needed for service continuity, migration, compatibility, rollback, security maintenance, testing, or reference while first-party implementations replace the inherited product layer.
Glaze UI, Wardveil Security, Privacy Shield, and Everkeep are mandatory integral systems across the GoreeCloud application portfolio. Glaze UI 1.4 is the current Stable production target; security, privacy, resilience, recovery, preservation, portability, and continuity states remain evidence-backed rather than decorative claims.
No GoreeCloud application qualifies for Stable while a required Glaze UI, Wardveil Security, Privacy Shield, or Everkeep integration is missing, incomplete, superseded, outdated, unverified, or unaccepted for its supported scope. Older consumer contracts require controlled migration rather than production grandfathering.
The approved Fold mark is the canonical Glaze UI visual identity, with authoritative standalone, monochrome, and horizontal-lockup SVG sources plus deterministic derivative-generation rules for websites, documents, profiles, favicons, and application surfaces.
Application-specific umbrella identities organize major first-party features, including Quill for Keyboard, Waypoint for Tasks, Beacon for DNS, Conduit for Network, Courier for Mail, Resonance for Music, and Keepsake for Photos.
GoreeCloud Drive persists file and folder metadata in PostgreSQL and applies trusted-principal plus Space-membership authorization to node creation, reading, updating, and deletion. The milestone preserves fail-closed service enforcement, Drop-only privacy, and strict request validation.
GoreeCloud Bookmarks has integrated an original Go foundation with owner-scoped records, bounded validation, cross-owner isolation tests, native service boundaries, and PostgreSQL persistence/runtime contracts progressing through validated source work. The Linkwarden-derived application and existing Browser capture path remain transitional continuity surfaces; no native production cutover is claimed.
Drive has moved beyond initial planning into an authorization-first native storage foundation, Sync has its native foundation merged, and Location is advancing a private multi-user tracking architecture with native Android collection.
Search is validating RC #09 while its required native replacement direction remains explicit. Notify has merged its first-party Linux/Debian and Android client source foundation while persistent Android delivery and production cutover remain separate gates. Terminal is on the 50.2-rc.2 source line, with the current implementation transitional and Stable approval still explicitly separate.
GoreeCloud Browser continues as a privacy-first transitional Firefox-derived line while moving toward an original GoreeCloud application layer. A dedicated Firefox Extensions repository provides a canonical home for GoreeCloud-maintained browser extensions and integration components.
Publicly relevant work expected to follow current foundations.
Advance upstream-derived projects through original domain models, authenticated service boundaries, durable storage, migration contracts, portability, recovery, and representative runtime acceptance without prematurely cutting over current services.
Expand tested Linux and Android delivery where dedicated clients improve access, while retaining strong web experiences and clear release-lifecycle evidence.
Strengthen deliberate interoperability such as Tasks and Calendar, Drive and Sync, shared identity, notifications, APIs, portability, current-Stable Glaze UI behavior, and the latest approved Privacy Shield, Wardveil Security, and Everkeep contracts without creating unnecessary coupling.
Continue building the active Drive and Sync foundations into durable multi-user file-management and transfer experiences, while developing a dedicated GoreeCloud Documents direction without recreating an oversized all-in-one cloud product.
Advance Launcher, Keyboard, Terminal, Browser clients, and other device software through build, packaging, accessibility, real-device or workstation acceptance, and controlled release gates.
Create sanitized, purpose-built guides and architecture explanations without publishing internal records, credentials, private topology, or operationally sensitive detail.
Make supported versions, release notes, verification guidance, platform packages, and approved download paths easier to understand across GoreeCloud software.
Expand the public Blog, Archive, Changelogs, and Autobiography surfaces so GoreeCloud's technical decisions, lessons, milestones, and long-term evolution remain understandable over time.
Strategic outcomes rather than scheduled commitments.
Move the center of gravity from rented infrastructure toward GoreeCloud-owned local systems while preserving resilient remote access, backups, and recovery.
Move toward GoreeCloud-controlled source hosting while retaining GitHub for public collaboration, mirrors, and wider open-source participation.
Expand locally operated AI, research, and automation capabilities while keeping models, data, workflows, and knowledge under GoreeCloud control.
Complete the transition to original GoreeCloud applications at the product layer while retaining only narrowly justified mature technical dependencies and standards-compatible foundations.
Keep data, memories, documentation, credentials, software, and operational knowledge portable, recoverable, understandable, and transferable across changing technologies.