BRING YOUR OWN AI
Your providers.
Your API accounts.
Hosted TUHFFF uses your chosen AI providers through API accounts. Consumer chat subscriptions and consumer coding plans are not supported for hosted customers.
Running Team in your own environment?
Team can use an API key or supported signed-in tool authentication. Availability depends on the provider, harness, and account terms. Confirm that combination during evaluation. The API-account steps below describe the hosted offering.
1. Choose an account your organisation controls.
Choose the AI provider and models your organisation permits. Confirm who owns billing, who may create keys, and whether your code may be processed outside your environment. Discuss any regional or data-handling requirements before onboarding.
Claude-backed work and Codex smoke runs are recorded in our development environment. Validate the provider and workflow you intend to use. Read product status.
2. Enable API billing.
Set up the provider’s API account and its billing arrangements. Your vendor bills your account directly. A consumer subscription does not stand in for an API account in the hosted offering.
Agree an initial usage budget. Configure the provider’s available alerts and account controls, and check how they behave. Do not assume every provider treats a budget alert as a hard spending stop.
3. Prepare a dedicated API key.
Use a key owned by the organisation and intended for this service. Follow your provider’s access and rotation policies. Arrange the approved onboarding channel with us; never paste keys into the website enquiry form, an ordinary ticket or an email.
The key remains your credential to rotate or revoke. Tell the operator before a planned change so work can be coordinated.
4. Start with one bounded task.
Choose a non-urgent change with a clear expected result and a way to check it. Agree who reviews the work and who can approve release. Confirm the provider account records usage as expected before expanding the workload.
5. Keep an owner on the account.
Review usage and invoices, maintain the billing contact, and investigate unexpected increases. If a key is revoked, billing is exhausted or a provider limits the account, coordinate recovery rather than creating more parallel work.
Provider rate limits, available models and charges can change. Your provider’s account documentation and your contract are the authoritative references.
Before onboarding, have these ready.
- The Git forge and repositories in scope
- Approved providers and API-account owner
- Data-processing and region constraints
- An initial budget and a billing contact
- A useful first ticket and its acceptance criteria
- The person responsible for review and release