Bonfire Terminal vs @aiagenta2z/onekey-gateway
@aiagenta2z/onekey-gateway is an API-key gateway that fans out to any provider on a pay-per-token basis. Bonfire Terminal is not a routing layer but a full on-device agent: it runs locally, bills your provider key at cost with no markup, and is sold as a one-time perpetual license.
Bonfire Terminal vs @aiagenta2z/onekey-gateway: the 16-factor comparison
| Rating factor | @aiagenta2z/onekey-gateway | Bonfire Terminal |
|---|---|---|
| Category | Other | AI Terminal / Local Agent |
| Popularity | Not disclosed | Growing · indie |
| Hosting architecture | Not disclosed | On-Device Local |
| Licensing model | Not disclosed | One-Time Perpetual |
| Data / training policy | Not disclosed | Fully local — nothing leaves device |
| Offline capability | Not disclosed | Yes |
| Pricing tier range | Not disclosed | One-time license |
| Execution unit cost | Pay-Per-Token | Unlimited Local Compute |
| API-key markup | Not disclosed | No — BYO key at cost |
| Supported LLM providers | Any | OpenAI; Anthropic; Google; Local; Any |
| Auth / permission types | API Key | API Key; Local/None |
| Phone / messaging bridges | None | Telegram; WhatsApp |
| Speech recognition engine | None | Whisper (local) |
| Local media processing | Not disclosed | Yes |
| Sovereign score | 32 / 100 | 93 / 100 |
The sovereignty gap
Where @aiagenta2z/onekey-gateway lands on each weighted pillar (its bar) — the red marker is Bonfire's score. Auto-derived from the 16 factors above.
Which should you choose?
Choose @aiagenta2z/onekey-gateway if…
Choose @aiagenta2z/onekey-gateway if you need a pay-per-token gateway to route requests across many providers through one API key.
Choose Bonfire Terminal if…
Choose Bonfire Terminal if you want a finished on-device agent with provider choice and a perpetual license, not just a gateway.
Bonfire Terminal vs @aiagenta2z/onekey-gateway: FAQ
Is @aiagenta2z/onekey-gateway private?
@aiagenta2z/onekey-gateway is a gateway with an unpublished hosting model, and routing gateways typically relay your traffic through their infrastructure. Bonfire Terminal is local-first, so requests originate and stay on your device except for the provider calls you explicitly make.
Is Bonfire Terminal cheaper than @aiagenta2z/onekey-gateway?
@aiagenta2z/onekey-gateway charges pay-per-token. Bonfire Terminal adds a one-time perpetual license but passes your provider usage through at cost with no markup, so once purchased you pay only metered tokens rather than gateway overhead on top.
Can Bonfire Terminal replace @aiagenta2z/onekey-gateway?
If your goal is running agent tasks with flexible providers, Bonfire Terminal covers it on-device with any provider. @aiagenta2z/onekey-gateway is specifically a routing gateway, so it differs if you need pure multi-provider request forwarding rather than an agent.
What can Bonfire Terminal do that @aiagenta2z/onekey-gateway can't?
Bonfire Terminal is a complete on-device agent with local Whisper transcription, local media processing, and Telegram and WhatsApp bridges. @aiagenta2z/onekey-gateway is a provider gateway with none of these; it forwards requests rather than running a workflow.
How do I switch from @aiagenta2z/onekey-gateway to Bonfire Terminal?
Install Bonfire Terminal and configure your provider key directly, since Bonfire connects to providers itself and needs no separate gateway. Everything runs on your device, so there is no routing service to keep paying for once you move over.
Does Bonfire Terminal work offline vs @aiagenta2z/onekey-gateway?
@aiagenta2z/onekey-gateway routes to remote providers and does not document offline use. Bonfire Terminal runs on-device with local models and Whisper, so core features work without internet where a request gateway cannot.