About NordsCode
A small team doing the work a platform team would do.
Five engineers, remote-first from Oslo, working with small and mid-sized companies across Europe, North America and Asia Pacific since 2019.
- Founded
- 2019, in Oslo
- Working pattern
- Remote-first, embedded with your team
- Time zones covered
- CET, with overlap for UTC-5 to UTC+8
- Engagement size
- Typically 2 engineers per client
Our mission
Make serious infrastructure engineering affordable for companies that will never have a platform team.
Good infrastructure engineering has been priced out of reach for most of the companies that need it. A platform engineer costs more than a small company can commit to before it knows what it needs, and consultancies built for enterprises arrive with a discovery phase longer than the whole project should be.
NordsCode exists to close that gap. We do the work a platform team would do, in weeks rather than quarters, for a fixed fee agreed before we start. Then we hand it over, because a company that depends on us permanently has bought a liability rather than an asset.
That last part shapes everything else. We build on standard, widely used tooling with no proprietary layer of our own. We write documentation for the engineers who will maintain the system rather than for the person signing the invoice. And we tell clients when the work they asked for is not the work they need, even when the honest answer is a smaller engagement.
How we work with SMEs
Six commitments that make a small budget go further.
Working with smaller companies is not the same job as working with large ones on a reduced budget. These are the choices that make the difference.
Fixed scope, not hourly billing
You get a written scope, a phase timeline with dates and a fixed price before work starts. If we misjudged the estimate, that is our problem to absorb rather than yours to discover at the end of the month.
We work in your repositories
Every change lands in your version control, reviewed by your engineers, from the first week. There is no separate NordsCode environment that gets handed across at the end.
Two named engineers, not a bench
The people on your introductory call are the people who do the work. We do not rotate staff mid-engagement or hand a project to whoever is available that month.
Handover is the deliverable
Runbooks, architecture notes and live working sessions are in the scope of every engagement, not an optional extra. The engagement is finished when your team can operate the result.
We say no to work you do not need
Roughly one enquiry in five ends with us recommending something smaller than what was asked for, or nothing at all. The introductory call is free precisely so that answer costs you nothing.
No reseller commissions
We take no partner revenue from any cloud provider or vendor. When we recommend a platform it is because of your workload and your budget, and we will tell you when the cheaper option is the right one.
The team
Five engineers. You will work with two of them.
Every engagement is staffed by named people who stay on it from the introductory call through to handover. Here is who they are and what each of them owns.
Mikkel Aune
Founder and Principal Engineer
Assessments, architecture, migration planning
Mikkel started NordsCode after a decade building delivery platforms inside companies that were too small to justify a dedicated platform team and too complex to survive without one. He runs the initial assessment on most engagements and writes the migration plans, which means he is usually the person on the first call and the one who tells you when the numbers do not support the work you were planning.
Sara Lindqvist
Head of Cloud Architecture
Landing zones, network design, cost modelling
Sara designs the account structures, network topologies and cost models behind every migration we run. She spent six years on infrastructure teams in regulated industries before joining, which is why our default answer to whether identity and logging can be sorted out later is almost always no. She owns the cost model that clients approve before a migration starts.
Tomás Ferreira
Lead Site Reliability Engineer
Observability, incident practice, on-call design
Tomás owns the observability and incident work. He runs the workshops where engineering and the business agree what availability actually needs to be, tunes alerting until it stops crying wolf, and facilitates the blameless reviews that turn a bad night into a fixed system. He is unusually firm about deleting alerts nobody acts on.
Amara Okonkwo
Security and Compliance Lead
Cloud posture, identity, audit readiness
Amara translates audit requirements into engineering work that developers can actually do. She has taken teams through ISO 27001 and SOC 2 readiness without stopping their roadmaps, and she writes the policies your assessor will read, checking each statement against a control that genuinely exists rather than one that sounds reassuring.
Jonas Berg
Enablement Lead
Workshops, pairing, documentation, handover
Jonas runs the handover: the workshops, the pairing weeks and the documentation your team will still be using in a year. He measures every engagement by how rarely clients need to contact us afterwards, and he is the reason our runbooks are written by the engineers who will use them rather than by us.
Start with a 45 minute call.
No charge, no deck, and no obligation to proceed. We will ask what broke recently and tell you honestly whether an engagement is worth your money.