03 / HOSTING

A good website.
A solid foundation.

Hosting is about more than a place to keep files. Delivery, encryption, updates and the ability to recover from a failure must fit what the website actually does.

Our hosting runs on our own network, with our own IP addresses and AS52122.

DeliveryCacheOperations

Shaped by possibilities

Choose an example

Example 01 / 03

A shorter path from content to visitor.

A CDN can cache public content close to the user. Edge functions can run selected logic in the same network, while an origin server handles the rest.

Practical example

For an image-heavy portfolio, finished images and style files can be served from a cache instead of being fetched from the origin on every visit. Personal pages and signed-in content need their own rules and must not be mixed into a public cache.

How it can be used

An event suddenly gets many visits after a mention. The programme and images can be cached, while registration capacity must be checked against the actual data source. A CDN does not replace capacity and correct logic in the booking.

What we aim for

A delivery model that can reduce the work on the origin and the distance to the visitor.

CDNCache-ControlEdge functions

Example 02 / 03

Publish without crossing your fingers.

HTTPS with a valid certificate is a minimum. We set up automatic renewal, secure headers and a publishing routine where changes can be rolled out and rolled back.

Practical example

A small team updates the website several times a week. Every change is tested first in a separate environment, and the previous version is ready if something unexpected happens.

How it can be used

A campaign goes out at 08:00. The page is finished the day before, tested and staged, and publishing is one controlled step.

What we aim for

Fewer surprises when publishing, and a way back that has been rehearsed beforehand.

HTTPSCertificatesRollback

Example 03 / 03

The size of the setup follows the task.

A website with fixed pages needs something different from a service with sign-in and a database. We choose between static files, an application server and combinations, and size it by actual use.

Practical example

A clinic with information pages and a simple booking can have a light public part and a small application behind it. That means low cost and little to maintain.

How it can be used

An organisation expecting more traffic during a campaign can scale up for the period and back down afterwards.

What we aim for

A setup that is big enough for the task, without paying for capacity that is never used.

ScalingMonitoringBackup

Experience the technology

What does a cache do?

Explore a simple worked example.

CacheOrigin

200 fetched from the origin

600 served from cache

Number of requests 800 Share served from cache 75%

Move the values and see how the traffic is split. A cache can reduce the number of requests that have to go all the way to the origin.

A simplified worked example. The numbers are your choices, not measurements of 10GB's traffic or performance.

What does this mean for your project?

CDN, edge and HTTP/3 are chosen as needed, configured for the solution and verified at delivery.

Source: Cloudflare: Static assets

Have a task
we should look at?

Let's find a good solution

Let's talk

Tell us what you want to build.

The form is the quickest way. You get a reply from a person, and we start with a short conversation about the goal, not with a price list.

hi@••••.no

Phone

+47 •• •• •• ••

Shown only after a tap and a short security check, so the address does not end up on spam lists.

A good website.A solid foundation.

Choose an example

A shorter path from content to visitor.

Publish without crossing your fingers.

The size of the setup follows the task.

What does a cache do?

What does this mean for your project?

Have a taskwe should look at?

Tell us what you want to build.

A good website.
A solid foundation.

Have a task
we should look at?