Discord Channel

Join the Discord channel to chat with other participants and sponsors https://discord.gg/dNvBejKYjv

About the challenges

MuseHub Challenge:

Create an app or plugin for music creators—extend MuseScore, Audacity, or build something tailored for guitar or piano players. Best entries get featured on MuseHub, with 10k+ guaranteed traffic

Audiotool Challenge:

Build on the Audiotool online DAW—use APIs, prototype interfaces, connect services. Winner gets featured in the Audiotool newsletter, homepage, and launch campaign, plus up to $5,000 in Google Cloud credits 

ABRSM challenge:

ABRSM is The Associated Board of the Royal Schools of Music and a global music education charity.

Help ABRSM explore how AI can support music education by building a proof of concept that generates feedback on music performances. We’re looking to combine audio analysis and language modelling to create scalable tools that could support human feedback in music assessment.

IMPORTANT: Participants who take on this challenge agree to share their code with ABRSM at the end of the event. 

Get started

MuseHub

Documentation: https://developer.musehub.com/muse-partners-help 

SDK: https://drive.google.com/drive/folders/1EH9vCji5Q4Hfij5XGt3DU_JVraT8NpA3

Muse DRM tool:  https://drive.google.com/drive/folders/1U4EnrPF9RBqVM9A03PvC4_RWDDJnFARj

AudioTool:

Join the Beta of AudioTool on https://new.audiotool.com/ and get access to the SDK to build apps for the Nexus platform. You can also make an existing app compatible with Nexus. 

ABRSM

Fill in this form to access the dataset and get the full brief. 

Requirements

What to Build

  • A working prototype of a creative project in music technology (e.g. app, plugin, interactive tool, hardware/software integration, or new workflow).
  • Hacks can be based on the sponsor challenges (MuseHub, Audiotool) or your own original idea.
  • Teams are encouraged to mix music + tech + creativity — coders, musicians, designers, engineers, and storytellers all welcome.
  • The build should demonstrate functionality (even if rough), not just concepts.

What to Submit

On Devpost, each team must submit:

  1. Project description

    • What you built, the problem it solves, and who it’s for.

  2. Demo video (max 3 minutes)

    • A clear walkthrough of your hack in action. Screen recordings, live demos, or slides + audio are fine.

  3. Code or prototype link

    • GitHub repo, plugin file, or prototype URL (if applicable).

  4. Team details

    • Names of all contributors and their roles.

  5. Challenge track

    • Specify if your project is for the MuseHub, Audiotool or ABRSM challenge, or an open category hack.

Hackathon Sponsors

Prizes

£1,500+ in prizes
+ other prizes
Best app for Muse Hub
1 winner

Linked to app from the landing page of the site

AudioTool
1 winner

Promoted on the Nexus page. $5000 worth of Google Cloud credits

ABRSM
£1,500 in cash
1 winner

Other challenge
1 winner

Platinum ticket to SXSW London

Devpost Achievements

Submitting to this hackathon could earn you:

Judges

Martin Keary aka Tantacrul

Martin Keary aka Tantacrul
VP Products, Muse Group

JB Thiebaut

JB Thiebaut
CEO Music Hackspace

Kathleen Wilkinson

Kathleen Wilkinson
Brand Partnership Manager / SXSW London

Elena Caton

Elena Caton
Head of Digital Products / ABRSM

Silas Gyger

Silas Gyger
Full Stack Engineer / Audiotool

Serkan Djemal

Serkan Djemal

Judging Criteria

  • Creativity & Innovation (25%)
    Is the idea original and memorable? Judges should look for concepts that are fresh, inventive, or present a unique twist on a problem. A strong entry shows imaginative problem-solving and stands out from the crowd.
  • Technical Execution (25%)
    How well does the project work? This includes the reliability, polish, and technical craftsmanship—well-structured, functional solutions that demonstrate solid engineering. Think of functionality, dependability, and intuitive build quality.
  • Impact & Usefulness (25%)
    Does the solution solve a real problem effectively? Judges should assess the project’s potential for tangible benefits—whether it’s practical, scalable, and valuable to its intended users or audience.
  • Presentation (25%)
    Is the idea communicated effectively and compellingly? This involves clarity, storytelling, and visual engagement—how well the team explains their concept, demonstrates it, and makes it easy for others (judges, users) to understand and remember.

Questions? Email the hackathon manager

Tell your friends

Hackathon sponsors

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.