Concept only · Read-only first
A WINDOW, NOT A SECOND DESKTOP APP
Show selected work.Keep the library at home.
A future browser view for content you explicitly choose to make available away from your desktop. Creator Vault AI remains the local-first core and source of truth.
NO PUBLIC LOGIN · NO WEB VAULT · NO UPLOAD · NO SYNC · NO LIVE GUEST LINK
Concept roles
Three views, each with a deliberately narrow job.
The first version—if approved and built—should prove safe viewing before attempting editing, uploading, or broad collaboration.
The cards below explain future roles. They do not create sessions, permissions, or share links.
Owner view · Concept
Review what you deliberately exposed
A future owner surface could show only the content selected for remote access, plus clear availability and source-status information.
Guest viewer · Concept
Present selected work without exposing the library
A future guest view could display a deliberately prepared set without revealing unrelated folders, metadata, account details, or the desktop library.
Read-only first · Principle
Prove trust before adding power
Editing, deletion, upload, synchronization, comments, and collaboration would expand the privacy and security surface and remain outside this concept.
Trust sequence · Future requirement
Remote access starts with explicit consent.
Before a real Web Companion exists, every step below requires a verified technical contract. The public concept page does not implement any of it.
Select content locally
The user chooses the exact files or prepared collection that may become remotely visible.
Review what leaves the device
The interface must state which bytes, thumbnails, metadata, and permissions are included before transmission.
Apply access controls
Identity, expiry, revocation, authorization, and audit behavior require a dedicated security review and Owner GO.
Revoke without ambiguity
A future system must make it clear what stops being accessible, what remains stored, and what is deleted.
Red-gated work · Not authorized here
What a real implementation would still need.
A polished static page is not proof of a secure remote library. These systems remain unbuilt or unapproved for public access in this website phase.
Identity must be real, revocable, and tested
No public StarBase Web Companion login is enabled. MFA, account recovery, session expiry, device management, and abuse controls require a separate plan.
User files cannot be treated like demo assets
Storage location, encryption, retention, deletion, backups, and regional behavior require explicit architecture and privacy review.
A guest link is a security system
Scope, expiry, revocation, download policy, forwarding risk, and access logs must be designed before a real share surface appears.
Production access needs monitoring and response
Rate limits, alerting, abuse response, support, data export, and incident handling are part of the product—not optional backend details.
LOCAL FIRST. REMOTE ONLY BY CHOICE.
Explore the idea without confusing it with a live service.
Return to the current Creator Vault AI product, or compare every StarBase surface and its actual status. The purchase below is for Creator Vault AI Early Access only; it does not unlock StarBase Web Companion.