Home / vs / @contractspec/lib.support-bot
vs@CONTRACTSPEC/

Bonfire Terminal vs @contractspec/lib.support-bot

@contractspec/lib.support-bot is a chatbot platform library for support bots. Bonfire Terminal is a full on-device agent instead: it runs locally, transcribes with Whisper, processes media on your machine, bridges to Telegram and WhatsApp, and bills any provider key at cost with no markup under a perpetual license.

Apply for AccessCHATBOT PLATFORM
Full comparison

Bonfire Terminal vs @contractspec/lib.support-bot: the 16-factor comparison

Rating factor@contractspec/lib.support-botBonfire Terminal
CategoryChatbot PlatformAI Terminal / Local Agent
PopularityNot disclosedGrowing · indie
Hosting architectureNot disclosedOn-Device Local
Licensing modelNot disclosedOne-Time Perpetual
Data / training policyNot disclosedFully local — nothing leaves device
Offline capabilityNot disclosedYes
Pricing tier rangeNot disclosedOne-time license
Execution unit costNot disclosedUnlimited Local Compute
API-key markupNot disclosedNo — BYO key at cost
Supported LLM providersNot disclosedOpenAI; Anthropic; Google; Local; Any
Auth / permission typesNot disclosedAPI Key; Local/None
Phone / messaging bridgesNoneTelegram; WhatsApp
Speech recognition engineNoneWhisper (local)
Local media processingNot disclosedYes
Sovereign score24 / 10093 / 100
Sovereign Software Score

The sovereignty gap

@contractspec/lib.support-bot24/ 100
Bonfire Terminal93/ 100+69 on sovereignty

Where @contractspec/lib.support-bot lands on each weighted pillar (its bar) — the red marker is Bonfire's score. Auto-derived from the 16 factors above.

Privacy & Control@contractspec/lib.support-bot 9 / 35
9
Bonfire 35
Cost Efficiency@contractspec/lib.support-bot 8 / 25
8
Bonfire 25
Technical Capabilities@contractspec/lib.support-bot 0 / 25
0
Bonfire 22
Vendor Risk (lower risk = higher score)@contractspec/lib.support-bot 7 / 15
7
Bonfire 11
Verdict

Which should you choose?

Choose @contractspec/lib.support-bot if…

Choose @contractspec/lib.support-bot if you need a library specifically for building support chatbots.

Choose Bonfire Terminal if…

Choose Bonfire Terminal if you want a general on-device agent with bridges, local Whisper, and media processing.

FAQ

Bonfire Terminal vs @contractspec/lib.support-bot: FAQ

Is @contractspec/lib.support-bot private?

@contractspec/lib.support-bot does not publish its hosting model or a training-data policy, so its privacy posture is unclear. Bonfire Terminal is local-first by design, keeping your prompts and data on your device rather than in a vendor cloud.

Is Bonfire Terminal cheaper than @contractspec/lib.support-bot?

@contractspec/lib.support-bot 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 any recurring fee.

Can Bonfire Terminal replace @contractspec/lib.support-bot?

Partly, since @contractspec/lib.support-bot targets support chatbots. Bonfire Terminal is a personal on-device agent, so it replaces the assistant experience but is not a drop-in library for building customer support bots.

What can Bonfire Terminal do that @contractspec/lib.support-bot can't?

Bonfire Terminal runs offline on-device, transcribes with local Whisper, processes media locally, and bridges to Telegram and WhatsApp. @contractspec/lib.support-bot is a support-bot library without documented offline mode, transcription, or media handling.

How do I switch from @contractspec/lib.support-bot to Bonfire Terminal?

For a personal agent rather than a support-bot library, install Bonfire Terminal and add your provider key. Bonfire is local-first, so your data stays on your device, and you gain bridges, transcription, and media processing.

Does Bonfire Terminal work offline vs @contractspec/lib.support-bot?

@contractspec/lib.support-bot does not document offline capability. Bonfire Terminal runs on-device with local models and Whisper, so its core features work without a connection, which the support-bot library does not publicly guarantee.