Deploy your own copy
Choose Vercel or a self-contained Docker server. The deployment and all of its data belong to you.
Run a tiny service that keeps watch around the clock and redeems eligible full resets near expiry—even when your computer is asleep.
Uses unofficial, undocumented OpenAI interfaces. See the caveat below.
5 min
default check interval
AES-GCM
credential encryption
User-owned
accounts and deployment
Idempotent
safe redemption retries
Three small steps
No OpenAI password sharing, central credential service, or app that must remain open on your computer.
Choose Vercel or a self-contained Docker server. The deployment and all of its data belong to you.
Use OpenAI’s device login. Your password is never collected, and OAuth credentials are encrypted at rest.
The service checks every five minutes and uses the earliest eligible full reset near its expiry.
Why always-on wins
A server does not depend on you noticing an expiry, opening an app, or keeping your laptop awake.
No open laptop, terminal session, or background app is required.
A five-minute schedule watches for credits entering their redemption window.
Persisted redemption IDs prevent ambiguous requests from consuming twice.
Encrypted credentials, inventory, and pending operations are stored durably.
Two editions
Both editions use the same protected setup flow and keep credentials inside infrastructure you control.
A serverless web app with durable Upstash state and signed QStash scheduling.
One Bun container, one persistent volume, and no external database or scheduler.
Safety by design
OAuth tokens are encrypted before durable storage. Rotated credentials are saved before later requests, and stable IDs make retries safe after ambiguous responses.
Encrypted at rest
AES-GCM protects OAuth credentials in Redis or the Docker volume.
No shared service
Your Vercel, Upstash, server, and OpenAI accounts remain yours.
Unofficial integration
OpenAI can change or disable the undocumented endpoints at any time.
Support the project
Help fund maintenance when upstream interfaces change—or simply buy the developer a coffee.