Current permission path for moving renderer credit outside the notation SVG?

[Suddl3]

Hi alphaTab team,

I searched first and found #161 and #92, so I understand the rendered alphaTab credit is intentional and that alternate attribution may need permission or an agreement.

I’m building an early-stage guitar learning/practice app, currently under the working names Guitar Codex / Atlas. alphaTab looks like a very strong fit for rendering synchronized guitar tab + score in lessons, practice mode, autoplay/autostep workflows, and eventually multi-track playback/mixing.

The only product concern is the inline rendered by alphaTab credit inside the notation viewport. In our app, the notation area is a dense interactive workspace that needs to sync with lesson graphics, highlighting, playback, and small embedded views. We would like to keep the notation canvas itself clean, while still giving alphaTab clear and visible credit elsewhere.

Would there be a current approved path for this? If the right path is a commercial license, sponsorship, paid permission, or another arrangement, we’re open to discussing that as well.

For example, would any of these be acceptable, or is there another placement you recommend for apps where alphaTab is a core part of the product?

• visible “Powered by alphaTab” credit in the notation/player settings or info menu
• attribution in the app About / legal / third-party notices
• attribution on a public credits page
• a more prominent branded placement somewhere outside the notation SVG itself

We are early enough that we can design this correctly before committing deeply. Happy to share screenshots/mockups of the proposed integration and attribution placement.

Thanks for building alphaTab. It looks like it could save us from rebuilding a very hard rendering/player stack ourselves.

[Danielku15]

alphaTab does not have any commercial offering or licensing which would grant the removal of the attribution. alphaTab is a pure hobby project for me and accepting any payments (sponsoring, license fees etc.) would require that I register a legal company in Austria for taxation which requires again money and effort to be invested on my side. I think eventually I'd rather lose money by accepting money if I'd do this.

Generally I'm open to alternative attribution methods which fit better into the UI/UX of the integrating app. The level of attribution depends a bit on the role of alphaTab within the app. If it is the key component, I'd also expect alphaTab to be mentioned fairly prominent to users. While if it is just a small side widget a less prominent attribution can also be fine.

Feel free to share insights in your UI/UX and how you would like to place the attribution so we can discuss options that make us both happy.