Bring your own models
An organisation can run Final Frame's jobs on its own model contracts, under its own spend, residency and audit: OpenAI, Azure OpenAI, Anthropic, Google Vertex AI and Gemini, AWS Bedrock, Mistral, ElevenLabs, fal, Replicate and Custom endpoint (OpenAI compatible). A job with no route, or one its own model cannot run, runs on Final Frame's model.
Adding a provider
Organisation settings, Bring your own models, for those who hold models.keys.manage (Org admins by default). Add provider: the kind, how it signs in, its settings and the key, then Test connection, which lists the provider's models. Each model carries its capabilities, region and residency, an optional token cap a month, and an owner.
Keys and federation
- Federation comes first where the provider offers it: AWS Bedrock by role assumption, Google Vertex AI by workload identity, Azure OpenAI by an Entra federated credential. Final Frame proves who it is and keeps no key.
- A key is tested with the provider before it is kept; a refused key is never kept. It is sealed under the organisation's own KMS key and never shown again: the screen shows its prefix and its last four characters.
- Rotating tests the new key, then makes it current; the old one keeps working for the overlap chosen: none, an hour, a day, three days or a week. Each key has an optional expiry and a rotation reminder, 90 days by default.
- A provider's address changes only with a new key, tested at the new address.
- Keys are entered by a person, in person. An API key, or support viewing the app as a user, is refused.
Routing
Model Context, Routing chooses, for each job, the model that runs it, Final Frame's or one of yours, and a fallback chosen the same way. A job runs on its route, then its fallback, then Final Frame's model. A model past its cap or its expiry, without a key, or without the capability the job needs is passed over; one that fails is written on the provider's record and the next one runs.
| Job | What it does | Runs on your model |
|---|---|---|
| Reasoning | Deep search and the judgements that decide which record is about your title. | Not yet: the choice is kept and shown, and Final Frame’s model runs it |
| Extraction | Reads deal memos and documents into the proposal for a delivery. | Not yet: the choice is kept and shown, and Final Frame’s model runs it |
| Translation | Writes titles, taglines and synopses again for another market, in its own language. | Yes |
| Synopsis writing | Writes the tagline and the five contractual synopsis lengths. | Yes |
| Image generation | Makes artwork, key art and stills in the Image Studio. | Not yet: the choice is kept and shown, and Final Frame’s model runs it |
| Video | Animates a picture or a slate into a short shot. | Not yet: the choice is kept and shown, and Final Frame’s model runs it |
| Voice and dubbing | Speaks voice-overs and dub lines. | Not yet: the choice is kept and shown, and Final Frame’s model runs it |
| Transcription | Turns a programme’s sound into timed words, the start of every subtitle made from it. | Not yet: the choice is kept and shown, and Final Frame’s model runs it |
| Embeddings and search | Indexes material so a search finds a moment by what it means. | Not yet: the choice is kept and shown, and Final Frame’s model runs it |
The record
Every add, change, test, rotation, removal, route and fallback is on the provider's own history and on the action log. Each use is on the provider's history with its tokens, which count towards its cap. A job run on your model is not billed by Final Frame; your provider bills you. How it is secured: Security and hardening.