Development
Architecture and development of AI solutions, agents and assistants connected to core systems and integrations. From prototype to production โ secure, observable and maintainable.
Hi, I'm
An architect at REMA 1000, where since January I have been making artificial intelligence something people actually use โ and the business can measure. Before that: fifteen years of integrations, retail systems and a stint at sea. In the evenings I build small tools, mostly to understand how things work.
Right now: AI adoption at REMA 1000 It is in Norway
01Now
My main job this year has been building REMA 1000's AI capability: from the first solutions in production to broad adoption, responsible governance and benefits we can measure.
Architecture and development of AI solutions, agents and assistants connected to core systems and integrations. From prototype to production โ secure, observable and maintainable.
Making AI an everyday tool. Training, champions and use cases that meet real needs across the business โ not just in IT.
A framework for responsible use: policies, risk assessment, data access and compliance with regulation such as the EU AI Act and GDPR โ without slowing innovation down.
From potential to impact. Benefit maps, measurement and follow-up, so every AI investment can be explained in time saved, quality and business value.
The hard part of AI is rarely the model. It is getting it adopted, governed and measured.
02Person
I like things that connect. It started with communications on a frigate and printers at Ricoh, became retail systems for a thousand stores, and is today language models talking to the core systems of one of Norway's largest grocery chains.
01 โ At sea
In 2007 I served on the frigate HNoMS Fridtjof Nansen, in artillery and communications. There I learned what I still bring into every architecture: systems have to work when it matters.
59ยฐ54โฒ N ยท 10ยฐ44โฒ E
Photo: Wikimedia CommonsI would rather never leave the keyboard. So this site has shortcuts โ
CLIs in Go for the weather, the power at home and Confluence โ and a set I let AI agents work in, instead of MCP servers. All of it open on GitHub.
Problems are inevitable. And they are soluble โ with better explanations.My reading of The Beginning of Infinity, David Deutsch
03Experience
Joined as integration architect, responsible for the integration landscape between stores, the chain and suppliers. Since January 2026 my primary focus has been AI: development, adoption, governance and benefits realisation across the business.
Advisor and architect for retail clients. End-to-end solutions for stores, point of sale and integrations, from needs and target architecture to delivery.
Architect on projects and programmes for national eHealth solutions, including health sector messaging over AMQP.
Ten years from support to architecture. Store Solution Manager for a Norwegian chain of about 1,000 stores, then Solution Management and Professional Services, where I became a solution architect. Built everything from internal tools to integrations and larger end-to-end solutions.
Field service on multifunction and production printers, and training in Ricoh's solutions for printing, scanning and OCR.
Served aboard the frigate HNoMS Fridtjof Nansen.
04Writing
On kristoffer.dev I write about AI agents, developer setups and what I learn along the way. Usually with code.
The status line as a small dashboard: weather from my own CLI, rate limits that know my pace, and a bill that is right.
Why I give AI agents small, isolated Go tools to work in, rather than MCP servers.
An autonomous AI assistant on its own home lab server โ with isolation, network control and custom tooling.
A spark from NDC Oslo every integration architect should keep: treat your events like internal APIs.
05Expertise
06Education
University of South-Eastern Norway
Horten Technical College
Contact
About AI that has to run in production, integrations that have to fit together, or just a good tool. Drop me a line.
hei@kristoffer.dev