Come with the work that feels heavy.We will make it light.

Send a short brief

A software and AI company in Malmö since 2019. Data scientists, engineers and architects who join your team or deliver the whole project.

A full team,working inside yours.

Data scientists, ML engineers, software and cloud engineers, and architects, all in one company. We add people to your team where you need more hands, work inside it as one of your own, or take on the whole project with a team of ours, and we grow or shrink with the work.

Book a call

We build and run our own products on the same stack we use for client work, so we only recommend what we would put in production ourselves. Source, configuration and notes move to your team as we go, and when we leave, the keys stay with you.

How we work

Delivery

Embedded delivery

We join your engineering team and work in its repositories, tools and ceremonies. One named lead stays accountable.

Starts with: A named lead in your team
Works in: Your repos and rituals
Typically: 3 months to 2 years

Ask about this

Legacy

Modernisation

We find what is expensive to change in an ageing system and replace it in phases, while the rest keeps running.

Starts with: An assessment of the estate
Approach: Phased, not a rewrite
Meanwhile: The system keeps running

Ask about this

Advisory

Diligence and advisory

A verdict on a software asset, written for the people paying for it. The judgement we would act on ourselves.

Starts with: A scoping call and code access
Covers: Architecture, data, team
Typically: 3 to 5 weeks

Ask about this

GenAI development

Platforms, interfaces and the software a model lives in, or a model wired into the systems you already run.

Starts with: A test on your own data
Builds: Platforms and integrations
Typically: 8 to 14 weeks

Ask about this

Compliance

SOC 2 readiness

We get your AWS estate, policies and evidence ready for a SOC 2 audit, Type I and then Type II, and help you keep them ready. An independent auditor carries out the audit and issues the report.

Starts with: Scope and a gap list
Builds: Controls, policies, evidence
Typically: Type I in 3 to 6 months

Ask about this

Selected work.Ours, and two we can show.

Two are products we build and run ourselves. Two are AI systems we built for clients in regulated work.

Our product
Murmur
Sound for focus and sleep. Every loop is written by our own music model.
Learn more about Murmur
Our product
Morrow
The puzzles people pay for, free every morning. Written by our model.
Learn more about Morrow
Client work
Compliance SLM
A first-pass auditor in the client’s cloud. 94 in 100 match the reviewer.
Learn more about Compliance SLM
Users get access only through a request their manager approves.
AC-2Account management
AC-6Least privilege
AU-6Audit record review
Client work
Library-backed extraction
Returns only what a library of known controls holds, in any domain.
Learn more about Library-backed extraction
More work
Ask about other work
Most client work is under NDA. Tell us the problem and we’ll show you what fits.
Send a short brief

AWS, from the first account up.Pick a service to see what it sets up.

Three of these are listed on AWS Marketplace. The drawing is your AWS organisation as a cabinet: each tray is an account, and blue is what the service puts in place.

1Accounts open2Guardrails lock3Logs land in one place

Landing Zone Foundation

A governed, multi-account cloud foundation, built with the platform's own governance tooling. For greenfield builds, and for teams already running in production without account separation or guardrails.

Structure: Account hierarchy, preventive guardrails, central identity
Baseline: Centralised logging, threat detection, posture monitoring
Handover: Documentation and a prioritised remediation backlog

See the listing

How buying works

These are professional services listings, so there is no checkout price. You request the service, we agree scope on a call, and we issue a private offer for you to accept. Billing arrives through the cloud account you already have.

What is not included

Cloud infrastructure and model usage are billed to you by your provider, separately from the service itself. We set up budgets and alerts so consumption is visible from the first day.

All listings

Landing Zone Foundation, Architect as a Service and Sovereign AI Perimeter are listed on AWS Marketplace as private offers. Migration and GenAI on Bedrock are delivered directly.

Our AWS Marketplace profile

How we work

Same four steps,a week or two years.

A three-week review and two years inside your team run the same way. Pick a way in and drag along the line to see what happens when.

A three-week review and two years inside your team run the same way. Pick a way in to see what happens when.

FrameWeeks 1–2
JoinWeek 3
DeliverWeeks 4–11
HandoverWeek 12

Day 1 · Frame

We agree the questions with you, or with your investors.

We agree the goal, what is in the way and how we will both know it worked, and write it down.

Week 1 · Join

Read access to code, cloud and documents, and interviews with your team are booked.

Our people get access and start inside your team, your tools and your routines.

Week 2 · Deliver

Architecture, data and delivery are reviewed, with the costs and risks priced.

The work lands in small pieces you can see and use. When the evidence changes, so does the plan.

Week 3 · Deliver

Findings are checked with your engineers, so nothing in the report is a surprise.

The work lands in small pieces you can see and use. When the evidence changes, so does the plan.

Week 4 · Handover

A written report: the red flags, what they cost to fix and a 90-day plan, then a read-out.

Code, setup and know-how move to your team, so it all runs without us.

Day 1 · Frame

We agree what the first 40 hours should answer.

We agree the goal, what is in the way and how we will both know it worked, and write it down.

Week 2 · Join

Read-only access to your AWS accounts and diagrams.

Our people get access and start inside your team, your tools and your routines.

Week 3 · Deliver

An architecture review: what holds, what will not, and what it costs to change.

The work lands in small pieces you can see and use. When the evidence changes, so does the plan.

Week 5 · Deliver

Decision records for the open choices, ready for your team to sign off.

The work lands in small pieces you can see and use. When the evidence changes, so does the plan.

Week 8 · Handover

A roadmap you can act on. Draw down the next block only if you need it.

Code, setup and know-how move to your team, so it all runs without us.

Day 1 · Frame

We pick the use case together and agree what a good answer looks like.

We agree the goal, what is in the way and how we will both know it worked, and write it down.

Week 2 · Frame

A test set of real questions from your team, to score every version against.

We agree the goal, what is in the way and how we will both know it worked, and write it down.

Week 3 · Join

Access to your AWS account and data. The first prototype runs on your own documents.

Our people get access and start inside your team, your tools and your routines.

Week 6 · Deliver

The first version answers in staging, scored against the test set.

The work lands in small pieces you can see and use. When the evidence changes, so does the plan.

Week 9 · Deliver

Connected to your systems, with guardrails on and the running cost measured.

The work lands in small pieces you can see and use. When the evidence changes, so does the plan.

Week 11 · Deliver

Live for the first users, with a trace behind every answer.

The work lands in small pieces you can see and use. When the evidence changes, so does the plan.

Week 12 · Handover

Code, evaluations and runbooks handed to your team.

Code, setup and know-how move to your team, so it all runs without us.

Week 1 · Frame

We agree what is in scope and which criteria apply. Security always does.

We agree the goal, what is in the way and how we will both know it worked, and write it down.

Week 3 · Frame

A gap list in priority order, and a first draft of your system description.

We agree the goal, what is in the way and how we will both know it worked, and write it down.

Week 5 · Join

We start in your AWS accounts and tools, next to the people who will own the controls.

Our people get access and start inside your team, your tools and your routines.

Month 2 · Deliver

Policies written, controls on your landing zone, and evidence collected automatically.

The work lands in small pieces you can see and use. When the evidence changes, so does the plan.

Month 4 · Deliver

A mock audit, tested the way an auditor would. We close what is left and shortlist auditors.

The work lands in small pieces you can see and use. When the evidence changes, so does the plan.

Month 5 · Deliver

Type I: an independent auditor checks the design of your controls on one date.

The work lands in small pieces you can see and use. When the evidence changes, so does the plan.

Month 6 · Handover

The Type II window opens. Your team runs the controls, and we check in every month.

Code, setup and know-how move to your team, so it all runs without us.

Month 12 · Handover

The window closes. The auditor tests it and issues your Type II report.

Code, setup and know-how move to your team, so it all runs without us.

Week 1 · Frame

We agree the goals, the shape of the team and how we work with yours.

We agree the goal, what is in the way and how we will both know it worked, and write it down.

Week 3 · Join

Our people join your stand-ups, your repositories and your on-call rota.

Our people get access and start inside your team, your tools and your routines.

Month 2 · Deliver

The first releases from the joint team reach your users.

The work lands in small pieces you can see and use. When the evidence changes, so does the plan.

Month 6 · Deliver

A review together: grow the team, shrink it, or keep it as it is.

The work lands in small pieces you can see and use. When the evidence changes, so does the plan.

Month 12 · Handover

What we know has moved to your own people, and we step out.

Code, setup and know-how move to your team, so it all runs without us.

Week 6 · Deliver

The first version answers in staging, scored against the test set.

The work lands in small pieces you can see and use. When the evidence changes, so does the plan.

4 / 7

Frame
Weeks 1–2
- Day 1
  We pick the use case together and agree what a good answer looks like.
- Week 2
  A test set of real questions from your team, to score every version against.
Join
Week 3
- Week 3
  Access to your AWS account and data. The first prototype runs on your own documents.
Deliver
Weeks 4–11
- Week 6
  The first version answers in staging, scored against the test set.
- Week 9
  Connected to your systems, with guardrails on and the running cost measured.
- Week 11
  Live for the first users, with a trace behind every answer.
Handover
Week 12
- Week 12
  Code, evaluations and runbooks handed to your team.

Hello from Malmö

Adamass

Come with the work that feels heavy. We will make it light.

Send a short brief Back to top

Come with the work that feels heavy.We will make it light.

A full team,working inside yours.

Five ways in

Embedded delivery

Modernisation

Diligence and advisory

GenAI development

SOC 2 readiness

Selected work.Ours, and two we can show.

Murmur

Morrow

Compliance SLM

Library-backed extraction

Ask about other work

AWS, from the first account up.Pick a service to see what it sets up.

Landing Zone Foundation

How buying works

What is not included

All listings

Same four steps,a week or two years.

Frame

Join

Deliver

Handover

Adamass