Products as services — what the three catalogues actually contain

Young, 2026-10-18: "these are the products that we are offered as services, study it and add to services-pricing-model-aud.md" — naming three catalogues: eve.dev/templates, medusajs.com/starters, nuxt.com/templates.

Method. All three catalogues were read live today. eve.dev and medusajs.com render client-side, so both were read through a real browser (document.body.innerText), not the static fetch — a static fetch of eve.dev returns only 847 characters of the 4,754 rendered. Counts below are what the catalogues actually list.

Why this matters commercially. Each catalogue entry is a deployable starting point, and every one is licence-clean for resale. That is the raw material of a product ladder: we are not inventing products, we are packaging templates we can already run.

1. The three catalogues, counted

Licence cautions found (not all entries are equal):

• Nuxt's catalogue mixes MIT, Premium (paid licence) and Freemium. Premium entries — Charts Planner Dashboard, Nuxt Starter Kit, Charts Dashboard, Charts Dashboard shadcn/vue, DailyHub, Materio Admin, Nuxter, Shadcn Landing Pro, Sokol eCommerce Minimal, Spike Admin, Supastarter, SuperSaaS — cannot be resold without buying a licence each time. They are excluded from our ladder by default. Nuxt itself is MIT.3
• Medusa core is MIT, so a tenant's commerce backend is fully ownable.11 Agilo's POS starter is MIT.[13]15
• Docus is MIT — already running as our docs site.12

2. eve — 18 agent templates → our AI-staff product

The catalogue splits into 3 featured and 15 more.1

Featured: Web Chat Agent (Next.js chat with per-user long-term memory, Better Auth, Drizzle, Neon, Upstash Redis) · Company Brain (answers employee questions in Slack from dbt models) · Software Factory (Foreman — GitHub/Linear tasks through classifier → analyst → implementer → reviewer, delivers a reviewed PR).1

More (15): Full Stack Agent with Python Backend · Voice Agent · Slack Assistant · Data Analyst · Contentful Assistant · Team Knowledge Assistant · Memory Agent · TanStack Start Chat (password-protected) · Marketing Team Coordinator · iMessage Agent as a Service · GitHub Project Maintainer · Social Media Manager · Incident Investigation Assistant · Sanity Content Assistant · Company Design Assistant.1

What we can actually sell from this

Deliberately excluded: the Slack-only and vendor-locked templates (Contentful, Sanity, Datadog, Typefully, Linq). They sell someone else's integration, not our hosting — the tenant would need that vendor anyway. Note also that eve is Apache-2.0, so agent services are resellable.16

3. Medusa — 12 starters → our commerce product

Core team (2): B2C Starter (Next.js 15 storefront: customer accounts, checkout, product pages) and B2B Starter (company-employee management, draft orders, quotes, cart approvals, spending limits, bulk add-to-cart, per-client price lists).2

Specialized (10):2

What this gives the ladder

This is the strongest catalogue for us because the backend is shared — one Medusa instance per tenant, and the storefront is a swappable template. That turns storefront type into a product variant, not a new build:

• Commerce (base) → B2C Starter
• Commerce + POS → B2C + Agilo Retail POS
• B2B → B2B Starter (or the industrial portal)
• Marketplace → Rigby (a different, larger product — commission logic)
• Configurator → Made-to-Order (a genuine upsell: live pricing)

Excluded: Marketplace is a different business model (we become a platform-of-platforms). It should be a separate tier, not a checkbox.

4. Nuxt — 43 templates → our site/KB/dashboard product

Filtered to MIT only (Premium excluded), the useful set:3

Docs & content: Docus (our docs stack) · Docs (Nuxt UI) · Shadcn Docs Template · Content Wind · Changelog · The Green Chronicle (blog) · Nuxt Shopify Template.

Landing & marketing: Landing (Nuxt UI) · Nuxtship · Shadcn Landing Pro (premium) · Glide.ai · Canvas (portfolio) · Hato (portfolio) · Zooper · Portfolio.

Dashboards/admin: Dashboard (Nuxt UI) · Nuxt Shadcn Dashboard · Materio (premium) · Spike Admin (premium) · Charts Dashboard (premium).

Apps/SaaS: AI Chatbot (auth + chat history) · SaaS · Atidone · Habit · Happy Paws · Editor (TipTap + AI) · Agency OS · Supastarter (premium).

What this gives the ladder

• KB / Docs site → Docus — the same stack we already run, so the marginal build is a port, not a project.12
• Business landing → Landing (Nuxt UI) or Nuxtship.
• Client ops dashboard → Dashboard (Nuxt UI); this is also the component family our own fleet dashboard rides.
• AI Chatbot → an alternative runtime for the EVE web-chat product.

The strategic point: all three catalogues converge on one stack — Nuxt/Nuxt UI for the front, Medusa for commerce, eve for agents. A tenant can be sold any combination without us maintaining three separate platforms.

5. Proposed additions to services-pricing-model-aud.md

The existing doc prices infrastructure (domain, email, compute, AI basis) and three tiers (Solo A$119 / Shop A$229 / extra location +A$75). What is missing is the product layer — what the tenant actually gets, named as products. The proposed addition, for Mira to price and merge:

5a. Product catalogue (what we offer as services)

5b. Why these prices sit where they do

The infrastructure cost is already priced and is near-zero marginal — the existing doc measures A$6.87–9.42/tenant/mo for the core (storage, bandwidth, compute, shared AI). A template add-on therefore carries almost no cost; its price reflects build and support labour, which is what the tenant is really buying. That is why the ladder is priced per product, not per resource.

5c. New cost lines the existing doc does not carry

5d. What stays un-priced (stated, not estimated)

• Support load per product — the real cost driver, unknown until the yukonit pilot runs 30 days.
• Premium-template licence fees — if a tenant insists on a paid Nuxt template, the licence is a pass-through cost we have not quoted.
• Marketplace commission handling — a different business model; needs its own plan, not a line in this one.

6. Findings for Min (register) and Sol (build)

1. Duplicate filename. product-catalogue-vercel-grounded.md exists twice — in decisions/ (Mira, 2026-10-17, 106 lines) and research/ (Sol, 2026-10-18, 76 lines). They are different documents sharing one name, so every [product-catalogue-vercel-grounded](product-catalogue-vercel-grounded) wikilink resolves ambiguously. Two homes for one name is the defect. One must be renamed.
2. A stray shell command is committed at the end of research/product-catalogue-vercel-grounded.md — the literal text cd /home/lab/SolOS/vault && git add … && git push origin main was saved into the document instead of being run. Cosmetic, but it is in git history.
3. Docs/index.md still does not list these sections (raised in my vault verification) — so none of this is reachable from the published docs nav.

Honest limits

• Entry counts are from today's rendered catalogues; catalogues change.
• I verified licence family (MIT/Apache/premium) per entry, not each template's transitive dependency tree. A template can be MIT and still pull a non-MIT dependency — that check belongs at build time, per template chosen.
• The prices in §5a are proposals in my lane's read of the catalogue, not costed by Mira. They must be reconciled against her business plan before any tenant sees them.
• I did not verify that each Medusa starter runs on our ARM (aarch64) prod node. React Native/Expo POS in particular needs a real device test.

Sources

Sources

1 https://eve.dev/templates — eve — Templates (agent catalogue) 2 https://medusajs.com/starters — Medusa — Starters catalogue 3 https://nuxt.com/templates — Nuxt — Community Templates 11 https://github.com/medusajs/medusa/blob/master/LICENSE — Medusa — MIT License 12 https://github.com/nuxt-content/docus — Docus — MIT License (repo) 13 https://github.com/Agilo/medusa-pos-starter — Agilo medusa-pos-starter — MIT License (repo) 15 https://medusajs.com/blog/agilo-starter-pos — Medusa — Agilo POS Starter announcement 16 https://github.com/vercel/eve — Vercel eve — Apache-2.0