BYOK Banana
Generate images with your own Gemini API key. No data passes through our servers and you can verify it yourself.
Request Flow: Direct & Secure
Transparency
Don't trust us. Verify.
We built a Network Audit panel directly into the tool. It displays every outgoing request from your browser in real-time, so you can confirm that your API key and images never pass through our servers.
How to verify yourself
- 1
Open DevTools (F12 or right-click then Inspect).
- 2
Go to the Network tab and enable "Preserve log".
- 3
Generate an image.
- 4
See that the only external API request goes to generativelanguage.googleapis.com.
Google: 1 request — Our domain: 0 requests.
Context
Why (almost) nobody does this
Server-side key storage
Most tools require account creation and store your API key on their infrastructure. This creates a central point of vulnerability and a permanent risk of data leaks.
Opaque credit systems
Most services sell proprietary credits with a significant markup over the actual generation cost. With BYOK, you pay Google directly at cost.
A deliberate product choice
This model is less profitable for the developer, which explains its rarity. This tool was designed solely for utility, without monetizing your requests.
How it works
Three steps
01
Get a key
Generate your Gemini API key for free from Google AI Studio. No payment required to start.
Open Google AI Studio →02
Paste the key
Enter the key in the dedicated field of the tool. It is kept in browser memory only, never sent to our servers.
03
Generate
Enter a text prompt, attach images if needed, and generate. Requests go directly from your browser to Google.
Limitations
What this tool is not
These constraints are not design flaws. They are mechanical proof that no server-side data collection takes place.
This is not a persistent account system.
A simple page refresh completely resets your session and erases your key from memory.
We do not store your images.
There is no database to save your history. Generated images are lost if you do not download them.
Closing the tab ends the session.
This is the direct consequence of zero server-side storage. The application is a stateless and ephemeral intermediary.