Bonfire Terminal vs @sovguard/engine
Where @sovguard/engine presents itself as an AI tool without publishing its pricing, hosting model, or data policy, Bonfire Terminal is refreshingly explicit: everything executes locally on your hardware, you supply your own model key at raw cost, and a single payment buys the software forever.
Bonfire Terminal vs @sovguard/engine: the 16-factor comparison
| Rating factor | @sovguard/engine | 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 | Not disclosed | Unlimited Local Compute |
| API-key markup | Not disclosed | No — BYO key at cost |
| Supported LLM providers | Not disclosed | OpenAI; Anthropic; Google; Local; Any |
| Auth / permission types | Not disclosed | API Key; Local/None |
| Phone / messaging bridges | None | Telegram; WhatsApp |
| Speech recognition engine | None | Whisper (local) |
| Local media processing | Not disclosed | Yes |
| Sovereign score | 24 / 100 | 93 / 100 |
The sovereignty gap
Where @sovguard/engine 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 @sovguard/engine if…
Choose @sovguard/engine if its particular take on the tool category fits a workflow you already trust and public transparency isn't a dealbreaker.
Choose Bonfire Terminal if…
Choose Bonfire Terminal if on-device privacy, zero token markup on your own API key, and paying once for good matter more than a hosted convenience.
Bonfire Terminal vs @sovguard/engine: FAQ
Is @sovguard/engine private?
Its data-training and privacy policy isn't publicly documented, so independent verification is difficult. Bonfire Terminal is different by architecture: it is a sovereign on-device agent, so nothing you process is uploaded or used for training. Every task, key, and file stays local on your own hardware.
Is Bonfire Terminal cheaper than @sovguard/engine?
@sovguard/engine does not publish its pricing, so a line-by-line comparison isn't possible. Bonfire Terminal's model is clear: one perpetual license, then you bring your own LLM key and pay your provider directly at cost with no markup added on top.
Can Bonfire Terminal replace @sovguard/engine?
In most cases, yes. @sovguard/engine operates as an AI tool, and Bonfire Terminal covers that ground as a local AI agent and terminal, adding on-device execution, bring-your-own-key billing, and messaging bridges while keeping all of your data on the device.
What can Bonfire Terminal do that @sovguard/engine can't?
Bonfire Terminal runs entirely on-device with local Whisper speech recognition and local media processing, bridges to Telegram and WhatsApp, and passes your LLM key through at cost. @sovguard/engine publishes no evidence of matching that local-first, zero-markup, sovereign feature set.
How do I switch from @sovguard/engine to Bonfire Terminal?
Install Bonfire Terminal, add your own LLM provider key, and point your workflows at the local agent. Because Bonfire runs on-device, there's no cloud account to provision; you can wind down @sovguard/engine once your tasks are running locally under a one-time license.
Does Bonfire Terminal work offline vs @sovguard/engine?
Bonfire Terminal is local-first, so its agent, local Whisper transcription, and media processing keep working without a network; only remote LLM calls need connectivity. That contrasts with @sovguard/engine, whose offline behavior isn't documented, leaving offline use uncertain.