Marketplace›Web and tech›Website development›Build your website end to end: React or Next.js front, Rust or Node back
Build your website end to end: React or Next.js front, Rust or Node back

Build your website end to end: React or Next.js front, Rust or Node back

Website development · delivered in 4-21 days

We design and build your website from scratch, choosing React or Next.js for the front end and, when a backend is needed, Rust or Node.js (TypeScript) behind it, delivered fully responsive across phone, tablet and desktop.

PackagePrice (USD)DeliveryWhat you get
Starter100.994 days1 responsive page built in Next.js, your own content, custom design, source code, 1 revision
Standard375.9910 daysUp to 5 pages with a small API behind working forms and mail, content upload, custom design, source code, 2 revisions
Advanced875.9921 daysA full web app of up to 10 pages with accounts, a database, admin screens and Docker, all in your repository, 3 revisions

This service suits small businesses, freelancers and founders who need a first site or want to replace one that no longer serves them. Next.js renders each page to HTML ahead of time, so both visitors and search engines see content immediately rather than waiting on scripts, and the same codebase can later grow to include accounts and a database.

The Starter tier delivers a single landing page or digital business card, responsive from 360 pixels up to a wide desktop screen, built with your own text and images and deployed live. The Standard tier extends this to a site of up to 5 pages with forms wired through to working mail. The Advanced tier moves closer to a true application, with up to 10 pages, user accounts, a database, admin screens, Docker and continuous integration, everything held inside your own repository. Extra pages beyond a chosen tier can be added separately.

I work as a developer rather than a designer: give me a Figma file or an example site and I will follow it, or, without any design reference, you will receive a neat standard layout that reads comfortably. If you would like a designer brought in, mention it and I will explain honestly what that involves. You supply the texts and images, since copywriting is not part of this service; where content is not ready, the build uses clear placeholders you can replace later without touching the code.

Everything is delivered into your own repository and hosting account, whether that is Vercel, Netlify or a server you manage yourself, so there is no platform lock-in and no ongoing fee payable to me. For 14 days after the project goes live, I correct anything that does not match what we agreed, at no extra cost.

There are no calls involved. Instead you get a written scope before work begins, a daily written update, and a preview link you can check throughout the build.

How the project runs

  1. Scope agreed in writing - each page is listed with what it shows and does; forms, mail, accounts and admin screens are named here or left out of the price. Once you approve the list, it becomes the agreement.
  2. Routes, layout and the responsive grid appear first on a shareable preview link, letting you confirm the structure works across phone, tablet and desktop before any content is added.
  3. Your texts and images are added, forms get connected to mail or to an API, and for tiers that include it, accounts and a database are set up behind the forms.
  4. you click through the preview link and send all corrections together; I apply them and share the same link again, keeping revisions to a single round rather than scattered messages.
  5. The finished site is published under your domain and hosting arrangement, the code is handed over into your repository, and you receive a short written guide covering how to edit content and redeploy it.

To get started, you provide the domain this order is for and a brief describing what you need.

What happens after you buy

Your order opens its own thread here the moment it is paid, and everything about that order - questions, changes and the final report - happens in it.

Questions people ask

Do you design the site, or do I need a designer?

I handle development, not visual design. Give me a Figma file or a site you like and I will match it closely. Without either, you will get a clean standard layout with solid typography, your own colours and logo. Bringing in a dedicated designer makes sense when the brand itself is central to the product.

Rust or Node for the backend: which should I pick?

For forms, mail and a small admin area, Node with TypeScript is the cheaper option to extend and easier to pass to another developer later. Rust pays off where the workload is heavy or needs to stay fast under pressure. I will recommend the right fit before you commit to an order.

Do I own it, or am I tied to you afterwards?

Ownership sits entirely with you: the code resides in your repository, the website operates on your hosting within your own accounts, and nothing passes through my billing. Another developer can take over at any point, which is precisely the reason for avoiding a builder platform.

Why not WordPress?

If the site is simply a blog, WordPress is a reasonable choice and I will say so plainly. React or Next.js becomes the better option once the site needs logins, dashboards, a genuine API, custom workflows or speed that a plugin-based stack cannot match.

People also buy