Admin backend choice — YukonIT

Context

YukonIT needs an admin backend for managing:

• Medusa e-commerce (products, orders, customers)
• POS (inventory, staff, locations)
• EVE AI staff (conversations, memory, workflows)
• KB (knowledge base for customers)
• Storefront (content, pages)

Option 1: Nuxt UI Pro Dashboard

Source: https://ui.nuxt.com/templates (dashboard template)

What it is: A full admin dashboard built on Nuxt 3 + Nuxt UI Pro. Pre-built components: sidebar, data tables, charts, forms, modals, dark mode.

Pros:

• Modern, polished UI out of the box
• Vue/Nuxt ecosystem — same stack as our docs-site and pulse-site
• Highly customizable (components are yours to modify)
• No separate admin service — it's a Nuxt app that calls Medusa's Admin API
• Can embed EVE chat, POS status, KB management in one place
• Self-hosted, no licensing cost

Cons:

• You build the admin features yourself (CRUD for products, orders, etc.)
• Medusa's Admin API is the backend — you're building a custom admin UI on top
• Maintenance: every Medusa update may need UI changes
• No built-in RBAC — you implement it

Effort: Medium (2-3 weeks for MVP admin)

Option 2: Medusa V2 Admin + POS

Source: Medusa's built-in admin dashboard (Medusa Admin)

What it is: Medusa ships a full admin dashboard at /app (React-based). It handles products, orders, customers, inventory, pricing, promotions, settings. POS (Agilo) connects to the same Admin API.

Pros:

• Zero admin UI to build — Medusa provides it
• Full feature coverage: products, orders, customers, inventory, discounts, shipping
• POS works against the same backend automatically
• Medusa maintains it — updates come with the platform
• Built-in RBAC (admin users, roles)

Cons:

• Less customizable — you're stuck with Medusa's admin UX
• React-based (different stack from our Nuxt sites)
• Harder to embed EVE chat or custom KB management
• Medusa's admin is "good enough" but not tailored to our 3-in-1 product

Recommendation (Sol's engineering lane)

Hybrid: Option 2 for commerce admin + Option 1 for the customer-facing dashboard.

• Medusa Admin (/app) handles the heavy commerce lifting: products, orders, inventory, customers, discounts, shipping. Don't rebuild what Medusa gives free.
• Nuxt UI Pro Dashboard as a thin layer on top for:
  • Tenant management (provisioning, status, health)
  • EVE conversation viewer + memory browser
  • POS status + offline queue monitor
  • KB editor (for customer self-help)
  • Cross-tenant overview (for us, the operators)

This avoids rebuilding Medusa's admin (weeks of work) while giving us a custom surface for the things Medusa doesn't do (EVE, POS status, tenant mgmt).

What this means for the build

1. Medusa Admin is ready out of the box (no build needed)
2. Nuxt dashboard is a new project (scaffold from ui.nuxt.com template)
3. The dashboard calls Medusa Admin API + our own tenant/EVE/POS APIs
4. Auth: Medusa admin users for commerce; our own auth for the dashboard layer

Open questions for Young

1. Do we need a single admin for all tenants, or per-tenant admins?
2. Should the KB be editable by tenants, or only by us?
3. EVE conversation history — who can see it? (tenant admin only? us only?)