Nuxt Studio SaaS Sunset to Open Source on January 5, — when and how should I migrate?
Choose whether to migrate documentation editing to the new self-hosted Nuxt Studio module now that the hosted "nuxt.studio" service has been sunset.
Blockers
- package/nuxt-studio-saas — EOL 2026-01-05
- Nuxt Studio only supports Nuxt Content websites.
- The new module requires a server-side auth route.
- If you use Google OAuth or custom auth, Studio requires a GitHub personal access token for write operations.
- If you use Google OAuth or custom auth, Studio requires a GitLab personal access token for write operations.
- Upcoming Nuxt Content versions will remove legacy Studio code.
Who this is for
- cost-sensitive
- small-team
- low-ops
Candidates
Migrate now to the self-hosted Nuxt Studio module
Nuxt's current Studio path is the self-hosted, open source module for production editing on Nuxt Content sites.
When to choose
Use this when you still want non-developers to edit docs in production, your site is a Nuxt Content site, and you can run it on SSR-capable hosting with the required auth and repository write-token setup.
Tradeoffs
You keep a visual editor, media management, real-time preview, and direct Git publishing without paying a Nuxt Studio SaaS fee. The tradeoff is that you now own deployment, OAuth setup, token handling, and runtime security on your own infrastructure.
Cautions
Nuxt Studio only supports Nuxt Content websites. The new module requires a server-side auth route, so a fully static hosting target without SSR support is not enough even if you prerender pages. If you use Google OAuth or custom auth, Studio also requires a GitHub or GitLab personal access token for write operations. Upcoming Nuxt Content versions will remove legacy Studio code, and Nuxt recommends removing the "preview" key now.
Skip Studio and keep a plain Git-based docs workflow
Keep editing content directly in your repository with your existing editor, pull request, and CI/CD workflow instead of adopting the new Studio module.
When to choose
Use this when your team is already comfortable editing Markdown, YAML, or JSON directly and you do not need non-technical editors to publish from the live site. It is the decisive choice if you want to avoid adding SSR auth routes, OAuth clients, and repository write tokens just to replace a service that has already been shut down.
Tradeoffs
This is the simplest and lowest-risk operational path because your current repository, review, and deployment flow stays intact. The downside is no visual editor, no media library, no real-time preview inside production, and no direct publishing UI for content editors.
Cautions
This is a fallback, not a continuation of the old SaaS, because as of 2026-03-20 the hosted "nuxt.studio" platform has already been sunset and subscriptions were canceled. If your main blocker is static hosting, note that the new Studio module still needs SSR support for auth, so staying Git-only may remain the cleaner option until your hosting model changes.
Try with your AI agent
$ npm install -g pocketlantern $ pocketlantern init # Restart Claude Code, Cursor, or your MCP client, then ask: # "Nuxt Studio SaaS Sunset to Open Source on January 5, — when and how should I migrate?"