How Karen runs Joong Hardware
Joong Hardware is a Jamaican wholesale hardware operation running on Karen AI — IrieVybz AI's sovereign business assistant. This case study covers what Karen handles end-to-end at the counter, in the POS, and behind the scenes for the operator.
What is the Joong Hardware case study?
The Joong Hardware case study documents how Karen AI — IrieVybz AI's sovereign business assistant — runs the counter, POS, customer service, and dev ops automation for Joong Hardware, a wholesale hardware operation in Jamaica. Karen handles inbound WhatsApp and voice calls, supports cashiers with AI search and manager-PIN OTP at the POS, enforces minimum order quantities, and exposes a dev MCP toolset (80+ tools) so the operator runs production ops from Telegram instead of SSHing into servers.
Specs — Karen AI at Joong Hardware
The configuration in plain numbers. No marketing fog.
| Client | Joong Hardware (joongwarehouse.com) — Jamaican wholesale hardware operation |
|---|---|
| IrieVybz AI tier | AI Autopilot ($250/mo) with Karen dev MCP add-on |
| Channels Karen runs | WhatsApp, voice (Twilio + ElevenLabs), Telegram (operator side), web chat |
| POS surface | /cashier/ web app — AI search, manager-PIN OTP, recent-transaction dropdown, past-transaction multi-term search, fulfillment popup, MOQ enforcement |
| Dev MCP toolset | 80+ tools — dev_sql, files, git, deploy, shell. Operator workflow surface for Joong's owner. |
| Database | PostgreSQL with per-tenant isolation + row-level pg_hba TCP-auth lockdown |
| Hosting | Hetzner VPS, Docker compose stack, EU + Jamaica sovereign region |
| Source of truth (code) | joonghardware.com GitHub repo (private) |
| Setup time (initial) | 48–72 hours base + 1 sprint for dev MCP customization |
| Setup time (replication) | 72 hours for a new hardware wholesaler using the Joong template |
| Languages supported | English; Jamaican Patois on production tenants |
| Data sovereignty | Self-hosted, encrypted-at-rest Postgres, no third-party data custodian |
Why Karen vs. a generic POS chatbot at Joong Hardware
Six specific differentiators between the IrieVybz AI deployment at Joong and the off-the-shelf POS or chatbot integrations a hardware wholesaler typically evaluates.
- Two interfaces, one brain. Karen is both the customer-facing assistant (WhatsApp, voice, web) and the operator's command surface (Telegram + dev MCP). Same data model, same memory, no integration glue.
- Operator-builder MCP, not just chat. 80+ dev tools (dev_sql, files, git, deploy, shell) live inside Karen. The owner runs database queries, deploys, and file edits from Telegram messages — no SSH, no shell access required for daily ops.
- POS-aware, not POS-replacement. Karen wraps the existing /cashier/ flow with AI search, manager-PIN OTP, recent-transaction lookup, and MOQ enforcement instead of forcing a rip-and-replace.
- Sovereign Jamaican hosting. Joong's data lives on a Hetzner VPS in a Jamaica-sovereign region with an EU mirror. No third-party SaaS data custodian.
- Cross-tenant leak protection at the database layer. pg_hba TCP-auth rejects joong_user from any database except joong_hardware — a database-level safeguard, not just an application-level check.
- Template reusable for any hardware wholesaler. The Joong configuration is the canonical replication source for other wholesale and trade-counter operations.
Who else this configuration fits
Five audience + scenario pairs where the Joong Hardware setup is a near-drop-in template.
- Hardware wholesalers with call-heavy ops — counter businesses where 60%+ of inbound is SKU and stock checks on WhatsApp and voice. Karen answers from the live product table.
- Building-supply retailers in the Caribbean — operators who want an AI assistant that handles Patois-style customer queries without sounding like a Silicon Valley bot.
- Multi-cashier counter operations — businesses needing manager-PIN OTP for overrides and a clean past-transaction search at the POS without buying a full new POS suite.
- Owner-operators who deploy their own code — operator-builders who want a Telegram-native interface for git, deploys, and database access via dev MCP instead of an admin web UI.
- Trade-supply businesses worried about cross-tenant data leaks — operations that need database-level (not just application-level) tenant isolation before they will hand over customer data.
Frequently asked questions — Joong Hardware × Karen AI
Straight answers about the Joong deployment, the tier, the data architecture, and how to replicate the setup.
What is the Joong Hardware case study about?
Which IrieVybz AI tier does Joong Hardware run on?
What does Karen do day-to-day for Joong Hardware?
Can a similar setup work for my hardware or building-supply business?
Where is Joong Hardware's data stored?
How is Karen at Joong Hardware different from a chatbot?
Customer reviews — Joong Hardware × Karen AI
IrieVybz AI is a new operator-first platform. Public attributed testimonials from Joong Hardware are being collected — until they're signed and live, the proof is the live deployment itself and the configuration documented above.
Proof in lieu of public testimonial: Joong Hardware's site (joongwarehouse.com), the dev MCP-driven workflow, and the per-tenant database isolation are independently verifiable.