90f2c99a60
- Source: inbox/archive/2026-03-03-futardio-launch-open-music.md - Domain: internet-finance - Extracted by: headless extraction cron (worker 4) Pentagon-Agent: Rio <HEADLESS>
36 lines
No EOL
1.9 KiB
Markdown
36 lines
No EOL
1.9 KiB
Markdown
---
|
|
type: entity
|
|
entity_type: company
|
|
name: Open Music
|
|
domain: internet-finance
|
|
status: failed
|
|
founded: 2025
|
|
website: https://openmusic.art
|
|
twitter: https://x.com/openmusic_art
|
|
key_metrics:
|
|
futardio_raise_target: "$250,000"
|
|
futardio_raise_committed: "$27,533"
|
|
futardio_raise_outcome: "REFUNDING"
|
|
team_size: "2 full-stack developers"
|
|
monthly_burn: "$25,000"
|
|
tracked_by: rio
|
|
created: 2026-03-11
|
|
---
|
|
|
|
# Open Music
|
|
|
|
Artist-first music streaming platform on Solana that attempted to replace Spotify's pro-rata pool model with direct listener-to-artist payments. Launched futarchy-governed fundraise on Futardio in March 2026, raising only 11% of $250K target before going to REFUNDING status.
|
|
|
|
## Overview
|
|
|
|
Open Music proposed a streaming platform where subscriber payments go directly to artists based on individual listening time rather than being pooled globally. The model promised ~$128/month for 100 fans versus ~$9/month on Spotify. Platform included AI-powered sonic discovery, artist audience ownership, and Solana/USDC payment infrastructure. Had working MVP at openmusic.art with early artist onboarding.
|
|
|
|
## Timeline
|
|
- **2025-Q4** — MVP launched at openmusic.art with artist upload and payment functionality
|
|
- **2026-03-03** — [[open-music-futardio-fundraise]] launched on Futardio seeking $250K for 10-month runway
|
|
- **2026-03-04** — Fundraise closed in REFUNDING status with $27,533 committed (11% of target)
|
|
|
|
## Relationship to KB
|
|
- [[futardio]] — fundraising platform
|
|
- [[futarchy-variance-creates-portfolio-problem-because-mechanism-selects-both-top-performers-and-worst-performers-simultaneously]] — case study in futarchy selection variance
|
|
- [[futarchy-governed-permissionless-launches-require-brand-separation-to-manage-reputational-liability-because-failed-projects-on-a-curated-platform-damage-the-platforms-credibility]] — counterexample showing platform survived failed launch |