Authentication
Add Maru sign-in to your product
Register a creator app, choose permissions and let people connect their Maru account.
Use a creator app when people need to connect their Maru account to your instrument, website or musical application. They can approve specific actions, such as saving app-specific presets or generating with their own credits. Adding this connection requires a developer integration and beta access.
App registration and the musical product
Registering an app supplies the name and permissions people see when connecting. You still need to build your instrument and integrate sign-in. Registration does not publish a listing or set up a sale.
Use Creator apps to manage registrations you own. A supported module workflow can link its project to an app through the same system. Your developer supplies the supported sign-in integration; the technical setup belongs in the app integration guide.
Choose what the app needs
| Permission or access choice | What it means to the person using it |
|---|---|
| Identity | Recognize the same person within this app after Maru sign-in |
| App-specific presets | Read or save presets within the app's supported module context |
| Generation | Submit permitted jobs using the person's account and credits after consent |
| Admission | Limit who can enter, such as approved members or people with verified paid access |
Identity does not give the app a person's email, global account ID or private project library. Spending permission is separate. Paid admission requires a supported purchase or membership connection; selecting an access policy does not create a checkout.
What the player experiences
The player begins in your product, signs in on Maru and reviews the named app's request. After approval, the product can perform the allowed actions. They can review and disconnect it in Connected apps.
Keep the purpose of the connection clear. Explain what still works when signed out, whether a service spends credits, and where results are saved. Generation and credits provides the player-facing explanation.
Follow adoption responsibly
Use generation activity to see how many people request new sounds. It does not count everyone who plays your instrument, and it does not show who bought it. Your creator dashboard and earnings explains what those numbers mean.
For a concrete product journey, follow the generative beatbox example. If your host or access model is not covered, contact Maru to scope early access.