Public web ecosystem
Build the GoreeCloud Projects, Glaze UI Design, Privacy Shield, Wardveil Security, Roadmap, Blog, and Archive websites with shared Glaze UI patterns and controlled Cloudflare Pages publication.
What GoreeCloud is building next.
This roadmap highlights major public-facing development priorities across GoreeCloud. It is intentionally higher level than internal task tracking: dates are not promises, priorities may change, and private infrastructure or security-sensitive work is omitted.
Active developmentPlannedFuture direction
Now
Active development
Work already underway across the platform.
Native GoreeCloud applications
Continue maturing original applications including Manager, Notes, Tasks, Contacts, Notify, Feed, and other focused services toward stable, independently maintainable releases.
Maintained open-source forks
Advance GoreeCloud Browser, Search, Network, Backup, Identity, DNS, and other maintained forks while reducing unnecessary third-party product identity and preserving upstream licensing.
Shared platform identities
Deepen Glaze UI, Wardveil Security, and Privacy Shield integration so GoreeCloud software shares consistent interaction, protection-state, privacy, and accessibility conventions.
Next
Near-term priorities
Publicly relevant work expected to follow current foundations.
Stable client releases
Expand tested Linux and Android delivery where a dedicated client meaningfully improves access while keeping web access available where appropriate.
Public documentation
Create sanitized, purpose-built documentation that teaches GoreeCloud architecture and software use without publishing internal records or sensitive implementation details.
Release and distribution experience
Make supported versions, release notes, verification guidance, and approved download paths easier to understand across GoreeCloud software.
Cross-project interoperability
Strengthen consistent identity, API, notification, status, and data-exchange conventions while preserving clear technical authority boundaries.
Later
Long-term direction
Strategic outcomes rather than scheduled commitments.
Local-first primary infrastructure
Move the center of gravity from rented infrastructure toward GoreeCloud-owned local systems while preserving resilient remote access, backups, and recovery.
Self-hosted source control
Move toward GoreeCloud-controlled source hosting while retaining GitHub for public collaboration, mirrors, and wider open-source participation.
Local AI independence
Expand locally operated AI, research, and automation capabilities while keeping models, data, workflows, and knowledge under GoreeCloud control.
Long-term digital continuity
Keep data, memories, documentation, credentials, and operational knowledge portable, recoverable, understandable, and transferable across changing technologies.
Direction without unnecessary promises.
Public by selectionOnly information approved for public disclosure appears here.
Purpose before expansionProjects exist for clear roles, not because capacity is available.
Privacy by defaultPublic progress never requires exposing private user or infrastructure data.
Evidence over labelsDevelopment, release candidate, and stable states remain distinct.