Cloud, Hosting & DevOps

Servers, deployments, monitoring and backups, run the way we run our own products.

All our products, from bkg.dk and danadresse.dk to uahub.dk and soge.dk, run on servers we operate ourselves: about a dozen Linux machines with aaPanel, nginx, MySQL, PostgreSQL, Redis and Docker. We patch them, renew their certificates, back them up every night and receive the alerts when something breaks. The services on this page are that same work, done for your systems.

We prefer open-source tools and ordinary European VPS providers to expensive managed platforms, because a small business should be able to read and understand its server bill. If all you need is a cheap webhotel for a simple site, that is a different product: our own hosting product kex.dk is on its way for exactly that.

Infrastructure work we do

Managed hosting for web apps

We host and operate the web apps we build or take over: system and runtime updates, TLS certificates, nightly off-site backups, monitoring and incident handling. It is meant for systems a business depends on, not for a five-page brochure site. Project support starts at 600 DKK a month; the full page lists what it covers.

Learn more →

Cloud architecture on a small-business budget

For a small business, architecture is mostly about deciding what not to run. A typical setup from our own fleet: one VPS with nginx in front, the application as a systemd service or a Docker Compose stack listening only on localhost, the database on the same machine, and a search engine or Redis only where the product needs one. We give each service a memory limit so one process cannot starve the rest, and we size those limits from real behaviour: on one server a search index kept rereading its own data from disk until its limit matched the size of the index. As load grows, we split services across machines before reaching for an expensive managed cloud.

Server and cloud migration

Moving a site or an app to another server is routine; doing it without losing mail, certificates or search rankings takes a checklist. We copy, test the new server before DNS points to it, switch DNS and then retire the old copy. That last step matters: after one site move we found the old server still answering for the domain and serving backup copies of the WordPress configuration file. Migration also covers external services that close down. When the public Danish address service DAWA shut, we built danadresse.dk with the same address IDs, so users could switch to it without rewriting their stored keys.

CI/CD pipelines

Every push should run the tests, and a deploy should be one command that can be undone. For bkg.dk, GitHub Actions runs more than 1,000 tests; the deploy script then checks health, key pages and self-checks on the new release and rolls back on its own if they fail. In a rehearsal where we killed the connection halfway through a deploy, the server returned to the previous release by itself in 285 seconds. danadresse.dk deploys from a signed webhook in about a minute. When GitHub's hosted runners are unavailable, we run tests and builds on a self-hosted runner, while deploys go through a script that always starts with a dry run.

Monitoring and alerting people do not mute

Monitoring that wakes you for every blip gets muted within a week. Our fleet dashboard watches disks, load, memory, services and backups on every server, and an alert gate in front of it sends a recovery notice only after an alert was actually sent, holds low-priority night alerts until the morning and marks anything that fires three times a day as unstable. Each product also has a daily routine that runs its tests and user journeys. The rule we design around: a page that quietly degrades is more dangerous than one that returns an error, so we probe the paths that can fail silently, not only the home page.

Backup and recovery that has been tested

A backup you have never restored is a hope, not a backup. Our servers back up sites and databases every night and copy them off-site to Google Drive, including the system layer: configuration, crontabs and mail. A daily audit reports any server with a missing or stale copy, and we rehearse restores; the latest drill for our phone platform came back 16 of 16 checks identical. Testing pays off: for one client we found that the WordPress database dumps contained placeholder strings where every percent sign should be, so a restore would quietly have damaged page styles and product descriptions.

Docker and containers

We use Docker where it earns its place: apps with several services that must run in known versions. bkg.dk runs as a Docker Compose stack behind an nginx edge container; a new release starts next to the old one, traffic moves only when the new container passes its checks, and the three most recent images stay on the host for a one-command rollback. Python dependencies are locked with hashes, so the production image matches the image that was tested. Docker engine updates across our servers are scripted with a rollback package, and we compare listening ports and site responses before and after each update.

Performance optimisation

Speed work starts by measuring the real page on the real server, not a lab score. On lynbro.dk we found the same fonts downloaded seven times under different URLs and a cookie banner acting as the largest element on mobile; after fixing both, LCP on production fell from 1,196 to 624 ms. Loading the anti-spam widget only when a visitor nears the form cut the start of the home page from 1,211 to 515 KB. On oksana.dk and uahub.dk, page caching for anonymous visitors, OPcache and a Redis object cache brought server response from about 0.9 seconds to between 0.12 and 0.21 seconds. Every change comes with before and after numbers.

Infrastructure we run every day

Our own server fleet

About a dozen Linux servers with aaPanel host our products and client sites. Backups go off-site every night, around 105 Let's Encrypt certificates renew through acme.sh, and updates of PHP, database engines and Docker run as scripts with a backup and a rollback. In November 2026 we found and fixed two certificate renewals that had been failing in a loop.

bkg.dk releases

Our booking platform runs in Docker Compose with blue/green releases behind an edge nginx. Since November 2026 a code release hands over to the new container in about a second, and configuration changes are reloaded the same way instead of restarting the stack. The deploy script verifies health and rolls back by itself when checks fail.

The incident of 25 October 2026

A deploy from a new CI runner on macOS used a different rsync implementation and mirrored a website build into the root of a production server, deleting system files. We restored the server the same day from off-site copies: sites, MySQL and PostgreSQL. Since then a guard dry-runs every sync that can delete files and refuses root and system paths.

lynbro.dk

This website is a static, prerendered build in three languages with a strict Content Security Policy and long cache lifetimes for versioned assets. Fixing duplicate font downloads, the cookie banner and an eagerly loaded anti-spam widget brought production LCP from 1,196 to 624 ms.

Tools behind our infrastructure

Linux servers managed with aaPanel and nginx; MySQL, MariaDB and PostgreSQL; Redis; Docker Compose; systemd units with memory limits; acme.sh for Let's Encrypt certificates; GitHub Actions for tests and builds; fail2ban against password guessing; Google Drive as the off-site backup target. All free or open source, so there are no licence fees to pass on to you.

Prices for hosting and DevOps

Cloud services setup
from 1,000 DKK
Technical audit of servers and deploys
from 3,000 DKK
Project support (ongoing operation)
from 600 DKK/month
Hourly rate
500 DKK/hour
Urgent support
1,000 DKK/hour

The price depends on how many servers and apps are involved, how they are deployed today and how much has to change. After a free scoping talk you get a fixed quote; send your request through the contact form.

How we take on your infrastructure

1

Read-only inventory

We log in without changing anything and list every site, service, cron job, certificate, database and backup task, and check which backups actually restore. You get a one-page map of the setup and its risks.

2

Close the dangerous gaps first

Missing off-site copies, certificates close to expiry, open ports and secrets lying in web folders come before anything cosmetic. Each change gets a backup and a written rollback before it runs.

3

Script the deploys and the checks

Deploys become a script with a dry run, health checks and a rollback, kept in the repository. Alert thresholds are tuned to your normal load, so an alert means something when it arrives.

4

Hand over or keep operating

You receive runbooks and full access. If you want us to keep running it, project support covers updates, renewals, backups and alerts; urgent work outside that is billed by the hour.

Frequently Asked Questions

Do we need AWS, Azure or Google Cloud?

Usually not. A typical small-business app runs well on one or two European VPS servers at a fraction of the cost, and that is what we use for our own products. If a customer contract or a regulation requires a specific provider, we discuss in the scoping talk whether we are the right fit.

Can you take over servers another developer set up?

Yes. We start with a read-only inventory and make backups we have restored ourselves before changing anything. Forgotten cron jobs, old control panels, expiring certificates and configuration files left in web folders are typical findings, and we fix them in order of risk.

What happens if a server is lost completely?

We restore it from off-site copies onto a new machine. That is not theory for us: in October 2026 we rebuilt a production server the same day after a faulty deploy deleted its system files. Afterwards we also checked the restored backup jobs, because a restored snapshot had brought back older scripts that no longer uploaded copies.

Will deploys cause downtime?

For a simple site a deploy is a file sync that takes seconds. For apps with users online we can set up blue/green releases, where the new version starts next to the old one and takes over only after its checks pass. How far to go depends on what a minute of downtime costs you.

Which tools do we get locked into?

None that cost licence fees. aaPanel, nginx, Docker, PostgreSQL, MySQL, Redis and acme.sh are free or open source, and you keep root access and the runbooks. Another developer can take over from us without rebuilding anything. The only recurring costs are the servers themselves and, if you choose it, our project support.

⚡

Get an Instant Price Estimate

Use our interactive calculator to get an approximate price for your project in 2 minutes.

⚡ Calculate Price

Ready to Cross the Bridge?

Let's build your lightning bridge to digital transformation. From first consultation to live deployment — we move fast.

Get Started Today