EVE — templates and features (2026-10-18)

Scope: EVE template catalogue and feature set for the vhost product line. EVE is the AI receptionist / agent layer for tenant sites. Feeds yukonit-admin-backend-study.md and services-pricing-model-aud.md.

1. Templates (EVE)

EVE is an open-source AI agent framework (Apache-2.0, 5,591★) designed for building AI-powered applications. Templates are starter apps.

EVE official templates

EVE community templates

2. Feature catalogue (EVE)

Core (Apache-2.0, included)

• Agent runtime — LLM-backed agent with tool calling, memory, RAG
• Streaming — SSE-based streaming responses
• Tool calling — function calling, API integration, database queries
• Memory — conversation history, entity extraction, semantic search
• RAG — retrieval-augmented generation over documents
• Multi-model — OpenAI, Anthropic, Google, local models
• Webhooks — event-driven triggers
• API — REST + WebSocket endpoints
• Auth — API key, JWT, OAuth
• Rate limiting — per-user, per-tenant

Integrations

• Medusa — product/order/customer queries via Store API (HIL-gated Admin writes)
• Nuxt — chat widget embeddable in Nuxt apps
• Slack/Discord/Telegram — messaging platform bots
• Email — inbound/outbound email processing
• Database — Postgres, SQLite, Redis

Admin surface

• EVE Admin — agent configuration, prompt management, tool registry
• Analytics — conversation metrics, resolution rates, CSAT
• Knowledge base — document upload, indexing, retrieval

3. What we sell (product mapping)

4. EVE receptionist role in KB flow

Per yukonit-admin-backend-study.md:

1. First-line support — answers customer questions from KB articles
2. Checkout assistant — helps customers complete purchases
3. Order status — queries Medusa Store API for order info
4. HIL-gated actions — refund requests, bulk pricing → land as draft orders in Medusa Admin awaiting human approval
5. Escalation — routes complex issues to human support

What EVE does NOT do

• Modify prices or inventory (HIL-gated)
• Process refunds without approval (HIL-gated)
• Access other tenants' data (per-tenant isolation)
• Store secrets (config-only, 0600 env files)

5. Licence

• EVE framework: Apache-2.0 — sellable, no per-seat, no revenue share
• EVE templates: Apache-2.0 — sellable
• EVE Cloud: commercial — we don't use it (self-hosted per tenant)

End-to-end licence-clean.

6. Open items

1. EVE beta status — make it work for our business (Young's ruling)
2. Protocol drift risk — EVE beta may change APIs; pin version + test
3. Multi-tenant isolation — one EVE instance per tenant vs shared with per-tenant data scoping (docker-systems-design says per-tenant compose)
4. EVE model selection — which LLM for receptionist (free tier vs paid)
5. EVE memory — per-tenant memory scope, not cross-tenant
6. EVE + Medusa integration — Store API read + HIL-gated Admin writes (verified pattern in medusa-eve-integration-study)