Most small business websites do not need a server. They need a page that loads, says the right thing, and keeps saying it at three in the morning while nobody is watching. The site you are reading is the evidence.

What we mean by static

Static means every page is built before anyone asks for it. This site is written in Nuxt with TypeScript and Tailwind, and the production build prerenders each route into a plain HTML file. One command does the work:

npm run generate

What comes out is a folder of HTML, CSS, fonts and a small amount of JavaScript for the parts that move, like the theme toggle and the mobile menu. Vercel serves that folder from its edge network. There is no database behind it, no application process waiting for requests, and nothing that has to stay alive between visits. If a page exists, it was written to disk during the build.

The monthly risk goes away

A server is a small promise you renew every month. Someone has to patch it, watch its memory, and notice when it falls over. For a web application that promise is worth making, because the server is doing real work. For a site that mostly explains who you are and how to reach you, it is overhead, and you pay for it in money and in attention.

Static files on a CDN remove most of that. There is no process to crash, so uptime becomes the host's job rather than yours. Serving a folder of files is cheap, and we bill hosting at cost, so the line on your invoice is what the provider charges us and nothing more. The risk that remains is a bad deploy, and a bad deploy of static files is undone by publishing the previous build again.

Speed and accessibility come with the format

We did not bolt a performance layer onto this site. The browser receives finished HTML on the first request, so the text is readable before any script has run. There is no loading spinner because there is nothing to wait for.

Accessibility follows the same logic. When headings, links, lists and landmarks exist in the document itself, a screen reader gets the structure without asking JavaScript for permission. We still choose contrast, focus styles and touch targets by hand, and we check the light and the dark theme separately. The static build does not do that thinking for us. It simply stops working against us.

SEO is written down, not configured

Every post is a markdown file per language in content/blog. The title, description, date, topic and author sit at the top of the file, and the page turns them into the title tag, the Open Graph tags and a block of structured data. Canonical links and language alternates come from the i18n setup, and the sitemap is generated from the same routes at build time.

Search metadata goes through code review like everything else. If a description runs long or a date is wrong, it shows up in the diff before it shows up in a search result.

Two languages are two folders

This site is Estonian first, with English under /en. In a static build that is not a runtime feature. The Estonian note lives in one folder and the English note in another, each written on its own rather than passed through a translator, and each becomes its own prerendered page with its own address. Nothing decides at request time which language you get. The file you asked for is the file you receive.

What static does not solve

Static has limits. A prebuilt page cannot accept a form submission on its own. Data that belongs to one logged-in person has nowhere to live. Nothing in the file knows how many items are left in a warehouse right now.

For contact, this site uses an email link, and for many small businesses that is enough. When a project needs a form that collects submissions, accounts, payments or live stock, we stop calling it a website and build it as a web application, with a server and a database chosen for the job. The pages that can stay static still do. The dynamic part is kept as small as the problem allows, so there is less of it to run and less of it to break.

What it costs

Our prices are written down rather than negotiated. A simple static site of up to three pages starts from 600 EUR. A multi-page site of up to five pages starts from 1200 EUR. Application work, which is where forms, accounts and live data belong, is billed at 50 EUR per hour. Hosting, domains and third-party services are billed at cost.

Static is the default we reach for because it removes the most moving parts for the least money, and for a studio site like this one that is the honest choice. When a project outgrows it, we will tell you before we send a quote, not after.