Nuxter vs NuxtBeyond

Stack and hosting

Nuxter is built for Cloudflare Workers on purpose. Queues, file storage, cache, mail, rate limiting, AI and the database connection are Cloudflare bindings, resources the Worker is connected to by name, all declared in one file with the code behind each already written. You learn one platform and run one Cloudflare account for everything except the database, which is Postgres at a provider you choose. The trade is that the app runs nowhere else. After a one-time setup that the deployment docs walk through, the shipped GitHub workflow deploys main each time CI passes, and pnpm deploy:cf runs the same steps from your machine.

NuxtBeyond runs on Workers too, through NuxtHub. Its home page says D1, R2, KV and the Workers runtime come pre-configured and that one command deploys them. Both kits are Nuxt 4 apps with Vue 3, Nuxt UI 4, Tailwind CSS and Drizzle ORM.

Sign-in and accounts

In Nuxter you choose password or magic-link sign-in in one config block, then switch on passkeys, authenticator-app codes with ten recovery codes, and GitHub or Google. Every session is a database row checked on each request, so users see their devices and sign one out, and a suspension signs the account out everywhere at once. Users delete their own account with a 30-day restore window, download their data as a file and read their own activity log, so a deletion or export request needs no support ticket.

NuxtBeyond ships email and password and Google OAuth, with email verification and password reset, on nuxt-auth-utils. Its maker writes that the kit has no 2FA, no passkeys and no magic links, and its site does not mention account deletion or an activity log as kit features.

Organizations and permissions

Nuxter's tenant is an organization, addressed by an id in the URL. The server reads the caller's role from the database on every request, so removing a member takes effect on their next request. Owner, admin and member roles are built from four permissions, and you add roles and permissions in config, where the type checker catches a misspelled name. Each plan caps how many members an organization may hold, so bigger teams move to bigger plans, and an organization can hold branches or sites that share its plan and seats.

Each organization also keeps an audit trail of thirteen event types. When a customer asks who removed a colleague or changed a role, the trail answers it.

NuxtBeyond's tenant is a project that owns members, billing, chats and files, with invitations by email and two fixed project roles, admin and member. Its home page calls this role-based access control, and its maker's March 2026 roundup lists "no RBAC" among its shortfalls. In his multi-tenant guide, a user can belong to several projects with a different role in each, and each API route checks membership. Its site does not mention member caps, an audit log or a level below a project.

Payments and billing

Nuxter's payments work with Stripe, Polar, Lemon Squeezy and Creem, chosen in a config array. Polar, Lemon Squeezy and Creem are merchants of record: the legal seller, which collects and remits sales tax for you. When a renewal fails, the customer keeps access for 14 days by default while the provider retries, and everyone who can bill the organization sees a banner with a button to fix the card, so a customer whose card expires keeps working while they update it.

Like Nuxter, NuxtBeyond puts its providers behind one interface, attaches the subscription to the tenant and hands card and plan changes to a customer portal. It switches between Stripe and Polar with one environment variable, and in the maker's Stripe guide the webhook stores the status Stripe reports, past_due included.

Database, jobs and files

Nuxter keeps app data in Postgres through Drizzle. In production the Worker reaches it through Hyperdrive, Cloudflare's connection pooler for a database hosted elsewhere, so you pick the provider: any Postgres that Hyperdrive can reach works, such as Neon, Supabase or PlanetScale. On your machine, pnpm dev runs PGlite, Postgres compiled to WebAssembly, with the same migrations. Writes that two requests could race, such as taking an organization's last seat or removing an account's last way to sign in, run in transactions that retry on conflict. The kit's 24 tables, its migrations and its 230 unit test files already run on Postgres.

NuxtBeyond keeps its data in D1, Cloudflare's SQLite database, as a binding in the same account as the Worker. Its maker describes the trade: typed queries through Drizzle and no connection pool to manage, with SQLite in place of Postgres, so you design around D1's limits. He also writes that D1 is fine for a lot of SaaS and not fine if you know you need Postgres on day one.

Nuxter runs typed background jobs on Cloudflare Queues, retried with growing delays, so a mail that fails during a provider outage, or a subscription that must be cancelled after an account is deleted, is retried for about half an hour instead of dropped on the first failure. A daily cron runs six cleanup tasks. NuxtBeyond's site lists no background jobs or scheduled tasks among its features.

Both store files in R2. NuxtBeyond ships document uploads per project, with storage limits by plan. Nuxter checks each upload's real file type and size against rules you set per purpose, generates the route that serves it, and builds avatar and organization photo uploads on it.

Email and notifications

Nuxter sends its mail through Cloudflare Email Sending or Resend. A failed send falls through to the next provider, and when every provider is down the mail waits in the job queue for a retry, so a password reset still arrives after a short outage. Templates are Vue files compiled at build time by Maizzle, an email framework that inlines styles for mail clients, and product or marketing mail carries a one-click unsubscribe.

A notification bell in the dashboard shows in-app messages, and payment notifications are already wired to it.

NuxtBeyond sends verification, password reset, invitation and support mail through Resend. Its site does not mention a template tool, retries for mail or in-app notifications.

AI

Nuxter ships the server calls an AI feature is built on: typed functions for text, image, speech, transcription, embeddings and video on Workers AI, Cloudflare's hosted models, reached through a binding with no API key. You name models by role in config, swap one per deploy with an environment variable, and add another provider as one file.

NuxtBeyond leads here. Its chat runs on OpenAI GPT through Cloudflare AI Gateway, and its answers from a project's documents run on Cloudflare AI Search, which keeps each project's results apart with a folder filter.

Its home page also lists image and video generation with DALL-E 3 and Sora. The maker wrote on 2026-09-26 that this path uses OpenAI APIs that OpenAI has retired and is broken until he migrates it.

Content, languages and marketing pages

Nuxter ships every screen, email and legal page in English and Serbian, and a test holds every language file to the same keys, so a string you add in English and forget to translate fails the suite. The languages docs list each file a new language needs.

Nuxter's blog, on Nuxt Content, has tag pages, drafts, RSS feeds and generated share images. A GitHub workflow drafts a post with an AI model, translates it and opens a pull request for you to review.

NuxtBeyond ships a Nuxt Content blog with Markdown and SEO, a light and dark theme, and a landing page you configure in one YAML file, content/index.yml. Its maker says the kit has no i18n.

Admin and operations

Nuxter's staff area starts from a searchable customers list. Staff edit or suspend an account, send a password reset, clear a lockout, grant a plan and refund a one-time purchase. Impersonation shows the app as the customer for 30 minutes and refuses every change, so staff see what the customer sees without touching their data.

NuxtBeyond's maker wrote on 2026-09-26 that the kit has no dedicated admin panel; his April 2026 comparison rated its admin dashboard "Basic". Both kits ship rate limiting and Cloudflare Turnstile, a bot check.

Nuxter ships a GitHub Actions workflow that checks the config, builds, applies database migrations and only then uploads the Worker, so a failed migration leaves the old version live. Error forwarding to Sentry or Better Stack takes one config flag and a DSN.

NuxtBeyond's deploy guide has you generate migrations with npm run db:generate and apply them to the remote D1 database. Local development runs on a separate SQLite file, so the guide tells you to check that each migration reached production.

Tests

Nuxter ships 335 test files: 230 unit, 97 component and 8 Playwright specs. As the testing docs describe, the unit tests run against PGlite with the real migrations applied, and CI runs lint, typecheck, the unit and component suites and a build on every pull request. When you change a kit file or take an update, the suite runs against your change.

In April 2026 the maker's comparison with Supastarter listed NuxtBeyond's testing as "No", and the commands its site lists include typecheck and lint and no test command. The repository is private, so tests added since would not show from outside.

Updates

Nuxter keeps the kit as a git remote named template. pnpm template:update lands everything the kit changed since your last update as one commit on a branch you review. A written table says which paths belong to the kit and which to you, and your migrations run in their own chain, so a kit update never renumbers them.

NuxtBeyond's FAQ says updates are pushed to the GitHub repository you get access to, and its terms say they come through "the download portal or repository access", with no guaranteed schedule. Its site does not describe how to bring later changes into a project you have already started.

Both include updates in the one-time price. Nuxter adds the command and the ownership map for taking one into an app you have already changed.

Docs and AI coding agents

Nuxter's documentation is public: 25 pages with search, so you can check how a part works before you pay. The repository ships AGENTS.md, which lists known traps with their causes and where each kind of code goes, with pointer files so Claude Code, Cursor and Copilot read it.

NuxtBeyond's terms list setup guides and a CLAUDE.md as part of the purchase, and its site has no public documentation pages (checked 2026-09-29). Its CLAUDE.md covers project structure, database schema and API endpoints, and the maker says it works with Claude Code, Cursor, Windsurf and GitHub Copilot.

Price and license

On 2026-09-29 NuxtBeyond's home page advertised a $59 launch price beside the struck-through $249, and $89 for the bundle beside $399, and said the price rises by $10 every 5 sales. The bundle adds the maker's Distribution Framework, Claude Code agents and skills for marketing work such as lead sourcing and outreach.

Nuxter's license, summarized on the pricing page, covers any number of your own products. A seat is one person who can read or change code that contains the kit, and AI coding tools need no seat.

Support and community

Nuxter's support is by email to Devilos LLC, the company that makes it; the public docs and the AGENTS.md described above cover the rest.

NuxtBeyond's pricing card lists support from the founder, and the home page invites questions by direct message on X. Its terms name a Discord community and a support email address.