Service · Nuxt
Nuxt consulting and senior delivery
Nuxt 3 and Nuxt 4 architecture, SSR strategy, Nitro server work and senior delivery for production teams. This site itself runs on Nuxt 4, and the consultancy covers the full stack around it.
Nuxt looks like a thin layer over Vue until you ship a real app. Then the questions stack up. Do you render on the server, the edge or the client? Where do you put your data fetching: in composables, server routes or an external API? How do you keep the bundle slim once auto-imports have brought in half the project?
The answers are not always obvious, and the defaults are not always the right fit. SSR turns expensive when hydration costs are not measured. Auto-imports make refactors painful when names overlap. Route rules quietly change cache behaviour without anyone noticing. Most teams hit at least one of these.
We work with you to make those choices on purpose. The first step is reading the project end to end. The second is fixing the parts that hurt. The third is leaving a team that understands the system well enough to keep evolving without you.
What we do
Nuxt engagements, four ways
Pick the shape that matches what you need this quarter.
Architecture and project structure
A full read of the layout: layers, modules, composables, server routes, middleware and runtime config. You get a written report with the trade-offs called out and a ranked refactor list.
- Nuxt layers and module boundaries
- Composable patterns and data fetching strategy
- Server routes, middleware and runtime config
Rendering strategy
SSR, SSG, hybrid and edge are all valid. The question is which one for which route. We map the traffic, the cache requirements and the data dependencies, then write route rules that match.
- Per-route SSR, SSG and ISR via route rules
- Edge deployment with Nitro presets
- Hydration cost profiling and reduction
Nuxt 2 to Nuxt 3 or 4 migration
A staged plan that does not freeze the team. Module changes, route changes, Vuex to Pinia, Options to script setup, and the move to Nitro server. Feature work continues during the upgrade.
- Migration plan ranked by risk and effort
- Module replacement and breaking change audit
- Hands-on cutover with rollback checkpoints
Hands-on senior delivery
Feature work on Nuxt 3 and Nuxt 4 with the full ecosystem: i18n, sitemap, robots, schema markup, image, content and analytics. We bring the patterns that ship this site to yours.
- Nitro APIs, server middleware and tasks
- i18n, sitemap, robots, schema, performance
- Pull request review with written feedback
How an engagement looks
Short discovery, written scope, then real work. No long sales process.
- 1
Discovery call
A free 30-minute call. You walk us through the codebase, the team and the deadlines. We ask the awkward questions early so the scope is honest.
- 2
Written scope and proposal
Within two business days you get a written scope with deliverables, timeline and a fixed price or weekly rate. Nothing locked in until you sign off.
- 3
Architecture review or sprint kickoff
Audits run for one week of deep reading and a written report. Delivery work starts inside your sprint cadence from day one.
- 4
Weekly delivery and code review
A weekly check-in, async PR reviews and a Slack channel for the day-to-day. You always know what's shipping next.
FAQ
Common questions
Do you work on Nuxt 2 codebases?
Yes. If a migration to Nuxt 3 or Nuxt 4 makes sense we plan it. If not, we modernise in place: TypeScript, composables, better testing, faster builds. The right call depends on the team and the runway.
Nitro server routes or external API?
Depends on the shape of the data and the team that owns it. For BFF work and tight UI coupling, Nitro routes win because they ship with the app. For shared data services, an external API stays simpler in the long run.
Static, SSR or hybrid?
Most production sites end up hybrid: SSR for SEO pages, SSG for marketing, client-side for the behind-login app. Nuxt route rules make the per-route choice clean. We map the routes during the audit.
Can you help with i18n, sitemap, robots and schema?
Yes. This site is the proof. Three locales with hreflang, a sitemap index, robots with AI bot rules and full JSON-LD across every page. The same setup transfers to your Nuxt project.
How does the engagement work?
Fixed-scope for audits, weekly retainer for delivery, hourly for ad-hoc emergencies. Pricing bands live on the pricing page so there are no surprises before the first call.
What about Nuxt Content?
Covered. Markdown content, MDC components, ORM-style queries and SSG output. We have shipped it for blogs, documentation sites and marketing pages. See Vue: The Road To Enterprise for related patterns.
Last updated: 2026-05-20
Next step
Nuxt codebase that needs senior eyes?
Tell us about the team, the stack and the timeline. We reply within two business days.