Website builds — Amsterdam

Your work is real.Your website should be.

We design it, build it front to back, and write it from what you already have — the paper, the deck, the README, the demo. Live in weeks, yours to edit after.

Start your siteSee how it works

Stack

Next.jsReactTypeScriptTailwindNode.jsPostgreSQLDockerVercel

You get

Positioning and copyA design system, not a themeFront end and back endA live domain and hostingThe source, and accessPositioning and copyA design system, not a themeFront end and back endA live domain and hostingThe source, and access

About nileBlu

Nobody funds, cites, buys or joins what they cannot see. We build the website you keep meaning to build.

You have the work. Getting a site up means writing the copy, designing it, building both halves and shipping it — four jobs, none of them the one you're actually paid to do. We do all four from the material you already have, and hand back something you can keep editing.

How the studio works

Services

Four jobs stand between your work and a website. We do all four.

You do not have to brief four suppliers, and you do not have to arrive with finished copy. Send the deck, the repo, the paper, the demo — we work out what the site should say, design it, build both halves, and put it live on your domain.

Start your site

We read what you already have — the deck, the README, the paper, the demo — then write the site: what the work is, who it is for, and why it holds up. You review sentences instead of staring at a blank page.

Start your site

“A website is not marketing. It is the only thing a stranger can check after they hear your name.”

Capabilities

Four things a website has to do that a template cannot: stay consistent as it grows, talk to a database, ship without ceremony, and run on a domain that belongs to you.

Design Systems

One token layer behind every screen. Change a colour or a type step in one place and the whole site follows it.

APIs & Data

Typed endpoints, a real database, and forms that deliver — so the site does work rather than only describing it.

Ship on Push

Types, tests and a build run on every commit. Merge, and the change is live in minutes with nobody logging into a server.

Hosting & Domains

Your domain, your certificates, your analytics, on infrastructure sized for your actual traffic — not a plan you were upsold.

Production-Grade Standards

The page you are reading is the audit. These are its own numbers, taken in your browser.

Semantic landmarks

Regions a screen reader can jump between, rather than a page of divs.

—Measuring

Images described

Every image carries alt text, even when that text is deliberately empty.

—Measuring

Third-party scripts

Code loaded from someone else's origin. None here: no trackers, no tag manager.

—Measuring

Transferred weight

Everything this page pulled over the network to render.

—Measuring

Transport

Whether this page arrived over an encrypted connection.

—Measuring

Read from the DOM and the performance timeline on this page. Nothing is sent anywhere, and nothing here is a promise — a claim we cannot measure from your browser is not listed.

Research & Labs

A project site is a deliverable. We build it like one.

Funded research usually owes the outside world a public site — a place the consortium, the instrument, the dataset or the group can be found and cited. It arrives with a fixed budget line, a start date and an end date, and it is nobody's actual job.

We build them properly: publication lists that stay current, author and affiliation pages, LaTeX and BibTeX rendering that survives a copy-paste, dataset and code links that resolve, and a site that still loads in five years when the grant has closed and nobody is maintaining it.

Talk about a project site

Publications & Preprints

BibTeX in, formatted list out. DOIs resolve, preprints link, and the page updates without anyone editing HTML.

Groups & People

Members, alumni, affiliations and roles from one source. Someone joins, one entry changes, every page follows.

Instruments & Datasets

Documentation, access conditions and citation instructions for the thing you built, in a form other researchers can act on.

Built to Outlive the Grant

Static where it can be, no service that can quietly stop existing, and a handover you can pass to whoever inherits it.

Scope

What we don't do.

Saying this early saves everyone a call.

Ongoing ad campaigns

We'll build the pages a campaign points at. We don't run the spend, and we don't bill a percentage of it.

Mobile apps

Web, front to back. If you need native, you need a different studio, and we'd rather say so now.

Rescuing a site whose architecture is the problem

We'll happily take over pages, copy and design. When the trouble is underneath — the data model, the build, the way it's assembled — patching it costs more than replacing it, and we'll tell you that instead of taking the work.

Act II — The machine

Open it up.

Everything past this point is something you can check yourself, on this page, right now.

What You Approve Ships

What you sign off and what goes live are the same file.

You should not have to take it on trust that the built site matches the design you approved. Point at either side below: the interface and the code that renders it are bound to the same parts, and every value resolves from one token layer. When you want the headline changed six months from now, this is the file that changes.

Interface ↔ SourceHover, tap or tab either side

Design and engineering studio

A studio site that scores itself while you read it.

26 pages, every one prerendered

Read the write-up

1<article
2className="rounded-card border border-line bg-surface p-8"
3>
4<p className="font-mono text-role text-faint">
5{project.sector}
6</p>
7<h3 className="mt-4 text-title text-ink">
8{project.title}
9</h3>
10<CountUp
11value={project.metric}
12className="text-display text-accent"
13/>
14<Button href={routes.project(slug)}>
15{project.cta}
16</Button>
17</article>

Every colour, size and radius above resolves from the same token layer this page is built on.See the four stages

Push to Live

One command, from commit to live.

Shipping should be the least dramatic thing that happens all week. This is the pipeline your site gets on day one — typed, tested, built and checked before a single visitor reaches the new version. It runs from a push, and after handover it runs for you.

install
verify
build
ship
live

~/your-siteRunning

git push origin main

commit 8f3c1de · main · signed

Dependencies restoredcache hit · 0.9s

Type-checking 412 files

No type errors2.1s

Lint clean0.7s

34 tests passed1.9s

Contrast and landmarks checked0.6s

Building production bundle

Compiled · 29 routes prerendered11.4s

Images optimised · 14 assets1.1 MB total

Uploading to the edge

Preview measured · vitals greenLCP 0.9s

Domain aliased · certificate renewedno downtime

Cache purged · sitemap resubmitted12 URLs

Live in production24.8s total

Measured, Not Claimed

This page is being scored while you read it.

Everyone who sells websites says theirs are fast. These four numbers are your browser's own, taken from the page you are reading right now — not a screenshot of a report someone ran on a good day.

Live on your device

LCP

Measuring

Largest Contentful Paint

How long until the main content of the page had drawn.

CLS

Measuring

Cumulative Layout Shift

How far the page moved under you while it loaded.

INP

Awaiting interaction

Interaction to Next Paint

The slowest response yet to something you did. Try the panel above.

TTFB

Measuring

Time to First Byte

How long the server took to start answering.

Readings come from the browser's PerformanceObserver, computed on this page — no analytics service, no third-party script, nothing sent anywhere.

Act III — The proof

How it goes.

What happens to you between sending us what you have and holding the keys.

Working with usWorking with usWorking with usWorking with usWorking with usWorking with us

Working with us

How this actually goes.

Four steps, and you can see the site at every one of them. Nothing is revealed at the end.

Start your site

You send what you have.

Deck, repo, paper, demo, a link, a voice note. Nothing polished.

We come back with the words.

Before any design, you see what the site will say. Change it there, where changes are cheap.

You watch it get built.

A live preview URL from the first day, updated on every push. No reveal.

You get the keys.

Repository, domain, hosting, analytics, in your accounts. Edit it on a Sunday evening without calling us.

Insights

What to build, what to say, and what to skip when you're putting a site up.

Hover a title to previewAll insights

FAQFAQFAQFAQFAQFAQ

Send the deck, the paper, the repo, the demo.

We'll send back a website.

Your work is real.Your work is real.Your website should be.Your website should be.

Nobody funds, cites, buys or joins what they cannot see. We build the website you keep meaning to build.

Four jobs stand between your work and a website. We do all four.

Four things a website has to do that a template cannot: stay consistent as it grows, talk to a database, ship without ceremony, and run on a domain that belongs to you.

Design Systems

APIs & Data

Ship on Push

Hosting & Domains

A project site is a deliverable. We build it like one.

Publications & Preprints

Groups & People

Instruments & Datasets

Built to Outlive the Grant

What we don't do.

Ongoing ad campaigns

Mobile apps

Rescuing a site whose architecture is the problem

Open it up.Open it up.

What you sign off and what goes live are the same file.

A studio site that scores itself while you read it.

One command, from commit to live.

This page is being scored while you read it.

How it goes.How it goes.

How this actually goes.

You send what you have.

We come back with the words.

You watch it get built.

You get the keys.

What to build, what to say, and what to skip when you're putting a site up.

Your work is real.Your website should be.

Open it up.

How it goes.