Changelog

The starter is no longer the only thing on the shelf. Muse Collection is a publishing library of production landing pages, sold with MuseMVP while founding licenses are open, and as its own catalog after that.

How you can buy

• Founding License — $99. MuseMVP starter, handbook, community, and the Collection library for life: every live issue plus every issue published after you buy. After this window, the split is $149 for the starter and $79 for the library.
• Collection library — $79 (was $129). Lifetime access to every live landing page and every future issue. Does not include the MuseMVP starter.
• Single issue — $29. One landing page, one license. Future issues are not included.
• Existing MuseMVP licenses already include the library. Source access stays in the same GitHub and Discord channels; you do not buy again.

The founding window is capped at 30 licenses and currently ends 26 August 2026 (23:59 Asia/Shanghai). Browse the catalog at /templates.

The sheet

Seven live issues, two still in production. Three across, three down. Open any tile for the catalog.

• 01

  Zeus

  The night desk for operational work

• 02

  Scrip

  Print the usage. Keep the books.

• 03

  Hikari

  A lamp for language

• 04

  Athena

  The brief you can sign

• 05

  Meridian

  Plot the work, keep the helm

• 06

  Quire

  Nested pages, floating on a blotter

• 07

  Aoi

  Name her. Keep the call.

• 08·Next issueOn press

  Vesper

  Dusk vitrine

• 09·Further onIn manuscript

  Folio

  Unbound proofs

A library or founding license already covers Vesper and Folio when they ship.

Why this sits next to the starter

MuseMVP remains the production baseline: auth, billing, i18n, and deploy-anywhere. Collection is the public-surface layer you can drop onto that baseline — buy one look, lock the whole library, or take the founding bundle before starter and templates are sold separately.

This is a breaking configuration change for existing forks: gateway keys and S3 credentials are no longer read from env at runtime.

Why the template changed

• Payment and storage secrets used to sit next to mail and OAuth in .env. Rotating a key meant a rebuild, and day-two operations mixed with bootstrap secrets.
• Runtime now reads only the app_setting table for billing and S3. There is no environment-variable fallback after you import leftover local values.

What you must set

• Add MUSE_SETTINGS_SECRET (at least 32 characters). It wraps encrypted settings with HKDF-SHA256 + AES-256-GCM and is never stored in the database. A production runtime missing this secret fails at startup.
• Apply migration 0001_dry_terror.sql so app_setting and app_setting_revision exist (pnpm drizzle:migrate).
• Create an admin, then open Admin → Runtime settings (/app/admin/settings). Save gateway credentials, checkout product IDs, and S3 settings. Use Test connection before going live.
• Optional one-shot: pnpm muse:settings:import copies leftover local gateway/storage credentials into the database. Runtime never reads those env vars afterward. Checkout product IDs are entered in the admin page, not env.

Billing and checkout

• Public pricing still uses stable app plan IDs (pro_monthly, pro_yearly, lifetime). Provider product IDs live in billing.productMap.
• Direct checkout mode is gone. Paid plans launch through Muse Billing against the stored default gateway (Creem, Stripe, Dodo, or Waffo).
• On the admin billing tab, the default-gateway card stays at the top. Each provider starts collapsed; expand it to edit credentials and that gateway's product IDs together. Badges show Default, Configured / Not configured, mapped product-ID count, and Unsaved.

Storage and deploy

• S3 access key, secret, endpoint, and the avatars bucket are admin settings. NEXT_PUBLIC_AVATARS_PROXY_URL stays in env because the browser builds avatar URLs from it.
• Docker, Vercel, Cloudflare Workers, and EdgeOne production env lists now require MUSE_SETTINGS_SECRET and no longer treat gateway or S3 keys as env.

This release gives every user visibility and control over their stored files, and rebuilds the API key management experience.

Storage Asset Management Page

• A new Settings > Storage page lets users manage their files in S3-compatible storage: list uploads with usage stats, preview assets, generate presigned download links, and delete files individually or in bulk.
• It is backed by new authenticated /assets Hono routes — every operation is strictly scoped to the user's own storage prefix, with thorough key validation and 300+ lines of service tests.

API Keys & Login Experience

• The API key settings were rebuilt around a table with a per-key actions menu (details, test, delete) and an on-demand verification dialog, so users can confirm a freshly created key actually works without leaving the page.
• The OTP login form layout was polished, with cleaner alignment of the password field and the forgot-password link.

This release focuses on deployment stability and dependency maintenance.

Updates

• wrangler.jsonc now sets a 300,000 ms CPU limit, so heavier requests on Cloudflare Workers deployments no longer trip the default CPU cap.
• Fixed the cookie@2 breaking change (parse renamed to parseCookie) that broke builds, keeping the template buildable on the latest dependencies.
• Routine Dependabot batches kept the dependency tree current through June (roughly 125 package bumps across four merged groups).

This release completes a security audit across authentication, billing, and infrastructure, and raises the engineering quality baseline across the board.

Security Fixes

• Closed a payment bypass: Creem and Stripe webhooks no longer fall back to parsing unverified bodies when no secret is configured — production now requires a webhook secret (mirroring the existing Dodo guard), with gateway security tests included.
• Fixed reflected XSS on the newsletter unsubscribe page and replaced the token scheme with HMAC-SHA256 signed tokens (constant-time comparison), so unsubscribe links can no longer be forged.
• All routes now send baseline security headers: HSTS, X-Frame-Options SAMEORIGIN, nosniff, Referrer-Policy, and a restrictive Permissions-Policy.

Reliability & Engineering Quality

• Server environment variables are validated at startup, so misconfigured deployments fail fast with clear errors instead of breaking mid-request.
• Three levels of App Router error boundaries (route/app/global) show localized error pages; auth emails (OTP, magic link, password reset) report real errors instead of silent success when delivery fails; the Hono API gained a central error handler and a request-body size limit.
• A CI workflow runs type-check/lint/unit on every push, Playwright e2e now runs against a production build with retries, and the webhook-to-entitlement chain has regression tests.

This release establishes the engineering convention for derivative copy customization, letting template-based projects coexist with upstream updates long-term.

Updates

• All derivative-product custom copy now lives exclusively in mvp.json (paired en/zh), leaving upstream translation files untouched — future template updates merge cleanly without i18n conflicts.
• The landing-page map and brand-adaptation references were substantially expanded, giving a clearer documented path for rebranding the public surface.

This release trims the template: low-usage, high-maintenance built-ins were removed so buyers start from a leaner baseline.

AI Chat Removed

• The built-in AI chat workspace — pages, Hono API routes, database queries, UI components, and the AI SDK dependencies — was removed, so projects that do not ship AI features no longer carry the extra code, dependencies, or attack surface (8 package.json entries dropped, ~3,000 lines of feature code removed).
• Breaking change: migration 0005 drops the ai_chat_conversation and ai_chat_message tables (CASCADE). Derivative projects that used AI chat should export any conversation data before pulling this upgrade.

Fortress Layout Removed

• The unmaintained fortress account-layout variant (~300 lines) was deleted, leaving the default layout as the single built-in path and reducing customization confusion; other shapes can be added as custom layout variants per the docs.

This release turns the admin panel into a complete user operations center, so routine account work no longer requires touching the database.

Admin User Management

• Create users, edit profiles, ban/unban (with reason and expiry), set passwords, and inspect or revoke active sessions — all through dedicated dialogs.
• Admins can impersonate a user to reproduce issues, with a persistent ImpersonationBanner making the impersonation state obvious and one click to exit.
• The user list surfaces billing contract information, and rendering was hardened with fallback text and avatar styling.

Tooling & Tests

• A batch user-creation CLI script with interactive prompts speeds up seeding demo or team accounts, and data-table pagination now reports accurate total row counts.
• The whole suite ships with new contract tests, unit tests, and admin-route e2e smoke tests.

This release polishes the landing page community entry point and the default brand assets.

Updates

• The landing header (desktop controls and mobile menu) gains a config-driven Discord button, so a single config entry surfaces your community link.
• Default favicon, app icons, OG image, and hero images were redesigned at higher resolution, giving fresh deployments a polished look out of the box.
• Locale handling was refactored to an enum with safer default-locale resolution, reducing i18n misconfiguration risk in derivative projects.

This release focuses on subscription relationship management: users can control subscription emails themselves, and billing gains an integration-free direct checkout mode.

Subscription Preferences

• A new Settings > Subscriptions page lets users manage their subscription email preference on their own, so opting out no longer requires manual support; it is backed by a new muse_subscribe_enabled column with its migration included.
• The admin users list gains a subscription status column with filtering, making opt-out audits quick.

Direct Checkout Billing Mode

• Pricing plans can now link straight to the payment provider's hosted checkout or portal page, with a DirectCheckoutBillingNotice explaining that subscriptions are managed externally — ideal when you do not want to wire in-app checkout flows.
• Checkout mode resolution logic ships with unit tests to keep configuration behavior predictable.

This release adds Dodo Payments as a first-class Muse Billing gateway, so teams can launch checkout, webhooks, and customer portal flows alongside Creem and Stripe.

Dodo Payments Integration

• Added the muse_dodo gateway with checkout session launch, webhook verification, contract sync, and customer portal links.
• Extended product catalog and environment templates with Dodo API keys, webhook secrets, environment mode, and lifetime/monthly/yearly product ID variables.
• Registered the gateway in Muse Billing orchestration with unit and API coverage for gateway behavior, mappers, and access resolution.

This release introduces EdgeOne as a first-class deployment target alongside Cloudflare, Docker, and Vercel, and brings all project dependencies up to date with all tests passing.

New Features

• Added EdgeOne as a supported deployment platform with full configuration and demo URL support.

Dependency Upgrades

• Upgraded all project dependencies to their latest versions.
• All unit tests, API tests, and e2e tests have passed successfully.

Improvements

• Streamlined deployment descriptions and updated UI styles for a cleaner experience.
• Refreshed hero images for both dark and light themes.
• Replaced deployment images for Cloudflare, Docker, and Vercel for consistency with the new EdgeOne addition.

This release strengthens the email sending pipeline with multi-provider support and robust error handling, cleans up authentication form styling, and brings the dependency tree up to date.

Product

• Enhanced email configuration to support multiple providers (Resend and Cloudflare), with environment examples updated accordingly
• Improved email sending logic with reply-to address support and better error handling for delivery failures across contact and newsletter routes
• Removed decorative asterisks from authentication form titles (login, signup, forgot password, reset password, 2FA verify) for a cleaner interface
• Added comprehensive unit tests for contact route, newsletter route, and mail sending logic

Code

• Batch-updated 26 dependencies including Next.js 16.2.5, React 19.2.6, fumadocs-mdx 15.0.0, Zod 4.4.3, and Wrangler 4.89.1
• Renamed next.config.ts to next.config.mts for explicit TypeScript module config with Cloudflare and MDX support

A week of housekeeping focused on dependency freshness, layout responsiveness, and contributor-facing documentation.

Dependency Updates

• Bumped 15 packages across the monorepo to latest compatible versions
• Bumped 22 additional packages including major framework and utility upgrades
• Resolved merge conflicts from Dependabot PR #52

UI and Layout

• Refactored the default layout shell to use flexbox for improved responsiveness across screen sizes

Documentation and Skills

• Updated skill file paths and enhanced brainstorming documentation for agent workflows
• Improved Claude configuration docs covering context management and verification processes

Related Commits

• 9c2cc37 chore(deps): bump the npm-all group across 1 directory with 15 updates
• 3df380e chore(skills): update skill paths and enhance brainstorming documentation
• 77e8153 docs(claude): enhance documentation for context management and verification processes
• eb381cf chore(deps): bump the npm-all group across 1 directory with 22 updates
• e029b50 refactor(layout): enhance component structure with flexbox for improved responsiveness

This release focuses on operational control and authentication flow quality.

What changed

• Added admin user ban and unban functionality.
• Added supporting design spec documentation for user moderation.
• Improved auth and settings testability with additional data-testid coverage.
• Refined redirect handling and type safety in auth-related flows.
• Optimized changelog timeline layout alignment and restored sticky date behavior.

Commits included

• 91260b7 feat(admin-users): implement user ban and unban functionality
• e29f9b1 docs(spec): add admin user ban design
• 45bf4ef feat(two-factor-auth): enhance TwoFactorVerifyForm with data-testid attributes for improved testability
• d655ee4 feat(password-input): refactor PasswordInput component to use forwardRef and improve type safety
• 91be374 feat(settings): add data-testid attributes for improved testability in confirmation and delete account components
• e470adb refactor(auth): streamline redirect handling and enhance type safety

The avatar upload workflow is now end-to-end production ready.

What changed

• Implemented avatar upload using signed URL generation.
• Added and refined real API tests for upload URL validation and error handling.
• Improved test bootstrap and dynamic path generation for better reliability.
• Updated storage-related documentation and environment variable guidance.

Commits included

• dc08c88 feat: implement avatar upload functionality with signed URL generation
• 0f69648 feat(api): implement avatar upload with signed URL and enhance test coverage
• f866e80 test: refactor avatar upload real API tests for improved structure and functionality
• 1f27df3 test: enhance avatar upload URL validation in real API tests
• 3349f8f test: bootstrap environment for avatar upload tests and improve error messaging
• 07c1a48 refactor: enhance avatar upload tests with dynamic path generation
• f5170d8 docs: enhance documentation for storage environment variable checks and avatar upload URL generation

This update introduced practical product controls for both developers and operators.

What changed

• Added API token feature support with conditional rendering paths.
• Added hideBorderX configuration for more flexible header presentation.
• Simplified default layout header structure for a cleaner top-level navigation area.
• Updated tooling config to exclude skills directory from Biome and TypeScript checks.

Commits included

• d563264 feat: implement API tokens feature with conditional rendering
• 546c9a0 feat: add hideBorderX configuration option for header
• 90bec07 refactor: simplify header structure in default layout
• ddac416 chore: update biome and tsconfig to exclude skills directory

All planned SaaS capabilities are now complete.

MuseMVP now ships with a full end-to-end SaaS feature set, so teams can focus on product differentiation instead of rebuilding common infrastructure.

Completed SaaS scope

• Authentication lifecycle, account setup, and user management.
• Billing flows with subscription-ready configuration.
• Admin and settings surfaces for day-to-day operations.
• Public content system for docs, blog, legal pages, and changelog.

MuseMVP is officially released as of 2026-03-10.

This release marks the point where the project is ready to be used as a real SaaS product foundation, not only a starter template.

Related links

• Docs: https://musemvp.com/docs
• Features: https://musemvp.com/features
• MuseMVP Docs: https://musemvp.com/docs

Related commits (selected)

• 91260b7 feat(admin-users): implement user ban and unban functionality
• e29f9b1 docs(spec): add admin user ban design
• 45bf4ef feat(two-factor-auth): enhance TwoFactorVerifyForm with data-testid attributes for improved testability
• d655ee4 feat(password-input): refactor PasswordInput component to use forwardRef and improve type safety
• 91be374 feat(settings): add data-testid attributes for improved testability in confirmation and delete account components
• e470adb refactor(auth): streamline redirect handling and enhance type safety
• 8a9bc25 refactor: enhance muse-billing module with improved documentation (#45)
• 9050bb6 feat(agents): enhance feature delivery and testing guidelines (#41)
• 36eb81d chore(deps): update package versions in package.json and pnpm-lock.yaml
• 0f69648 feat(api): implement avatar upload with signed URL and enhance test coverage (#40)
• dc08c88 feat: implement avatar upload functionality with signed URL generation
• 383e1c0 chore: enhance API key management and update related tests
• 6cf1d0d feat: add test framework module + optimize AI rules file + update nextjs and better-auth. (#31)
• 43175cd refactor: restructure blog and legal related pages; optimize landing page rendering (#29)
• cbc4963 feat: introduce MuseMVP skill for customizing SaaS app home route
• 7f96f88 refactor: migrate from content-collections to Fumadocs MDX and update related configurations
• a0ac45f feat: enable conditional display of DeleteAccountForm based on configuration
• d563264 feat: implement API tokens feature with conditional rendering
• 546c9a0 feat: add hideBorderX configuration option for header
• 50855ce feat: add new skills and documentation for brainstorming and better-auth practices
• fd14861 refactor: restructure landing page components for improved modularity
• ec953dc fix: update pricing section configuration based on billing settings
• dfc11be feat: add discount code functionality to pricing and error handling
• ···