Use the Store for licensed catalog, then jump into AI Studio when the brief needs a custom melody, voice, or alternate take.
How the SONICHAOS teams plan works for studios and agencies: one seat per producer, pooled downloads, invoice billing on Studio tier, and a per-project audit trail.
A studio with eight producers does not want eight personal accounts and a shared Slack channel for download links. The SONICHAOS teams plan is built for that studio: one seat per producer, downloads pooled to the team, audit log per project, license PDFs co-signed with the buyer's legal name.
A seat is one producer's work account. The seat carries:
Seats are not restricted by genre, by category, or by daily quota; the team's monthly download allowance is shared across every seat. A producer working a heavy month can pull 200 tracks while a producer on holiday pulls zero, and the math works out at the team level.
The smallest team plan starts at 3 seats; the largest tier we publish caps at 25 seats and recommends a custom contract above that.
The Studio tier (10 seats and above) bills by invoice rather than by card. The reason is operational, not mystical: most studios pay recurring vendors through a finance system that wants a 30-day net invoice with a PO line, not a credit card receipt that has to be expensed.
Invoice billing on SONICHAOS runs on Stripe Invoicing. The team admin sets the billing email, the legal entity name, the registered address, and the tax ID at signup; Stripe produces a compliant invoice on the first of every month, payable in 30 days through bank transfer or card of choice. Late payment triggers a soft pause: the team can still browse and audition, but new downloads are blocked until the invoice clears.
Below 10 seats, the plan stays on card billing because the operational overhead of invoicing is not worth it for a 3-seat team.
Every download against a team seat writes a row to the audit log. The row carries:
The audit log is exportable as CSV from the team admin page, filtered by date range, by seat, or by project tag. A studio finance lead running a quarterly licensing reconciliation downloads the CSV, joins it against the project codes in their accounting system, and the numbers tie out without a manual cross-check.
The audit log is also the answer to a client question that comes up about once a quarter: "which tracks did your producer use on our campaign in March." The export answers it in 30 seconds.
Every download against a team seat produces a license PDF that is co-signed with two names: the seat-holder's producer name and the buyer's legal entity name. The legal entity comes from the team's billing profile, the same string Stripe Invoicing prints at the top of the invoice.
Two practical effects. First, a client's legal team that asks "show me the licence" gets a document with the studio's legal entity on it, not the producer's personal name. That matches the client's expectation. Second, a studio that gets acquired or restructured can update its legal entity in the billing profile, and every license PDF issued from that day forward carries the new entity. Past PDFs keep the prior name, which is correct: they were issued under the prior entity.
The PDF carries the project tag the producer entered at the download moment, so a campaign-level audit lines up the licenses with the deliverables a client actually approved.
A producer leaves the studio mid-campaign. What happens to the licenses they downloaded against their seat? The licenses stay valid. The licence is perpetual on download; removing the seat does not back-date it. The campaign keeps running on the tracks the producer downloaded.
What changes:
If the project tag is shared across producers (as it usually is), another seat-holder picks up where the leaver stopped, downloads against the same project tag, and the audit log shows both producers attributed correctly.
Two things are not in the teams plan today. First, seat-level quota limits — every seat shares the team pool without individual caps; a studio that needs per-seat caps usually wants a custom contract, not a self-serve plan. Second, SSO via SAML or OIDC, which is on the Studio roadmap for the back half of the year and currently sits behind a beta flag for two reference customers.
Open the teams page for the seat counts, the per-tier download allowances, and the invoice billing details.
