One consistent setup
A branded Windows installer brings the same settings, shortcuts and protection to each installation.
GROW UP ESPORTS / BROWSER PROJECT
Our community.
Our identity.
One browser.
A familiar browser with a Grow uP feel. A simpler setup, built-in DNS protection, and less day-to-day maintenance.
PROPOSED PLATFORM Powered by official Brave. Configured by Grow uP.
A FAMILIAR FOUNDATION. A SHARED IDENTITY.
Grow uP Browser ×+BUILT FOR OUR COMMUNITYGrow uP
TogetherPOWERED BY BRAVE · CONFIGURED BY GROW UP
Grow uP Browser ×← → ↻
♧ growup.gg
☰BUILT FOR OUR COMMUNITYGrow uPTogetherPOWERED BY BRAVE · CONFIGURED BY GROW UP
✓
Protection, by designManaged secure DNS
VISUAL CONCEPT · OPTIONAL START PAGE SHOWN
THE FOUNDATIONOfficial Brave+Grow uP identity+DNS protection+Automatic upkeep
01 / THE IDEA
Build the experience.
Keep the trusted engine.
Grow uP brings the setup, identity and management layer. Brave continues to handle the browser itself and its official security updates.
Less to maintain
Official Brave updates and automated Grow uP configuration reduce repetitive manual work.
Space to grow
Start with a focused release. Add community tools and richer experiences when the foundation is proven.
VERSION 1
The essentials, connected.
- Branded installer and Windows shortcuts
- Official Brave with a cleaner configuration
- Per-install registration and filtered secure DNS
- Automatic configuration maintenance
- Release automation, monitoring and recovery
- Black/red visual assets; optional lightweight theme
INTENTIONAL BOUNDARIES
A focused first release.
No custom browser engine or Brave fork. No preinstalled Claude extension, account-linked onboarding, device management portal or full device control.
Brave stays visible in its executable, About page and usually its taskbar identity. The Grow uP identity lives in the installer, shortcuts and optional theme.
02 / THE MEMBER EXPERIENCE
From setup to ready.
One installation flow. Familiar browsing afterwards. Explore the proposed journey below.
EXPERIENCE WALKTHROUGH↳
Your existing Brave profile stays yours. The plan preserves bookmarks, passwords and history. Removing Grow uP management should leave Brave and your profile in place.
03 / BEHIND THE EXPERIENCE
Four parts.
One connected platform.
No deep technical knowledge needed: each part has a clear job, from your computer to the services that keep it running.
The browser & setup
Brave handles websites, extensions and security updates. The Grow uP installer adds branding, selected settings and an installation ID.
Official BraveWindows installer
The protection layer
AdGuard Home checks website address requests against filtering rules. Azure hosts this service and the registration service.
AzureAdGuard Home
The maintenance layer
A scheduled task checks at startup and roughly every day. It verifies signed settings updates and repairs managed shortcuts or configuration.
Verified updatesRepair support
The release pipeline
GitHub stores the project and automates builds, checks and deployments. Monitoring, backups and rollback support ongoing operations.
GitHub ActionsAzure monitoring
DNS, IN PLAIN ENGLISH
A check before the connection.
DNS translates a website name into an address. The proposed Grow uP service filters these requests to help block known ad, tracker, malware and phishing domains.
Your browser→Grow uP DNS→Website
Secure DNS encrypts the lookup. It is one layer of protection, not a guarantee that every dangerous page or advert will be blocked.
What is being configured in Brave?+
Keep the useful tools
Shields, extension support, password management, developer tools and automatic updates remain available. Sync is optional.
Reduce distractions
The plan targets Rewards, Wallet/Web3, Leo, VPN, News and Talk for disabling through supported policies. Playlist is optional. Policy support must be validated before release.
04 / THE GROW UP IDENTITY
Recognisably ours.
Dark, confident and community-minded. Controlled red accents, clean geometry and practical language connect the browser project to Grow uP.
WE GROW UP TOGETHERPROJECT VISUAL DIRECTIONA complete visual system
The design workstream covers every touchpoint: Windows icons, installer artwork, browser theme, documentation graphics and support visuals.
Grow uP red#E10613Near black#0B0B0DCharcoal#14161A
Working palette from the plan. The official logo remains intact. Theme delivery is configurable for v1 or v1.1; a richer start page is a later option.
05 / DEVELOPMENT ROADMAP
A clear route to rollout.
Eight proposed phases, with a small real-world pilot before organization-wide release. This is a delivery sequence, not a claim of completed work.
THE PILOT GATE5–20 installations
Prove setup, DNS response times, update behaviour, readability and recovery on real devices before expanding.
↗How the development work is divided+
Eight workstreams can be assigned to developers or AI agents, with integration testing bringing their outputs together.
Brand & visual systemAzure infrastructureDNS serviceRegistration serviceWindows installerClient maintenanceRelease automationQA & integration
What must be true before launch?+
- Fresh install, upgrade, repair and removal work
- Existing Brave profiles stay intact
- Unique install IDs and filtering work
- DNS outage behaviour is verified
- Official browser updates continue
- Signed configuration updates are tested
- Branding stays readable and consistent
- Backup restore, alerts and rollback are proven
06 / RUNNING IT RESPONSIBLY
Built to be manageable.
Designed to be transparent.
Automation reduces routine work. Clear ownership, privacy choices and tested recovery keep the platform sustainable.
No account required
Each installation gets a random ID for registration, troubleshooting and statistics. No personal identity mapping is planned by default.
These IDs are pseudonymous, not proof of complete anonymity. Detailed DNS query retention should be minimized and documented.
Recovery is part of the plan
Monitoring raises alerts; backups and rollback support restoration. A public AdGuard secure DNS endpoint is proposed as an alternative.
Multiple DNS endpoints do not guarantee a strict primary-then-fallback order. Actual behaviour must pass testing.
Trust the update path
Signed installers and settings updates, restricted admin access, protected secrets and registration rate limits are planned safeguards.
This is a convenience-focused browser platform, not full device management or strong device authentication.
DAY TO DAY
Mostly automated. Still owned.
The operations team reviews alerts and failed releases, approves promotions where needed, maintains secrets and checks backup health.
When something goes wrong+
Registration unavailable: existing installations can continue; new setups may temporarily need a fallback. Restore the service and verify ID creation.
DNS unavailable: restore service and inspect logs; confirm tested alternative DNS behaviour.
Theme issue: stop distribution or roll it back while keeping browsing functional.
COST & SCALE
Start small. Measure demand.
The initial plan proposes one small Azure B1ms server in Spain Central, plus storage, public IP, monitoring, backups, code signing and applicable build usage.
No budget or delivery dates are confirmed. Scale when CPU, memory, registration demand or DNS latency justify it; first options include a larger server and a second DNS instance.
07 / WHAT COMES NEXT
A foundation for more.
Once the core works reliably, Grow uP can add community features without rebuilding the browser.
01Branded start page & curated links OPTIONAL
02Lightweight community utility extension FUTURE
03Group filtering & regional DNS endpoints FUTURE
04Support portal & richer operational insights FUTURE
05Optional Workspace-aware features FUTURE
THE PRACTICAL QUESTIONS
Good to know.
Is this a new browser built from scratch?+
No. It uses the official Brave browser. Grow uP adds its installer, settings, branding, DNS service and maintenance layer. Avoiding a browser fork keeps official security updates and reduces long-term maintenance.
Can I download the browser here?+
This site explains the proposed development project. It does not distribute a finished installer or represent live protection services. A tested, signed installer is a future project deliverable.
Does this protect every app on my computer?+
The plan configures secure DNS in Brave. It does not claim whole-device filtering or protection for every app. It also does not replace normal device security practices.
Can Grow uP settings be removed later?+
The planned uninstaller removes Grow uP policies, maintenance tasks, shortcuts, management files and any managed theme. Brave itself and user data should remain intact; this behaviour is part of release testing.
What still needs a decision or technical validation?+
Confirm the theme delivery method and release timing, supported Brave policies, real DNS fallback behaviour, privacy and retention settings, code-signing arrangements, operating ownership, budget and schedule before production rollout.