Nuxter vs Nuxt UI SaaS template

Stack and hosting

Nuxter is a Nuxt 4 app on Vue 3, Nuxt UI 4 and Tailwind CSS 4, written in TypeScript, and it builds into one Cloudflare Worker. Its queue, file storage, cache, mail, rate limiting, AI and database connection are bindings, services Cloudflare attaches to the Worker by name, all declared in wrangler.jsonc. You learn one platform and run one Cloudflare account, and the parts arrive wired to each other. The trade is that the app runs on Cloudflare Workers and nowhere else.

A shipped GitHub Actions workflow deploys main after CI passes. It builds, applies database migrations, then uploads the Worker, so a schema change and the code that needs it go out together. The deployment docs list the command that creates each resource.

The template is built on the same stack: on 29 September 2026 its package.json declared nuxt ^4.5.2 and @nuxt/ui ^4.11.2, the same versions Nuxter uses, so what you learn about Nuxt UI's components carries over.

The template ships no server code of its own: its repository has no server/ directory, and package.json lists no auth, database, payment or mail library. Its nuxt.config.ts sets no host and builds the pages to static HTML ahead of time, following links from the home page.

Sign-in and accounts

You choose Nuxter's sign-in methods in one block of starter.config.ts: email and password or magic links as the primary method, then passkeys, authenticator codes with recovery codes, and GitHub and Google sign-in. Password reset and email verification come with it, and a method you switch off has no route at all. The auth docs cover each one.

Sessions are rows in the database, checked on every request, so a user sees each signed-in device and can sign one out, and suspending an account takes effect at once. Users can also change their email address, download their data as JSON and delete their account, with 30 days to restore it by default.

The template ships login and signup pages, with Google and GitHub buttons. Its landing copy says they are ready for you to "connect your backend", and its package.json names no auth library. An unmerged auth branch adds email and password sign-in with Better Auth on NuxtHub; the create command delivers main. On main you choose a library and build sessions, password reset and verification mail yourself, which is the part Nuxter ships.

Organizations and permissions

In Nuxter the organization owns the plan, the members and the seats. Owners, admins and members hold roles built from named permissions, invitations go out by email with a chosen role, each plan caps how many members an organization may hold, and an audit trail records joins, removals, role changes and plan changes. An optional second level puts branches or sites under a company.

Nuxter settles the cases a team product hits early: an admin cannot make anyone an owner, the last owner cannot leave, and two people cannot take the last seat at once. Your own routes check named permissions that come from a role or from the organization's plan. When a better plan would allow the request, the route answers 402 (payment required), so your screen can offer the upgrade.

A search of the SaaS template's repository finds no code for teams. Nuxt UI publishes a separate Dashboard template, listed as working with the SaaS template, whose team switcher, members list and role select run on sample data.

Payments and billing

Nuxter's pricing page is built from the plans in starter.config.ts, and its buttons open a hosted checkout at Stripe, Polar, Lemon Squeezy or Creem, each covering subscriptions and one-time purchases. Around the checkout it handles what a subscription business meets in its first months, as the payments docs describe:

A merchant of record is the provider that sells to your customer in its own name and files the tax.

The template's pricing page shows three plan cards with a monthly and yearly toggle, a logo strip and an FAQ, read from content/2.pricing.yml. You replace the plans in that file with your own and connect the buttons to a provider, since the repository contains no payment code. The webhooks, trials and failed-renewal handling in the table above are then yours to write.

Database, jobs and files

Nuxter stores app data in Postgres through Drizzle ORM, with 24 tables and migrations in two chains, one for the kit's tables and one for yours, so a kit update never collides with a migration you wrote. You host the database at a provider you choose, such as Neon or Supabase, and the Worker reaches it through Hyperdrive, Cloudflare's connector to outside databases. pnpm dev starts an embedded Postgres, so a fresh clone runs with no database server to install.

Background jobs run on Cloudflare Queues. A job is one typed file, and a failed one retries with growing delays. After its last retry it moves to a dead letter queue, a holding queue for jobs that keep failing, where the Worker reports it. A daily cron runs cleanup tasks, and uploads go to Cloudflare R2 under rules per purpose for format, size and access, with avatar and organization photo uploads wired.

The template's one database setting belongs to Nuxt Content, which keeps the site's pages in its own SQLite store. Its package.json lists no ORM or database driver, and a search of its repository finds no jobs, queues, cron or upload code, so each is yours to pick when the product needs it.

Email and notifications

Nuxter sends mail through Cloudflare Email Sending or Resend, falls through to the next provider when one fails, and queues the mail for retry when the failure looks temporary. Nine account mails ship, built from templates compiled at build time, in English and Serbian, among them sign-in links, password reset, verification, invitations and security notices. Product and marketing mail carries a one-click unsubscribe link.

Inside the app, a notification bell and drawer read from a database table, with payment notifications already wired.

The template's package.json lists no mail provider, and its repository contains no email templates.

AI

Nuxter ships a typed server module for the model calls a product makes: text, image, speech, transcription, embeddings and video. Cloudflare Workers AI, Cloudflare's hosted models, is wired through a binding and needs no API key. In config you pick a model for each job (one for copy, one for images, and so on), swap one per deploy with an environment variable, and add another provider as one file.

The template's package.json lists no AI SDK.

Content, languages and marketing pages

Nuxter's blog posts are Markdown files per language, with tags, drafts, RSS and a generated social image for each post. A GitHub Actions workflow drafts a post with an AI model, translates it and opens a pull request for you to review. Nuxter also generates a sitemap and robots.txt and keeps private pages out of search results.

The whole app ships in English and Serbian, with a language prefix in the URL (/sr/pricing), a language switcher, translated emails and hreflang tags, which tell search engines which page is which language. Each language you add gets the same routing, switcher and hreflang tags. The template sets the page language to English and has no i18n module or locale files.

The template leads on marketing pages: its landing, pricing and docs sections come ready to fill from Markdown and YAML. Both projects are built on Nuxt UI 4 and Nuxt Content 3, and MIT lets you copy those sections into a Nuxter app as long as the template's notice stays with them.

Admin and operations

Nuxter gives staff a customers list with search and filters. From it they edit or suspend an account, view the app as that customer read-only, send a reset or verification mail, clear a sign-in lockout, grant a plan and refund a one-time purchase, and each action is written to the customer's activity log.

Nuxter rate limits its sign-in, registration, email and checkout routes, and after too many failed sign-ins it locks the caller out for 15 minutes, so a password-guessing script stops without any code from you. Every response carries a Content-Security-Policy, a header that limits where a page may load scripts from, plus the usual hardening headers. Cloudflare Turnstile, Cloudflare's bot check, guards sign-in and registration once its two keys are set. A search of the template's repository finds no rate limiting or security headers.

Nuxter's dashboard reads the database: the overview chart is drawn from real activity, and the members, billing and customers pages show live rows. The SaaS template's own pages are its public pages plus login and signup. Nuxt UI's separate Dashboard template, built from the same components, runs on sample data.

Nuxter records product analytics on the server and sends them to Cloudflare Analytics Engine, PostHog or Umami, with no vendor script or tracking cookie in the browser, and each visitor's privacy choices decide whether events are sent. A server error carries a request id that the error page shows, so a customer's screenshot leads you to the log line. Errors can be forwarded to Sentry or Better Stack, and /api/health tells an uptime monitor whether the database answers. Typed feature flags with percentage rollouts ship ready to switch on. A search of the template's repository finds no analytics, feature flags, error tracking or health check.

Tests

Nuxter ships 335 test files: 230 unit, 97 component and 8 Playwright specs. Unit tests run against an embedded Postgres with the real migrations applied, and about 50 files cover payments. The included GitHub Actions workflow runs lint, a format check, typecheck, the unit and component suites and a production build, as the testing docs explain, so a changed billing rule or a kit update shows its effects in CI.

The template's one workflow runs lint and typecheck on every push. A search of its repository finds no test files, so its test suite starts with the tests you write.

Updates

Your app keeps the kit as a git remote named template. pnpm template:update brings everything the kit changed since your last update as one commit you review, so the kit's later fixes reach an app you keep building for years. A written table marks which files are the kit's and which are yours, so you know where to put code that an update will not touch.

You start from the template by copying it: the README gives npm create nuxt@latest -- -t ui/saas, and the installation docs add GitHub's Use this template button. Both projects ship a renovate.json that extends github>nuxt/renovate-config-nuxt for dependency updates, and the template's README tells you to install the Renovate GitHub app. Neither its README nor its docs mention how to bring later template changes into a project already started from it.

Docs and AI coding agents

Nuxter's docs are public before you buy, at nuxter.app/docs: 25 pages with search. The kit ships AGENTS.md, a 330-line brief with setup commands, code standards and known traps with their causes, plus short files that point Claude Code, Cursor and GitHub Copilot to it, so all three read the same instructions.

The template's own docs are seven pages: three on installing and using it, and four on writing Markdown. Its README's Documentation link points to the Nuxt UI docs.

Nuxt UI, the component library, hosts an MCP server that coding agents can query and an llms.txt index of its components. Both serve any project built with Nuxt UI, Nuxter included. The template's repository contains no instruction files for coding agents.

Price and license

Nuxter is sold as two licenses, paid once: Individual at $249 with one seat and Team at $649 with five. Both include the same code and every update, with no subscription, and the license never expires. A seat is one person, a license covers any number of your own products, and each client you build for needs its own license. The pricing page sets out the terms.

The template's license is the standard MIT text, copyright Nuxt UI Templates, and its one condition is that the copyright and permission notice stay in copies.

Support and community

Nuxter's support is by email to Devilos LLC, the company that makes it, about the kit, a purchase or a license. The public docs, which you can read before buying, and AGENTS.md, which gives your coding agent the kit's setup, standards and known traps, cover the rest.

No support channel or response time is stated for the template. Its footer links to the general Nuxt Discord, and its repository has GitHub Issues switched on.