SoulSynce

SoulSynce is a self-reported music streaming and store platform built around a "River" for discovering full songs and music videos, with features including Artist Worlds, alternate versions, comments, and song ownership. The author states that the platform is approaching beta with real users, registrations, and working listener behavior data. It was built by one person (Will Nelson) using React, Node.js, MongoDB, and OpenAI tools. The description indicates a focus on full-song discovery, artist identity, and ownership, but does not provide evidence of revenue, customers, or adoption beyond the author's claims.

The description states that SoulSynce is a music streaming and store platform built around:

• A "River" — a cinematic carousel for discovering original songs and music videos
• Artist Worlds — spaces where artists can publish albums, create versions, and connect with listeners
• Alternate versions of songs
• Comments on music
• Song pages
• Protected previews
• Analytics
• Installable PWA features

The platform allows listeners to preview songs, explore Artist Worlds, view alternate versions, comment, share individual song pages, and eventually purchase songs into their personal library.

Evidence The author's own write-up describes these features as part of the product. No independent verification or third-party confirmation is provided.

The author states that SoulSynce was inspired by the idea that music discovery should be more than endless playlists or short clips, aiming to create a place where full songs, artist identity, alternate versions, conversation, and ownership can coexist.

The platform positions itself as:

• A custom streaming and store platform
• Focused on full-song discovery
• Emphasizing artist identity and ownership
• Building toward a complete music ecosystem

Evidence The author's own write-up describes the inspiration and positioning. No external validation or market positioning data is provided.

The description states that SoulSynce targets:

• Listeners who want to preview songs, explore Artist Worlds, view alternate versions, comment, share individual song pages, and eventually purchase songs into their personal library
• Artists who can upload music, create versions, publish albums, and connect directly with listeners

Evidence The author's own write-up describes these user types. No data on customer segments or ICP validation is provided.

The description states that:

• Listeners can eventually purchase songs into their personal library
• Artists can upload music, create versions, publish albums, and connect directly with listeners
• The platform plans to add artist payouts and live song sales
• Payments are being finished as part of the beta stage

Evidence The author's own write-up describes these elements. No pricing information, revenue model details, or monetization data is provided.

The platform was built with:

• Frontend: React, Vite, JavaScript, HTML5, CSS3, PWA
• Backend: Node.js, Express, REST APIs, JWT authentication
• Database: MongoDB, MongoDB Atlas
• Media storage: Backblaze B2, Cloudflare Stream, protected media storage
• Analytics and tools: OpenAI Codex, PayPal

The author notes that challenges included:

• Securing preview vs. full media access
• Guest access limitations
• Ownership verification from unverified browser responses
• Responsive carousel layouts, audio/video playback, search, SEO, analytics accuracy, authentication issues

Evidence The author's own write-up describes the tech stack and challenges. No independent confirmation of delivery quality or technical performance is provided.

The author states:

• The platform is approaching beta
• It has real songs, real visitors, registrations, and working listener behavior data
• It includes a custom discovery River, Artist Worlds, alternate versions, comments, albums, song pages, protected previews, artist tools, analytics, and installable app features
• The next stage is beta with payments, song ownership, artist payouts, live music sessions, and live song sales

Evidence The author's own write-up describes these elements. No independent data on user engagement, retention, or actual usage metrics is provided.

The description does not provide any information about:

• Competitors
• Market positioning relative to existing platforms
• Differentiation from other music streaming services

Evidence Not evidenced. The author does not mention competitors or market context.

• Single-person team: The platform was built by one person (Will Nelson), which raises questions about scalability and long-term maintenance.
• Unverified claims: All traction, user data, and functionality are self-reported without independent verification.
• Technical complexity: The platform involves complex media handling, authentication, and ownership systems — all of which are described as challenges.
• Lack of revenue or monetization details: No evidence of monetization, pricing, or revenue generation is provided.
• Hackathon project: This was submitted to a hackathon, suggesting it may be in early development.

Evidence Inferences based on the author's own claims and the nature of a hackathon submission.

1. What specific metrics define "real visitors" and "working listener behavior data"?
2. How is user authentication and media ownership verified in practice?
3. What are the actual technical challenges that remain unresolved before full launch?
4. How does the platform plan to scale beyond a single developer?
5. What is the current status of payments, song ownership, and artist payouts?
6. Are there any existing partnerships or early adopters?
7. How does the platform differentiate from existing music streaming services?