BYOK
BYOK in Paragraph CMS lets teams connect their own AI provider keys, use external models in page workflows, and keep billing and model control separate.
Grzegorz
BYOK stands for Bring Your Own Key. In Paragraph CMS, it means an organization can connect its own AI provider keys and use external models directly inside the product instead of relying only on the built-in Paragraph AI Credits.
This is the feature for teams that want their own provider billing, their own preferred model mix, or tighter control over which vendor powers AI work in the CMS.
One place to manage provider keys
The AI settings view includes a provider table for connecting external AI vendors. In the current implementation, Paragraph CMS supports exactly six BYOK providers: OpenAI, Anthropic, Google AI, xAI, Groq, and DeepSeek.
Each provider can hold one saved API key per organization. After a key is saved, the UI shows only a masked version, while the full credential is encrypted on the server.
Use your own models in page workflows
Once a provider key is connected, its models become part of the AI model picker in the page experience. That means editors can choose external models while drafting content, rewriting text, generating SEO metadata, or filling hero metadata such as slug, caption, and alt text.
BYOK fits naturally with Editor, Page SEO, and Page Hero, because the model choice happens close to the actual content work.
Built-in AI and BYOK can coexist
BYOK does not replace Paragraph AI. It complements it. Teams can use the included credits for a fast default path, then switch to their own keys when they want provider-specific control or separate billing.
There is one important functional detail in the current implementation: full page article generation currently requires Paragraph AI or an OpenAI model, because that flow always runs with browsing enabled. Other AI helpers still benefit from BYOK across the rest of the page workflow.
