Opinionated by design
Ten things we deliberately do not build.
Every feature we skip is one less thing to defend in front of a regulator, and one less way for the evidence chain to have a hole in it. If you need any of these, pick a platform that builds them. That is a real requirement and we are not going to argue you out of it.
- 01
Bring your own key for the model
We control the stack in order to control what the receipt can honestly say. We run only models we have evaluated, because otherwise we cannot stand behind how they behave under the policy.
- 02
On-premises deployment
EU-based hosting, not EU-exclusive. That is the environment we host, run and support; in an environment we do not operate we cannot stand behind the same chain.
- 03
A voice-cloning marketplace
We will not host a marketplace of synthetic identities: Article 50(2) puts the marking duty on the output, and a marketplace multiplies the number of voices we would have to stand behind.
- 04
Enterprise contact-centre suites
Not our segment. We are agency-native, not a replacement for a large-enterprise contact centre, and pretending otherwise would cost you a year.
- 05
STIR/SHAKEN caller authentication
A North American caller-ID regime that we do not implement, and that does not apply to EU deployments. Separately: machine-readable marking under Article 50(2) is planned, with C2PA as the intended format; it is not in the product today.
- 06
Custom models and fine-tuning on your weights
Leading governed models only, run through our stack. We can record which model ran; what we cannot do is stand behind the behaviour of a model we have not evaluated, so we support evaluated models only.
- 07
A self-serve credit tier
White-glove onboarding, or nothing. There is no credit-card hobbyist tier: running an evidence chain per call costs real money and hiding that in usage surprises would be the dishonest version.
- 08
Every language, counted for the count
We cover the European languages where we can defend the disclosure wording as well as the transcription. Raw language count is a number that looks good and tells you nothing about whether the disclosure is correct in that language.
- 09
Squads of agents handing off to each other
Single-prompt agents. We support one prompt, one policy and one traceable decision per turn today, because that is simpler to check a year later by someone who was not there.
- 10
A user-tunable denoising mode
Premium EU-routable synthesis on a standard audio path. No user-tunable denoising: one audio path keeps delivery and support simple.
These are the ten we are asked about most. Ask us about anything else.