projectadg last reviewed 2026-05-21

ZeeHost — AI restaurant host (HaaS) + landing brand

Context

Restaurants need someone (or something) to answer customer phone calls, take bookings, handle FAQs, and route urgent items to staff — without paying a full-time human host. ZeeHost is Aspire's HaaS (Host-as-a-Service) play: AI-powered phone/chat agent specialized for restaurant operations. It's also the brand vertical name for Aspire's hospitality-AI verticals.

Architecture

graph LR CALL["Guest call / chat"] --> ZH["ZeeHost<br/>AI restaurant host<br/>zeehost.ai"] ZH --> BOOK["Bookings"] ZH --> MENU["Menu / orders"] ZH --> GW["Aspire LLM Gateway"] classDef app fill:#715EE3,color:#fff,stroke:#291F50; class ZH app;

Detail

What's live (as of 2026-05-09)

Stack

Remaining for v1 voice channel

Coolify resources

Relationship to Zinga

ZeeHost is the customer-facing brand for hospitality AI; the Zinga suite is the product brand for hospitality SaaS replacements. ZeeHost = AI; Zinga = SaaS. They share infrastructure (Postgres, LLM Gateway) but distinct domains + UX. See aspire-brand-architecture.

Sub-brands using zeehost.ai or related domains

DomainWhat
chat.zeehost.aiZeeHost chat MVP
kitchen.zeehost.aiZinga Kitchen landing (Restoke replacement)
zac.zeehost.aiZac AI CFO landing (Zinga Ledgr)
becs.getzinga.com.auZingamenu BECS signup

Open questions

  1. Should ZeeHost be a separate paid SaaS, or bundled with Zinga PMS/Booking subscriptions?
  2. Voice channel before chat polish, or chat polish first?
  3. Migration plan from OpenRouter → Aspire LLM Gateway (when does this happen?)

Related

🔗 Relationships

graph LR zeehost["zeehost"]:::self zeehost --> use_postgresql_by_default["use-postgresql-by-default"] zeehost --> aspire_llm_gateway_only_egress["aspire-llm-gateway-only-egress"] zeehost --> aspire_brand_architecture["aspire-brand-architecture"] zeehost --> aspire_llm_gateway["aspire-llm-gateway"] classDef self fill:#715EE3,color:#fff,stroke:#291F50;