Connected work across the music business

Problems we are designing for

• Career work is spread across people and tools

  Connect artist, team, projects and relevant context

  Artist and team

• Representation and permissions are difficult to establish

  Organize evidence, authority and approvals

  Rights and permissions

• Discovery does not always become an ongoing relationship

  Offer a clear, chosen path to continued participation

  Fan relationships

• Venue, schedule and audience activity become disconnected

  Connect venue, event, artist and participation context

  Live and venues

• Media use after a performance needs coordination

  Link approved media to its source activity and permissions

  Media workflow

• Commercial activity is difficult to understand together

  Connect applicable terms, activity and reporting

  Commerce

• Artists need continuity across established services

  Support chosen existing, Raw-native and partner services

  Artist control

• Music careers require practical business knowledge

  Explain planning, funding, merchandise and professional responsibilities

  Learning

Three example journeys

• Artist and authorized team

  Artist or project → authorized team → organized music context → coordinated next action.

• Venue music request

  Guest discovery → enabled Jukebox request → supported playback records → optional artist following.

• Performance to continuing relationship

  Show → approved media → supported distribution → chosen continued engagement.

Workflow illustrations are not live demonstrations or documented case studies.

Rights and permissions

Raw Rights organizes evidence, authority and approvals behind music. Artists retain the rights they actually hold and grant scoped permissions; the product does not transfer third-party rights or ownership of fans' personal information.

Media workflow

Approved recordings, broadcasts, clips and distribution paths should stay linked to the performance, permissions and people that authorized them. Raw Media describes what can happen around and after a performance—not every named feature is deployed today.

Artist control

Raw supports artists' existing brands, websites, social channels, fan communities, ticketing, merchandise and other chosen services. Authorized managers, labels, publishers, agents and distributors remain part of the professional picture.

• Outbound link

  Raw points to an existing artist website, store or channel without claiming data integration.

• Import / export

  Structured movement of approved information between systems when a workflow supports it.

• API integration

  Programmatic connection where credentials, scopes and ownership are explicitly established.

• Supported shared workflow

  A coordinated path inside Raw where permissions, records and handoffs are designed together.

We do not show partner logos or claim integrations that are not established in the application register.

Commercial model

Commercial terms remain program-specific. Fan payment, artist proceeds, platform fees, third-party costs, refunds and contractual allocations are explained separately. Any 10,000-fan example remains an illustrative model, not measured adoption or promised earnings.

Ciright and KEYRA are related implementation and identity surfaces for The Raw Network. An implementation relationship is not proof of every integration.

Supporting technology

Raw remains the music-facing brand. Ciright Core is the shared business foundation. KEYRA supports identity and authorization. Sansar is the immersive experience layer.

• The Raw Network

  Music-facing product and public brand

  Artists, fans and industry participants encounter Raw for discovery, relationships, live work and commerce.

• Ciright Core

  Shared business foundation

  Core holds business records, relationships and permissions that multiple programs can use. Database internals stay out of the public surface narrative.

• KEYRA

  Identity and authorization

  Supported sign-in and scoped permissions for product access. Email follow proves mailbox access only; it is not a verified user identity.

• Sansar

  Immersive experience layer

  Immersive participation and experience delivery where a program supports it. Maturity varies by workflow; not every public page implies a live immersive deployment.

AI assists useful tasks at varying maturity. Human authority over consequential actions remains governed by actual permissions. We do not assign an AI meaning to historical “MIA” usage without resolving inconsistent records.