Nuxter vs Nuxt Starter Kit

Stack and hosting

Nuxter is one Nuxt 4 app on Nuxt UI 4, Tailwind 4 and TypeScript, built for Cloudflare Workers on purpose. Queues, file storage, cache, mail, rate limiting, AI and the database connection are all bindings, which are Cloudflare services the Worker calls by name. One file, wrangler.jsonc, declares them all. You learn one platform and run one account, with nothing to wire between services. The trade is that the app runs on Cloudflare Workers and nowhere else.

A GitHub Actions workflow deploys your main branch after CI passes: it checks the config, migrates the database and then uploads the Worker.

Nuxt Starter Kit uses Nuxt 4, Nuxt UI, Tailwind and TypeScript too. Its code is a Turborepo monorepo: the app in apps/web is assembled from Nuxt layers, each kept as its own package. Its deployment docs say it runs on any platform that supports Node.js and PostgreSQL, and cover Vercel, Netlify, Railway and a VPS.

Sign-in and accounts

You pick the sign-in method in one config block: email and password, or a magic link (a one-time sign-in link sent by email). Passkeys, authenticator-app codes (TOTP) and GitHub and Google sign-in are separate switches that combine with either.

Users see and end their sessions, read their account's security log, and can delete the account with, by default, 30 days to restore it. If a business customer's security review asks for two-factor sign-in, it is already built.

Nuxt Starter Kit builds sign-in on the Better Auth library, per its authentication docs, and stores sessions in PostgreSQL.

Organizations and permissions

Nuxter gives every account an organization at signup. The organization holds the plan and the seats. It ships with owner, admin and member roles, email invitations, a seat limit per plan checked at invitation and again at acceptance, and an audit trail of membership and plan changes. An organization can have a second level, such as branches or sites under a company, and the company's owners and admins manage every branch without joining each one. This is multi-tenancy: many customer companies share one app, and each sees only its own data. Because it is there from the first signup, you do not retrofit organizations onto your tables and routes after launch.

Routes check named permissions that come from a person's role or from the organization's plan. When a plan sells the permission and the organization does not hold that plan, the route refuses with a 402 Payment Required status, so your page can show an upgrade offer instead of an error.

Asked whether it supports teams or organizations, Nuxt Starter Kit's FAQ answers: "No, my starter kit is not built with multi-tenancy in mind. I currently also don't have this planned on my roadmap." For access control its docs describe a requireAuth() helper and a role column set to USER or ADMIN.

Payments and billing

Nuxter ships payment adapters for Stripe, Polar, Lemon Squeezy and Creem, and you list the ones you sell through in one config array, so you can start on one and add another later without rewriting checkout, webhooks or the billing pages. Polar, Lemon Squeezy and Creem act as merchant of record, the company that sells to your customer on your behalf and handles sales tax; on Stripe, one environment variable turns on Stripe Tax. Plans live in config, and the pricing page, billing pages and checkout read from it.

A customer whose card expires keeps access while they fix it, and nobody gets a second trial by cancelling and subscribing again. Each webhook is signature-checked and applied once, so a payment the provider reports twice grants access once. A full refund removes the access it paid for.

Nuxt Starter Kit takes payments through Polar as merchant of record, with the @polar-sh/better-auth plugin and a webhook endpoint. Its setup docs have you create three Polar products, Pro monthly, Pro yearly and a lifetime deal, beside a free plan, and say any other product mix needs changes in the payment layer and other parts of the codebase.

Database, jobs and files

Both kits use Postgres through Drizzle. Nuxter's pnpm dev runs an embedded Postgres (PGlite, Postgres compiled to WebAssembly), so you install no database server. Nuxt Starter Kit's docs list PostgreSQL, local or hosted, as a prerequisite and mention no bundled local database or seed script.

In production you choose the Postgres provider, such as Neon or Supabase, and the Worker reaches it through Hyperdrive, Cloudflare's connection pooler for Postgres. The kit's migrations and yours run in separate chains, so a kit update never collides with a migration you wrote. The deploy workflow migrates before it uploads the Worker, so a failed migration leaves the version already running live. Nuxt Starter Kit's deployment docs run pnpm db:migrate as a step after deploying.

Nuxter runs background jobs on Cloudflare Queues. A job is one typed file. A failed job is retried with growing delays. After the last retry it moves to a dead letter queue (a separate queue for jobs that kept failing), and Nuxter reports it to the error trackers you configure. A daily cron runs cleanup tasks. Nuxt Starter Kit's docs do not mention background jobs, queues or scheduled tasks.

Nuxter stores uploads in Cloudflare R2. Each kind of upload gets its own rules in config: the formats it accepts, a size cap, and whether anyone or only the owner can read it. Nuxter reads each file's type from its first bytes, so a file cannot pass as an image by claiming to be one. Avatar and organization photo uploads are built in. Nuxt Starter Kit's storage layer uploads to AWS S3, records each file and its owner in the database, and provides signed URLs for private files.

Email and notifications

Nuxter sends mail through Cloudflare Email Sending or Resend. When one provider fails it tries the next, and when every provider has a temporary failure it queues the mail, so a password reset sent during a short outage goes out once a provider answers again. Each mail is labelled transactional, product or marketing. Product and marketing mail skips users who opted out and carries a one-click unsubscribe header. Mail goes out in the reader's language. Inside the app, a notification bell and drawer are wired to payment events.

Nuxt Starter Kit sends through Plunk or Resend, with templates written in Nuxt Email Renderer, a set of Vue components for email. An admin can preview every email and send a test from the admin section. Its docs do not mention queued retries, and inside the app it has toast messages and a banner an admin sets for all users.

AI

Nuxter ships the typed server calls a product makes to AI models: text, image, speech, transcription, embeddings and video. They run on Cloudflare Workers AI through the Worker's binding, so there is no API key to manage. In config each model is named for the job it does, such as copy or illustration, and an environment variable swaps it per deploy. You add another provider, such as OpenAI, by writing one adapter file and a config entry.

Nuxt Starter Kit's site and docs describe no AI feature, SDK or model provider.

Content, languages and marketing pages

Nuxter ships a Markdown blog with tags, drafts and RSS, and GitHub Actions workflows that draft a post with an AI model, translate it and open a pull request for you to review. Sitemaps, social share images and language alternates are generated. Analytics are recorded from the server, with no vendor script or tracking cookie, so with the default settings visitors see no cookie banner. Events go to Cloudflare Analytics Engine, PostHog or Umami. The app, its emails and its legal page templates ship in English and Serbian.

Nuxt Starter Kit leads on pre-launch pages: its pricing page lists a waitlist with email verification and invite management, testimonials managed from the admin, and a searchable docs section for your product. It also has a blog with RSS, Umami analytics, and English and German.

Admin and operations

Your support staff get a searchable customers list. They can edit an account, suspend it with a reason the user sees at sign-in, send reset mails, clear lockouts, and view the app as that customer for 30 minutes with every change blocked, so support sees what the customer sees without touching their data. Every action lands in the customer's activity log. Nuxt Starter Kit's admin docs list users with edit, delete, reset password, ban and impersonate, and its pricing page adds an app-wide banner.

Nuxter sets a Content-Security-Policy and other hardening headers by default, blocks browser requests from other sites that would change data through its API (a defence against cross-site request forgery), and rate limits every sign-in route. Cloudflare Turnstile, a bot check, turns on with two environment variables. Server errors can go to Sentry or Better Stack with no SDK added to the Worker bundle.

Nuxt Starter Kit uses the nuxt-security module for headers, and its home page lists rate-limited login endpoints. Its security docs say the module's rate limiter is off by default, for you to turn on in production after testing it on your host. Its authentication docs list Better Auth's rate limiting as "when configured". Its docs name no error tracker.

Tests

Nuxter ships 335 test files: 230 unit test files that run against a real Postgres engine, 97 component test files that mount components inside a Nuxt app, and 8 Playwright spec files. About 50 cover payments, including webhooks, refunds and trials. CI runs lint, typecheck, the unit and component tests and a production build on every pull request.

Nuxt Starter Kit ships Playwright tests with page objects and a CI pipeline that runs them when you push. Its testing docs describe the shipped tests as basic checks that the application is running, for you to extend. Its docs do not mention unit or component tests.

Updates

Nuxter ships pnpm template:update. A file in your app records the kit version you last took, and the command brings only what the kit changed since then, as one commit on a branch. You review it like any pull request. A written table marks which paths are yours and which are the kit's, so you know where to put code that an update will not conflict with.

Nuxt Starter Kit's update guide has seven steps built around git pull origin main --allow-unrelated-histories --no-rebase on an update branch that you test and then merge. Its FAQ says the maker keeps dependencies up to date because he relies on the kit for his own projects.

Both kits include updates in the one-time price.

Docs and AI coding agents

Nuxter ships a 330-line AGENTS.md, the instructions coding agents read before they change code: setup, the checks to run, code standards, where each kind of code goes and the traps to avoid. Claude Code, Cursor and GitHub Copilot each get a pointer file to it, so the agent you already use reads the same rules and the list of checks to run before it finishes. Nuxter's documentation is public, 25 pages with search, and is also published as llms.txt and llms-full.txt, so you can hand it to an AI assistant whole.

Nuxt Starter Kit publishes its docs as llms.txt and llms-full.txt, and ships the nuxt-llms module, which generates both files for your own app. Its site and docs do not mention instruction files for coding agents.

Price and license

Nuxter's license counts seats. Everyone who reads or changes code that contains the kit needs one, and automated tools, AI coding tools included, need none. Agencies and freelancers buy one license per client and may buy it in the client's name. The license forbids selling or publishing the kit, or using it to make another starter kit.

On 29 September 2026 Nuxt Starter Kit's pricing page showed $99, with the $149 list price struck through. Its Personal License allows commercial use and changes to the code, and forbids reselling, redistributing, sub-licensing or transferring the kit.

Support and community

Nuxter's buyers get support by email from Devilos LLC, the company that makes the kit. Its public documentation, which you can read in full before you buy, and AGENTS.md cover the rest.

Nuxt Starter Kit's support docs list a private Discord for buyers, GitHub Discussions and Issues on the repository, email, and an AI chat on the docs site. Its FAQ says the Discord gives direct support from the maker, Michael Hoffmann.