Engineer ApS Software
We build the software your team will inherit — and write it so they can.
Architecture, backends, frontends, websites, maps, design systems and more than one language — from Copenhagen.
Cases · 2025
A maritime platform with clear system boundaries
The founder’s work for NextMariner separates a Next.js interface, a Go API and PostgreSQL business rules. Each layer has a defined responsibility.
Read the case studyFrontend request
Go API
PostgreSQL JSON
Implementation overview of the request path, with outcomes and measurement context kept in the case text.
Software
Software built to be maintained, not just delivered
Backends, frontends and the architecture that holds them together, written so that the next person to open the repository can change it. The work records describe the starting situation, what was done and the result.
Start with one workflow, integration or part of an application. We can agree a small delivery with acceptance checks, documented interfaces and a handover that enables your team to maintain the software.
Software work · Pricing and engagement options · Discuss your project
Cases
Selected projects, with their scope, key decisions and our role in the work.
Infrastructure simplified beyond AWS
Reviewed an international client’s infrastructure, removed unused services, adjusted capacity and moved workloads away from AWS.
Read the case studyOne infrastructure plan for 14 departments
Designed a shared framework for a research institute that 14 departments could run on together, each keeping the things that make it different.
Read the case studyA mapping product, carried end to end
Infrastructure, data processing and the map application itself, built and kept running for two years.
Read the case study
Engineer ApS was registered in 2025. These cases include company projects and work our founder carried out in client teams and as an employee, dating back to 2003. Each case explains the role and working arrangement.
Services
Engineering services, with examples of delivered work.
Software Engineering
Deciding how the whole thing should be built
The shape of a system worked out on paper first, so the parts fit and the cost is known before anyone writes code.
The engine behind your app or website
The part users never see: where the data lives, what the rules are, and how other systems are allowed to talk to it.
The screens people actually use
Interfaces that load quickly, work on a phone and behave the same in every browser your customers happen to use.
A working product, end to end
One team taking an idea from a sketch to something your customers can log into, instead of handing it between three suppliers.
A website you can update yourself
A site that is quick, findable and editable by your own staff, without a bill for every change of wording.
Showing up when customers ask an AI
A site or an app that the AI assistants your customers use can find, read and act on, checked on every release rather than promised once.
Letting AI use the software you already have
Your existing software opened up as tools an AI agent can call, without rewriting anything that already works.
Maps that answer questions
Anything that happens in a place — vessels, vehicles, plots, sensors — put on a map you can search, measure and share.
Making it obvious how to use
Layout, wording and flow arranged so people finish what they came to do instead of ringing your support line.
Working in more than one language
Software that reads naturally in every market you sell in, including the dates, the currencies and the way names sort.
An AI assistant that knows your trade
An agent wired to the systems you use, tested on cases your own experts write, overseen by your people and never tied to one model.
Contact
Still working out what you need?
Tell us what is going wrong, or what you are trying to build. We will tell you what it would take, roughly what it would cost, and whether we are the right people for it.
From 1,400 DKK an hour, excluding VAT — and less per hour on a longer booking.