BYOK means “bring your own key”: you connect an account credential from a supported AI provider so generation can use that provider account. In a creative workflow, the key question is who charges for which part of the work. Separate the workflow software subscription from model-provider usage when planning costs.
Map the billing path
Check Nova Creative's plans and generation routes alongside the provider's own charges. For a complete comparison, use cost per usable asset rather than the price of one request alone.
Write down the workflow tool, the provider account, the selected model, and the party paying each bill. A statement about no generation markup does not mean generation is free. Provider usage can still incur charges, and the workflow tool may have its own subscription or feature limits.
Nova Creative presents BYOK as a supported generation route. Before choosing it for a project, check the current plan, supported providers, and model availability in the app. Avoid budgeting from an old catalogue count or a price mentioned in an earlier campaign.
Prepare the provider account
Confirm that the provider account can use the model you intend to run and has an appropriate billing setup. Where the provider offers project-specific keys, permissions, or spending controls, use the controls suited to the job. Keep credentials out of shared prompts, screenshots, and creative handoff documents.
A team should know who owns the account and who can respond if access changes. A workflow that depends on a departing contractor's personal provider account is difficult to maintain. Record the account owner and operational contact without copying the secret key into project notes.
Test one complete path
- Connect the key through the supported account settings.
- Choose one compatible model and a small test brief.
- Run a single sample and confirm that it completes.
- Check the provider's usage reporting after the run.
- Confirm the expected output before expanding the workflow.
Provider usage reporting may not update immediately. Reconcile charges after the reporting delay rather than treating an empty dashboard as proof that the run cost nothing. Review provider documentation for the exact billing behaviour of failed or cancelled requests.
Plan for changes
Models, account permissions, and provider limits can change. Keep the provider and model names with the workflow notes and check them before an important production batch. If you replace a model, run a new sample: compatible inputs do not imply equivalent results.
Use a spending cap or a manually bounded test plan where available. A multi-branch graph can multiply requests quickly, so inspect the number of directions and attempts before running it.
Compare complete costs
Evaluate provider charges alongside subscription costs and review effort. Track spending per accepted asset instead of only the listed price of a request. BYOK is useful when its account and billing arrangement fits your workflow; it does not remove the need to review quality, manage credentials, or understand what each generation step will do.