What API development services do you offer?

We offer REST API development, GraphQL APIs, third-party API integration, Laravel API development, and API security implementation. We also provide DevOps services including AWS infrastructure and CI/CD pipelines.

Where are you based and do you work with clients across the UK?

We're based in Leeds, West Yorkshire, but we work with clients across the entire United Kingdom including London, Manchester, Birmingham, and beyond. We work remotely with businesses throughout Britain.

What technologies do you specialise in?

We specialise in Laravel and PHP for backend development, along with RESTful APIs, GraphQL, Node.js, AWS, Docker, Kubernetes, and CloudFlare. We also work with MySQL and PostgreSQL databases.

Do you provide ongoing support after project completion?

Yes, we offer ongoing support and maintenance packages to ensure your APIs and applications continue running smoothly. This includes monitoring, updates, security patches, and performance optimisation.

Vercel Acquired NuxtLabs - What It Means for the JavaScript Ecosystem

Vercel acquired NuxtLabs back in July 2025, and now that the dust has settled, it is worth reflecting on what this means for the wider JavaScript ecosystem - and for teams like ours who build with these tools every day.

For those who missed it, Vercel brought in the team behind Nuxt and Nitro, including Sebastien Chopin (creator of Nuxt), Daniel Roe, Pooya Parsa, and Anthony Fu. Nuxt remains MIT-licensed with a public roadmap, and several previously paid NuxtLabs products like Nuxt UI Pro, Nuxt Studio, and NuxtHub are being open-sourced.

What actually happened

An important distinction here is that Vercel acquired NuxtLabs, the for-profit company, not the Nuxt open source project itself. NuxtLabs built commercial products around the Nuxt ecosystem and funded many of the core contributors. The Nuxt framework and its governance remain separate entities, even though they are closely linked.

Four core team members - Sebastien Chopin, Daniel Roe, Pooya Parsa, and Anthony Fu - were hired by Vercel to continue working full-time on open source. The rest of the Nuxt core team remain freelance or employed elsewhere. Daniel Roe continues to lead Nuxt's technical and strategic direction.

The case for optimism

On the surface, this looks like a genuine win. Sustaining open source at scale is incredibly difficult. NuxtLabs was constantly balancing framework development against the commercial pressures of funding its own existence. Vercel stepping in removes that burden entirely.

The immediate benefits are tangible. Core maintainers now have stable salaries and benefits instead of relying on sponsorship. Previously paid products are becoming free and open source. Sebastien Chopin can focus entirely on code instead of splitting his time between product decisions and business management. All of that should accelerate Nuxt's roadmap significantly.

The consolidation question

But this also raises questions that the community should be asking. Vercel now has significant influence over Next.js, SvelteKit, and Nuxt - three of the most widely used meta-frameworks in JavaScript. Add Turborepo, the AI SDK, and their hosting platform into the mix, and you start to see a pattern of consolidation that deserves scrutiny.

Nitro is particularly interesting in this context. It is the server runtime that powers not just Nuxt, but also SolidStart, TanStack Start, and AnalogJS. Vercel now has a hand in the server runtime layer of almost every major meta-framework except Astro, Remix, and Fresh. As one community member put it, that is a lot of the JavaScript meta-framework landscape under one roof.

The promise is that everything stays open, vendor-neutral, and community-governed. The reality is that employment creates alignment in ways that sponsorship does not. When your salary comes from a hosting company, the line between framework decisions and platform decisions can get blurry, even with the best of intentions.

What to watch for

If you are building on Nuxt today, nothing changes immediately. Your applications still deploy anywhere. The framework is still excellent. But there are specific things worth monitoring over the coming months:

Hosting parity - Does deploying Nuxt to non-Vercel targets like Netlify, Cloudflare, or AWS remain genuinely zero-config?
CLI and documentation defaults - Do sample projects and scaffolding start subtly favouring Vercel services?
Licence consistency - Do any new features ship under non-MIT terms?
Framework convergence - Do Next.js patterns start seeping into Nuxt in ways that compromise its identity?
Release cadence - Are the promised open-source releases of previously paid tools delivered on schedule?

Our perspective

For us at The API Guys, this reinforces something we have believed for a long time. We prefer React and Next.js for our frontend work, and we are comfortable with that choice. But we also recognise that healthy ecosystems need genuine competition, not consolidation under a single corporate umbrella.

Vercel's business model is straightforward - they make money by hosting web applications. Making Nuxt better means more developers building more applications, which means more hosting demand. The incentives align, and that is generally a good thing. But aligned incentives and independent governance are not the same thing.

The best thing the community can do is stay engaged. Read the governance documents. Watch the pull requests. Hold everyone accountable to the promises that were made.

Open source works best when no single company holds too many of the keys.