Design · Web design

Websites built as the experience, not a picture of one.

Static, fast, art-directed per device. The page you approve is the page that ships — no builder bloat between the design and the visitor.

Start a project

Website free with hosting — €180/year

What it is

We build sites as static output: HTML, CSS and a small amount of JavaScript, generated by a build step and served as files. There is no framework runtime to download before the first paragraph appears, and no page builder writing markup on your behalf.

Layouts are art-directed for desktop, tablet and phone separately. A phone is not a narrow desktop, so the crop, the type scale and the amount of motion change with the device instead of being squeezed into one universal grid.

How it works

  1. 01

    Scope and structure

    What the site must do, who it is for, and which pages actually earn their place.

  2. 02

    Design in the browser

    Type, rhythm and motion are judged where they will live, not in a static mockup.

  3. 03

    Build static

    A build pipeline produces responsive AVIF/WebP images, minified CSS and versioned output.

  4. 04

    Measure, then ship

    Lighthouse on mobile, on throttled network, before launch — not after a complaint.

What you get

  • Three art directions — Desktop, tablet and phone are each composed, not scaled.
  • Static output — No SPA runtime, no builder plugins, no database to break.
  • Responsive imagery — AVIF with WebP fallback and correct sizes, generated at build time.
  • Accessible by default — Keyboard paths, focus states and contrast are part of the build, not a retrofit.
  • Readable without JavaScript — If a script fails, the content is still there.
  • Versioned — Every deploy is a known state you can roll back to.

Who it is for

  • Studios and operators whose current site is slow, generic, or impossible to edit safely.
  • Businesses moving off a page builder they have outgrown.
  • Anyone who needs the site to load on a phone, on mobile data, in a hurry.

Questions

Can we edit the site ourselves afterwards?
Yes — through the CMS client panel. You edit, preview and publish; the public site stays static and fast.
Why static instead of WordPress?
Static output has no plugin surface to keep patched and nothing to execute per request, so it is faster and far less likely to break on its own.
Do you redesign existing sites?
Yes. A redesign usually starts by deciding which pages deserve to survive.
What does hosting involve?
We host the built files and handle certificates and deploys. It is a small monthly cost, and you can take the build elsewhere.