• Multiple AI Providers - Gitee AI, HuggingFace Spaces, ModelScope
• Image-to-Video - Generate videos from images (Gitee AI)
• Dark Mode UI - Gradio-style with frosted glass effects
• Flexible Sizing - Multiple aspect ratios (1:1, 16:9, 9:16, 4:3, etc.)
• 4x Upscaling - RealESRGAN integration
• Secure Storage - API keys encrypted with AES-256-GCM
• Token Rotation - Multiple API keys with automatic failover on rate limits
• Flow Mode - Visual canvas for batch generation (experimental)
  • Local image caching with IndexedDB blob storage
  • Dual limits: 500 images or 4GB max storage
  • LRU cleanup with user confirmation before deletion
  • Download all images before cleanup

Support multiple API tokens per provider for automatic rotation when hitting rate limits (429 errors).

Enter multiple tokens in the API settings, separated by English commas (,):

token_1, token_2, token_3

Note: You must use English comma (,), Chinese comma (，) will not work.

1. Uses the first available token to make API requests
2. When a 429 (rate limit) error occurs, automatically switches to the next token
3. Exhausted tokens are tracked and skipped for the rest of the day
4. Token status resets daily at UTC 00:00
5. UI shows real-time token statistics (total/active/exhausted)

• Node.js 18+ / pnpm 9+
• Gitee AI API Key

See Deployment Guide for detailed instructions.

git clone https://github.com/WuMingDao/zenith-image-generator.git
cd zenith-image-generator
pnpm install

# Configure environment
cp apps/web/.env.example apps/web/.env

# Terminal 1
pnpm dev:api

# Terminal 2
pnpm dev:web

Open http://localhost:5173

📖 Full Development Guide

After deployment, you can call the API directly:

curl -X POST https://your-project.pages.dev/api/generate \
  -H "Content-Type: application/json" \
  -H "X-API-Key: your-gitee-api-key" \
  -d '{"prompt": "a cute cat", "width": 1024, "height": 1024}'

📖 Full API Reference - Providers, parameters, code examples

Browser ──HTTPS──→ Cloudflare Workers ──HTTPS──→ AI Provider (Gitee/HuggingFace)
   ↑                      ↑
AES-256-GCM          Proxy Layer
encrypted            (your deployment)

• Local Encryption: API keys are encrypted with AES-256-GCM before storing in localStorage
• Transport Security: All communications use HTTPS encryption
• Proxy Architecture: Your keys are sent to your own Workers, not directly to AI providers

Important: If you use someone else's deployed instance, the operator can potentially access your API keys.

This is because:

1. The deployment owner can add logging code to capture request headers
2. You cannot verify what code is actually deployed (even if the repo is open source)
3. Cloudflare provides tools like wrangler tail that can inspect live requests

Recommendations:

For maximum security, always deploy your own instance.

MIT

• Gitee AI - z-image-turbo model
• shadcn/ui - UI components
• Hono - Web framework