A music network,
in your messages.
Synergy is a standalone beta built to help people in music find collaborators, partners and opportunities through iMessage. It was previously called Session. Its home within REALM or another venture is still being decided.
The experience we’re building
Tell Synergy what you do, share work you’re proud of, and describe who you need. It remembers your context and keeps checking for relevant people. When there’s a possible fit, it explains why and asks both people before sharing contact details. A private portal keeps saved context and introduction status together.
The aim is less searching and fewer missed introductions. Music context, current needs, availability and follow-through are what make the service useful.
Try the real texting beta
- Open Team access. Enter the password shared by the organizer and your own iMessage-enabled mobile number.
- Complete signup. The page displays your assigned number and a START code. No approval email is needed for this team test.
- Send the complete activation message from the phone you registered. It includes a START code and a WEB code for the private portal.
- Finish the conversational interview and review your profile. JOIN enables discovery and weekly suggestions during the stated daytime window; JOIN QUIET keeps suggestions on demand.
- Share a current request, such as “Find me a vocalist for an indie-soul EP.” Synergy checks enrolled members as the network changes.
Limited-capacity pilot. The rules-based matcher may find nobody yet. It does not search the whole internet or verify music credits. The separate web preview contains fictional people.
What is implemented
- Server-checked team access, real Photon number allocation and activation by an inbound text.
- AI-assisted onboarding for roles, work links, credits, venues, socials, working terms and goals.
- A server worker that persists conversation state and restarts after failures. It no longer depends on the builder’s laptop.
- Opt-in standing requests: check roughly once a minute, send at most one relevant suggestion per week, respect quiet hours, and pause after two unanswered suggestions.
- Mutual acceptance before contact sharing, saved introduction history, and pause/stop controls.
- A private portal with phone-based sign-in, saved profile fields, introduction history and queued profile updates. The team code alone cannot unlock a profile.
Verification: team signup returned a real assigned line using the existing tester account. The cloud worker connected with a verified OpenAI key. A live synthetic onboarding conversation and 110 automated tests passed. The owner activated his handset and exchanged live AI-assisted messages; replies were accepted by Photon. The custom domain serves the deployed site over HTTPS; the portal rejects unauthenticated profile access. Live phone-to-portal verification, full new-member onboarding and a real two-person introduction still need to be demonstrated.
Still being built
Deeper matching and portfolio understanding; community access controls; branded email sending; Google OAuth activation and calendar scheduling; invited meeting-bot participation; optional phone onboarding; billing.
OpenAI handles conversational questions and intent; explicit rules still control matching, consent and delivery. It should not be presented as a finished autonomous agent.
For developers
Web: Next.js 15, React 19 and TypeScript on Vercel. Public routes serve the landing, team activation and fictional preview. Secrets remain on the server.
Messaging: Photon Spectrum SDK over its event stream. A Node 22 worker runs as a dedicated service account under systemd on an existing Linux server. One worker serializes inbound processing and outbound suggestions.
Conversation: OpenAI Responses API with GPT-5.4 mini, structured output and bounded member context. Provider response storage is disabled. The pilot allows up to 40 model calls per member and 400 overall per UTC day; commands remain available when AI is unavailable.
Persistence: private Vercel Blob for beta requests and activation records; restricted server files for live state, with private cloud backup. The browser demo’s local storage is separate.
Next architectural step: a transactional shared database, durable job/outbox processing, model evaluation and completed per-member calendar OAuth. Do not use the builder’s calendar account as a shared product integration.
Delivery: uncertain sends are retained for reconciliation and are not blindly retried. The pilot is intentionally small; it is not yet a production-scale system.
What feedback helps
Does the interview understand what matters about your work? Is the suggested person relevant, and is the reason clear? Did an introduction lead to a conversation or work? Tell us where you got stuck and what you expected next.