Bonfire Terminal vs @amsterdamdatalabs/enact-gateway
@amsterdamdatalabs/enact-gateway is a gateway tool for routing agent actions. Bonfire Terminal is a finished on-device agent rather than a gateway: it runs locally, transcribes with Whisper, bridges to Telegram and WhatsApp, and bills any provider key at cost with no markup under a one-time perpetual license.
Bonfire Terminal vs @amsterdamdatalabs/enact-gateway: the 16-factor comparison
| Rating factor | @amsterdamdatalabs/enact-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 | 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 @amsterdamdatalabs/enact-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 @amsterdamdatalabs/enact-gateway if…
Choose @amsterdamdatalabs/enact-gateway if you need a gateway for routing or brokering agent actions.
Choose Bonfire Terminal if…
Choose Bonfire Terminal if you want a complete on-device agent rather than a routing gateway.
Bonfire Terminal vs @amsterdamdatalabs/enact-gateway: FAQ
Is @amsterdamdatalabs/enact-gateway private?
@amsterdamdatalabs/enact-gateway does not publish its hosting model or a training-data policy, and gateways typically relay traffic through their infrastructure. Bonfire Terminal is local-first, keeping requests on your device except for explicit provider calls.
Is Bonfire Terminal cheaper than @amsterdamdatalabs/enact-gateway?
@amsterdamdatalabs/enact-gateway does not publish pricing tiers. Bonfire Terminal is a one-time perpetual license plus your own LLM usage at cost with no markup, so after purchase you pay only metered tokens rather than gateway overhead.
Can Bonfire Terminal replace @amsterdamdatalabs/enact-gateway?
If you want an agent that runs tasks, yes. Bonfire Terminal is a full on-device agent. @amsterdamdatalabs/enact-gateway is a routing gateway, so it differs if you specifically need action brokering between systems.
What can Bonfire Terminal do that @amsterdamdatalabs/enact-gateway can't?
Bonfire Terminal is a complete on-device agent with local Whisper, local media processing, and Telegram and WhatsApp bridges. @amsterdamdatalabs/enact-gateway is a gateway without these; it routes actions rather than running a full workflow.
How do I switch from @amsterdamdatalabs/enact-gateway to Bonfire Terminal?
Install Bonfire Terminal and add your provider key directly, since Bonfire connects to models itself without a separate gateway. Everything runs on your device, so there is no routing service left to operate.
Does Bonfire Terminal work offline vs @amsterdamdatalabs/enact-gateway?
@amsterdamdatalabs/enact-gateway does not document offline support and typically relays to remote systems. Bonfire Terminal runs on-device with local models and Whisper, so core features work without a connection where a gateway cannot.