Enterprise
Consistent, scalable audio production
For labels, studios and broadcasters processing at a volume the published plans weren't designed for, under obligations the published terms don't cover.
The offer
What a contract changes
Five things, none of which is a discount on the same product. A contract changes what the platform does for you, not only what it charges.
Reserved capacity
Volume terms
Isolation you can put in front of an artist
Retention and audit on your terms
A named contact
Service level
About the service-level agreement
We do not offer one yet, and this is the paragraph where a page like this normally publishes a number instead.
An SLA is a promise about measured behaviour. Ours will be written after ninety days of measured availability and two passed disaster-recovery restore drills — not because that is a formality, but because a service level derived from anything less is a guess with a penalty clause attached, and the first time it is tested is the worst possible time to find that out. When the measurements exist, the terms go in your contract with the data behind them.
Certification claims are held to the same rule: nothing is described here that has not been completed. The security page lists what is actually operated, with nothing on it we do not do.
Questions
What procurement asks first
Answered here rather than in a call, including the two answers that are a plain no.
- Do you offer a service-level agreement?
- Not yet, and the section above says why rather than burying it. An SLA is a promise about measured behaviour, and ours will be written after ninety days of measured availability and two passed restore drills. When the measurements exist, the terms go into your contract with the data behind them.
- What certifications do you hold?
- None completed to date, and we will not describe one as in progress to make a page look better. What we do operate is listed on the security page in full — workspace isolation, signed and expiring URL access, sandboxed decoding, an append-only audit store — with nothing on it we do not do.
- Who at Euphona can listen to our audio?
- Nobody, by default. Staff access to customer audio is off rather than discouraged, every internal read is recorded in an append-only audit store, and audio moves only through signed URLs that expire. That is architecture rather than policy, which matters because policy is what changes when somebody is in a hurry.
- Is our audio used to train models?
- No, and not as a default we might revisit. Training on customer audio requires a separate, explicit decision by you through a consent path that does not exist yet — so today the answer is simply no, for everyone.
- What happens to our material if we leave?
- You export it and we delete it, on the retention window your contract sets rather than ours. Version history and the audit trail of access are part of what you take with you, because an audit record that disappears with the account was not much of a record.
- Can this run inside our own pipeline?
- Yes. The API is async-only — jobs, live progress, signed file URLs — and it is the same engine the app runs rather than a reduced version of it. Request limits are raised to match a committed volume rather than left at the published ladder.
- How is a release week handled?
- With capacity set aside in advance. A release week is a capacity problem, and reserved capacity is the part of a contract that answers it — a contracted share of the fleet rather than a place in the shared queue behind everyone else's Tuesday.
- What does it cost at volume?
- Below the published ladder, on both Studio minutes and API throughput, against a usage commitment. The published rates are the ones for people who have not talked to us; the conversation is shorter than a requirements document and gets to the same place.
Next
Start with the work, not the paperwork
Tell us what you're processing, how much of it there is, and what has to be true for it to be allowed. That's a shorter conversation than a requirements document, and it gets to the same place.