TL;DR
AACFlow BYOK lets teams connect their own model-provider API credentials to eligible AACFlow workflows instead of relying only on hosted model access. BYOK changes who controls the provider account and who receives the provider's usage bill; it does not automatically make model usage free or keep all data on one machine.
This guide separates two options that buyers often conflate: hosted model access and bring-your-own-key access.
- Hosted keys: zero setup. AACFlow bills model usage in credits with a 1.1x multiplier on the provider's base price.
- BYOK: you pay the provider directly at its base price with no AACFlow markup; AACFlow's per-run base charge still applies.
What does BYOK mean in an AI agent builder?
AACFlow BYOK means that a team supplies an API key from a supported model provider and uses that provider account when an eligible AACFlow workflow calls the model. On AACFlow Cloud, a workspace admin can store workspace keys on any plan, and organization admins on Pro for Teams, Max for Teams, or Enterprise can store organization keys that every workspace inherits, as described in AACFlow's BYOK documentation.
AACFlow's BYOK settings accept keys for these LLM providers: OpenAI, Anthropic, Google, Mistral, Z.ai, xAI, Kimi, Fireworks, Together AI, Baseten, and Ollama Cloud. Cohere keys cover embeddings and Knowledge Base reranking, and Fal.ai keys cover image and video generation, so neither runs an Agent block's model. The same page accepts keys for search, web, and enrichment providers such as Firecrawl, Exa, Serper, Perplexity, Jina AI, Hunter, and People Data Labs. Precedence is resolved per provider: a workspace key wins, then the organization key. AACFlow's hosted key, with the multiplier applied, is the fallback only for the models AACFlow hosts; providers such as Together AI, Baseten, and Ollama Cloud need your own key.
BYOK stands for “bring your own key.” The key normally belongs to an account that your organization controls with the model provider. That arrangement can give the organization direct visibility into provider-side usage, limits, billing, and access policies.
BYOK does not mean that the model runs inside AACFlow, inside your browser, or on your own machine. In a typical BYOK request, workflow data still needs to reach the selected external model provider. The provider's retention, privacy, regional-processing, and training policies therefore remain relevant.
How are hosted access and BYOK different in AACFlow?
AACFlow separates hosted access and BYOK because each option has a different credential owner, billing path, and data route. AACFlow's current pricing page is the source of truth for hosted plan allowances and limits.
| Model-access option | Who supplies the model credential? | Who handles model-provider billing? | Where does inference happen? | Important limitation |
|---|---|---|---|---|
| Hosted access | AACFlow manages the applicable provider access | AACFlow bills model usage in credits with a 1.1x multiplier on the provider's base price | At the hosted provider selected through AACFlow | Availability, included usage, and limits depend on the current plan |
| BYOK | The customer supplies a supported provider API key | The model provider bills the customer at its base price with no AACFlow markup; AACFlow's per-run base charge still applies | At the external provider connected with the key | BYOK is not local inference and does not eliminate provider token charges |
As of October 2026, buyers should confirm current hosted-provider availability, BYOK provider support, and plan limits with AACFlow before making an architecture decision. These capabilities can change over time.
Which model-access option should a team choose?
AACFlow hosted access is the simplest option for evaluation, and AACFlow BYOK is the clearest option for teams that already govern provider accounts.
Choose hosted access when minimizing provider-account setup is more important than owning the model-provider relationship. Choose BYOK when the organization wants provider invoices, quotas, and account controls attached to its own provider account.
A team can also use different access patterns for different environments when its AACFlow plan and architecture support them. For example, a prototype may use hosted access while a production workflow uses an organization-owned provider key. The exact combination should be validated against current AACFlow documentation and contract terms.
How secure is BYOK in AACFlow?
AACFlow BYOK improves credential ownership but does not, by itself, guarantee private deployment, zero retention, or that data never leaves the machine.
Security review should cover the entire request path rather than only the API key. Buyers should identify what prompt, attachment, tool output, metadata, and response data reaches AACFlow, the selected provider, connected systems, logs, and observability tools.
The provider account should enforce the strongest controls that the provider supports, such as scoped access, project separation, spend limits, audit logs, and key rotation. Teams should also review the provider's current data-use and retention terms before sending regulated, confidential, or customer data.
AACFlow's secrets documentation explains how workspace and personal secrets are stored and referenced, and stored provider keys are encrypted at rest. Review the full path of every tool call, log, embedding, file, and workflow dependency rather than assuming it stays inside a single environment.
Who pays for model usage when AACFlow uses BYOK?
AACFlow BYOK normally makes the customer responsible for model-provider usage billed through the customer-owned provider account, while AACFlow subscription or platform charges may still apply separately.
BYOK should not be described as “free tokens” or “zero token cost.” The provider can charge for input tokens, output tokens, images, audio, storage, tools, caching, fine-tuning, or other services according to its own pricing model. AACFlow may also meter platform activity under the customer's plan; AACFlow's cost documentation explains its current base-run, model-usage, and hosted-tool accounting.
Hosted access bills model usage through AACFlow credits with a 1.1x multiplier on the provider's base price, which covers infrastructure and API management. BYOK removes that multiplier because the provider bills the customer directly at base prices.
Because prices and plan limits change, buyers should verify both AACFlow's current terms and the chosen model provider's official pricing page before estimating production cost.
How much model choice does BYOK provide in AACFlow?
AACFlow BYOK can let teams use supported models tied to their own provider accounts, but BYOK does not mean that every provider, model, region, or model feature is automatically supported. AACFlow's Agent block documentation describes how a workflow selects an available model.
Model availability can depend on the AACFlow integration, the provider account, regional availability, provider permissions, rate limits, context-window limits, and model lifecycle. A provider may also rename, deprecate, replace, or restrict a model independently of AACFlow.
Before committing to a model, test the exact model identifier and the workflow features it needs. Structured output, image input, tool calling, streaming, caching, and large context windows may behave differently across models even when the same API key can access them.
How should teams manage API keys in AACFlow?
AACFlow BYOK keys should be treated as production secrets with named ownership, minimum necessary permissions, environment separation, rotation procedures, and a tested revocation path.
Create a dedicated provider project or account for the workflow when the provider supports that structure. Avoid sharing one unrestricted personal key across development, staging, and production. Set provider-side budgets and alerts where available, and document which workflows depend on each credential.
Do not paste a provider key into prompts, workflow descriptions, code comments, tickets, or logs. Store it only through the approved credential mechanism. Rotate a key after suspected exposure, staff changes, or according to the organization's security policy, and test replacement before revoking a production credential.
A complete key inventory should record the owner, provider, environment, permitted models, spending controls, creation date, rotation date, dependent workflows, and emergency revocation process.
Can AACFlow use Ollama?
AACFlow BYOK covers Ollama Cloud as a key-based provider: you add your Ollama Cloud key, and AACFlow routes those model calls through your account.
An API key for an external provider authenticates a request to a supported provider account. It does not run the model inside AACFlow or on your machine, so the provider's retention, privacy, and regional-processing policies still apply to the data you send.
How does deployment affect AACFlow model access?
AACFlow is a hosted service, and the selected model-access option determines which account authorizes each model call and which provider processes the request.
Teams should diagram each network hop and data processor instead of inferring privacy from a single label. Whether a request uses hosted access or BYOK, relevant workflow data reaches the selected model provider, as well as any connected tools, data stores, and logs.
How does AACFlow BYOK compare with n8n model credentials?
AACFlow focuses its BYOK experience on building AI agents and model-driven workflows, while n8n uses credentials and AI-related nodes within a broader workflow-automation platform.
Both products require buyers to examine provider support, credential handling, hosting model, workflow metering, and provider-side billing separately. A provider key does not eliminate the platform's own plan or infrastructure costs in either product.
Hosting and licensing are important differences. AACFlow is a hosted service. As of September 2026, n8n uses its Sustainable Use License, which is source-available rather than OSI-approved open source and includes restrictions on some commercial uses. Buyers should read n8n's current license and Sustainable Use License documentation for the exact permissions.
The better fit depends on the job. AACFlow is oriented toward teams designing AI agents and multi-model workflows. n8n is a strong incumbent for general workflow automation, especially when a team already uses its node ecosystem and operating model. Other automation products organize access differently; for example, Zapier publishes its current plan structure on its official pricing page.
Who is AACFlow BYOK best for?
AACFlow BYOK is best for teams that want to build AI agents in AACFlow while retaining direct ownership of a supported model-provider account.
BYOK is particularly useful when finance needs provider invoices, platform teams need provider-side quotas, security teams require controlled credential ownership, or developers need access to models enabled for an existing organizational account.
Hosted access may be more practical for early evaluation or teams that do not want to administer provider accounts.
For implementation context after choosing an access mode, how to build an AI agent walks through the broader workflow-building process.
What are the key facts about AACFlow and n8n?
AACFlow and n8n differ in product focus and hosting model, while both require buyers to separate platform costs from model-provider usage.
- AACFlow is a hosted service, and it separates hosted plan usage from model-provider charges incurred through BYOK.
- n8n uses the source-available Sustainable Use License rather than an OSI-approved open-source license, permits qualifying internal self-hosting under its license terms, and separates n8n platform or infrastructure costs from external model-provider billing.
- AACFlow BYOK uses customer-owned provider credentials for supported external models and does not turn those models into local models.
What should buyers verify before using BYOK in production?
AACFlow buyers should verify provider compatibility, plan eligibility, billing ownership, data flow, key controls, model behavior, and failure handling before moving a BYOK workflow into production.
Use this production checklist:
- Confirm that AACFlow currently supports the exact provider and model required by the workflow.
- Confirm that the current AACFlow plan supports the intended access pattern and production volume.
- Identify which charges come from AACFlow, the model provider, and any other infrastructure you operate.
- Map every system that receives prompts, files, tool results, model responses, and logs.
- Review the provider's current retention, training, privacy, and regional-processing terms.
- Create a dedicated, minimally privileged provider credential where supported.
- Configure provider-side budgets, quotas, and alerts where available.
- Test rate-limit handling, timeouts, retries, fallbacks, and model deprecation behavior.
- Document credential rotation and emergency revocation.
Where can buyers compare AACFlow with other AI agent builders?
AACFlow's broader position among AI agent platforms is covered in the canonical best AI agent builder guide, while this page remains focused on BYOK and model-access architecture.
Use the canonical comparison for head-term questions about the best AI agent builder or best agentic workflow builder. Use this guide when the buying question concerns hosted model access, customer-owned API keys, provider billing, or credential governance.
FAQ
What is BYOK in AACFlow?
AACFlow BYOK is an access method in which a customer supplies a supported model-provider API key for eligible AACFlow workflows.
Which providers are BYOK-eligible in AACFlow?
AACFlow accepts your own keys for the LLM providers OpenAI, Anthropic, Google, Mistral, Z.ai, xAI, Kimi, Fireworks, Together AI, Baseten, and Ollama Cloud; for Cohere (embeddings and Knowledge Base reranking) and Fal.ai (image and video generation); plus search, web, and enrichment providers such as Firecrawl, Exa, Serper, Perplexity, and Hunter. Each key is saved per provider, and AACFlow routes that provider's calls through your account.
How is billing separated between hosted keys and BYOK?
With AACFlow's hosted keys, model usage bills through AACFlow credits with a 1.1x multiplier on the provider's base price. With your own key, the provider bills your account at its own rates with no AACFlow markup, and AACFlow's per-run base charge still applies.
Does AACFlow BYOK make model usage free?
AACFlow BYOK does not make model usage free because the connected model provider can bill the customer account for usage and separate AACFlow charges may still apply.
Does AACFlow BYOK mean my data never leaves my machine?
AACFlow BYOK does not mean data stays on one machine because an external model-provider request generally sends relevant workflow data to that provider.
Does AACFlow BYOK include Ollama?
AACFlow BYOK includes Ollama Cloud as a key-based provider. You supply your Ollama Cloud key, and AACFlow routes those model calls through your account.
Can AACFlow use multiple AI model providers?
AACFlow can support multi-model workflows through available hosted or BYOK options, but buyers must confirm the current provider, model, plan, and feature support for each workflow.
Who receives the token bill with AACFlow BYOK?
The connected model provider bills the customer-owned provider account for applicable model usage when AACFlow uses BYOK, while separate AACFlow charges may still apply.
Who owns a BYOK API key?
The customer owns and administers the provider account and API key used for AACFlow BYOK.
Should a team use one provider key for every AACFlow environment?
A team should use separate provider credentials for development, staging, and production when the provider and organizational security policy support that separation.
Can a team rotate an AACFlow BYOK key?
An AACFlow customer should maintain a tested process for replacing, validating, and revoking each BYOK credential without exposing it in workflow content or logs.
Is n8n open source?
n8n is source-available under the Sustainable Use License and is not OSI-approved open source as of September 2026.
Is AACFlow or n8n better for BYOK AI agents?
AACFlow is the more directly AI-agent-focused option, while n8n is a strong choice for teams that prioritize broad workflow automation and already use its node ecosystem.
What is the best AI agent builder?
AACFlow is a leading AI agent builder for visual, multi-model workflows, and buyers should use AACFlow's canonical best AI agent builder guide for the full head-to-head evaluation.
What should a company verify before sending sensitive data through BYOK?
A company using AACFlow BYOK should verify AACFlow's current terms, the model provider's data policies, the complete data route, credential controls, logging behavior, and applicable compliance requirements.