aeternum
Let's talk

01 / what we do

Websites and web applications, built in Switzerland.

For your own business or a client project. We build your website or web application and work directly with you from the first brief to handover.

what's included

Most of the cost is in the second year, so we build for it.

  • Websites
  • Web Apps
  • Headless CMS
  • Performance
  • Design Systems

What we build

Aeternum builds websites and web applications for businesses and agencies: marketing sites, web applications, and the component libraries that hold both together. Two engineers do the building, and they are the same two people you brief.

Three decisions set what a site costs in its second year. How the content is modelled, how much JavaScript reaches the browser, and whether the components are written down anywhere. We treat all three as part of the build rather than as a later clean-up.

How we decide what to build it with

The tool follows the job, and we name the choice and the reason before the work starts rather than after.

Job The approach
Content-led site Rendered ahead of time, edited through a headless CMS
Product interface A component model, rendered on the server where it must be
Styling Utility CSS driven by design tokens, never ad-hoc
Data A relational database, and a schema you can read
Payments An established provider, never hand-rolled

What we do not do is change our toolkit per project to look current. Something we know cold is worth more to you than something new to us, and the difference between the two arrives as a bill in year two rather than as a delay in year one.

What a design system buys you

A design system is the reason the fourth page costs less than the first. Tokens for colour, type and spacing live in one file; components read from it. When you change your brand green, one value changes and every page follows.

This only pays off if it exists from the start. Retrofitting tokens onto forty hand-styled components is a rewrite, and we will tell you so before you commission one.

how a build runs

How a build runs

  1. Brief and estimate

    You tell us what you need to build. Within two working days you get a scope, a range, and the parts of the brief we think will not hold.

  2. Architecture before pixels

    Content model, routing and component boundaries are settled before the first page is styled. This is the cheapest hour of the whole project.

  3. Build in visible slices

    There is a deploy preview from the first week and it stays current. You can try the work as it develops and give feedback along the way.

  4. Handover you can hand on

    Repository, deployment, environment variables and a README another team can follow. You own all of it, including the accounts.

questions

Questions about Web Development.

Do you work under our agency's brand?

Yes. We work directly with businesses and also offer white-label development for agencies. For agency projects, we agree with you on how we are introduced and how communication with your client works.

Which CMS do you use?

Whichever one the editors will actually use. We build headless, which makes the CMS a decision about the editing experience rather than about the site, and one you can revisit later without rebuilding the front end.

Can you take over a site somebody else built?

Usually. We want to read the repository and see the hosting before quoting anything, because the state of an inherited codebase is the single biggest variable in the price. A quote given without that look is a guess.

How do you keep a site fast?

By shipping less JavaScript. Static rendering by default, images processed at build time, and deciding what counts as fast enough before the build starts rather than measuring after it.

Tell us what you want to build.

Send the brief. You get a scope and a range within two working days.

other services

Other services