Rights centre
Consent, source, owner, remix permission, training permission, licence and AI disclosure are recorded on each asset and carried into every derived version.
Trust
The questions serious creators ask first.
Who owns this, how was it made, what will it cost, and where does my data live? Soneth AI Studio answers all four in the product itself — in the rights record, the provenance manifest, the cost preview and the privacy model.
- Rights centre
- Content credentials
- Lineage
- Checksum manifest
- Cost preview
- Hard stop
- EU baseline
- Six languages
- Accessibility
Rights
Ownership is recorded, not assumed.
AI music raises real questions about consent, sources and licensing. Soneth answers them per asset, in the data model, rather than in a paragraph of terms.
You keep your work
You own the music you create. The platform's job is to make that ownership provable and portable, including in the export you take elsewhere.
Reference audio with a position
Uploading a reference requires stating the rights position for it, so a licensing question surfaces before the render rather than after a release.
Policies with teeth
Artist, voice, lyrics, upload and training policies are enforced by a policy engine — unapproved voice or artist imitation is out of scope by design.
Credits and splits
Contributors, roles and revenue splits are structured metadata on the release and travel into the export package.
Notice and appeal
Pre- and post-publication safety checks, a notice-and-action path for complaints, and an appeal route for decisions that were wrong.
Provenance
How it was made travels with the file.
Reproducibility and provenance are the same feature seen from two sides: one lets you re-run the result, the other lets someone else verify it.
Content credentials
A provenance manifest records the inputs, models, adapters, parameters and processing steps behind a version, with content hashes.
Lineage
Parent versions, remix sources and reference material stay linked, so the chain from first prompt to final master is readable end to end.
Checksum manifest
Every export ships with a manifest that identifies each artefact by hash — useful for archives, distributors and disputes alike.
Pinned engines
Engine, model and adapter versions are pinned per job. A platform-side upgrade never silently changes what an older version means.
Audit trail
Permission changes, approvals, publications and moderation decisions are recorded and reviewable rather than reconstructed from memory.
Model SBOM
The models in use are documented with version, licence and origin, so the question “what is inside this” has a written answer.
Cost
You can see the bill before it happens.
GPU inference costs real money. Hiding that behind a credit animation is a design choice Soneth declined to make.
Cost preview
An estimate appears before the paid submit, and the finished job shows provider, runtime and final cost against that estimate.
Budget warning and hard stop
Budgets are enforced server-side. Batch, radio and training sessions stop when the ceiling is reached, not when someone notices.
No artificial feature classes
Plans differ by credits, concurrency, storage, retention, seats, API rate and support — never by locking an engine, a format or commercial use.
No API keys, no BYOK
Provider access is entirely platform-managed. You never paste a key, and Soneth never charges you for a provider relationship you have to maintain yourself.
Usage you can read
Usage and cost are visible per workspace, per project and per job, so a team can see where its budget actually went.
Interchangeable providers
Engine capability and compute execution are separated, so Soneth can move to cheaper or faster capacity without changing your workflow.
Privacy and access
European baseline, international product.
The platform starts from EU data protection and adds regional profiles from there, rather than retrofitting compliance after launch.
EU baseline
EU data protection and an EU region are the starting position; further residency profiles are added as capabilities rather than promises.
Export, delete, restore
Data export, deletion, retention and restore are product features with defined lifecycles — not a support request you hope gets answered.
Six languages
German, English, Russian, Chinese, Japanese and Korean at launch, with English as the global fallback and German fully first-class.
Locale, not assumptions
Time zone, number, date, currency and unit formats follow the user. Names, lyrics and metadata are Unicode throughout.
Accessibility
Keyboard operation, screen reader support, visible focus, text scaling, reduced motion and contrast settings are requirements on every surface.
State is never colour alone
A status carries a dot, a colour and its own word; a selection carries a ring and a fill. Nothing critical depends on distinguishing two hues.
The short version
- Rights record
- Consent, source, owner, remix, training and licence per asset
- Provenance
- Manifest, content hashes, pinned engine versions and lineage
- Spending
- Preview before submit, server-side budget warning and hard stop
- Data protection
- EU baseline with export, deletion and retention as features