One of the biggest requests we kept getting was simple:
"Can I use my own OpenAI or Claude API key instead of the shared quota?"
So we built it.
Cloudpen's AI coding assistant, Quill, now supports Bring Your Own Key (BYOK).
By default, Quill uses Cloudpen's shared AI pool, which is perfect for getting started. But once you're working on larger projects or relying heavily on AI, shared rate limits become noticeable.
With BYOK you can connect your own provider and use Quill with your own quota instead.
What you can do
Connect your own OpenAI, Anthropic (Claude), Gemini, Grok, or OpenRouter API key
Use your provider's own limits instead of Cloudpen's shared pool
Pick the model that best fits the task
GPT-4o for complex reasoning
Claude Opus for long-context editing
Gemini Flash for speed
Switch between keys whenever you want
Remove your key at any time and instantly fall back to the shared pool
Security
One thing we cared about from the beginning was key security.
API keys are encrypted using AES-256 before storage and the raw key is never returned after saving. Only the last few characters are shown so you can identify which key is active.
Why we built it
The goal with Cloudpen has always been to remove friction from development.
Sometimes that means adding an editor.
Sometimes it means offline support.
Sometimes it means letting developers bring their own infrastructure instead of forcing ours.
BYOK falls into that last category.
If you already pay for an AI provider, you should be able to use it directly inside your editor.
We're continuing to build Cloudpen in public, and this is one more step toward making it a complete browser-based development environment.
I'd love to hear how you'd approach BYOK in your own editor—or what providers you'd want to see next.
Top comments (0)