We join your team, using the same repositories, tools, and ceremonies. The aim is a family-style way of working built on trust, shared contexts, and pace.
Come with the work that feels heavy.We are happy to make it feel light.
Heavy work welcomeWe keep it lightThen it's yours
Senior delivery. Fixed accountability.
A boutique IT consultancy for embedded software delivery, modernisation, GenAI development, technical diligence, and strategic advisory.
- MalmöBased in Sweden since 2019, working with founders, investors, and engineering leaders who want a clear owner.
- One leadOne named technical lead stays accountable for the engagement, from the first brief through handover.
- Senior rosterSenior people do the work. Decisions stay written down so the assignment remains understandable after we leave.
Work as one team.
We join your repositories, tools, and ceremonies with one named technical lead accountable for the engagement.
- Same reposWe join your repositories, tools, and ceremonies instead of running a parallel vendor process beside the team.
- Named leadOne technical lead owns the relationship and the technical direction for the length of the assignment.
- Shared workThe aim is a family-style way of working: trust, shared context, and pace, because that is how the work holds up.
Modernise without losing control.
We improve applications, platforms, and data systems in practical phases, adding AI only where it earns its place.
- Phased changeWe improve applications, platforms, and data systems in practical phases rather than betting everything on a rewrite.
- Keep controlThe current system stays operable while the work is in progress, so ownership and delivery never go dark.
- AI when usefulWe add AI only where it earns its place against real acceptance criteria and the people who will operate it.
Make the decision with evidence.
Technical diligence and strategic advice based on architecture, operations, team capability, security, and delivery risk.
- ArchitectureWe examine how the system actually works: structure, interfaces, data, and the constraints that shape the next decision.
- RiskOperations, security, team capability, and delivery risk sit in the same written view, not in separate conversations.
- Written judgementThe report reflects the judgement we would act on ourselves. We do not recommend a path we would not stand behind.
Westructureuncleartechnicalwork,deliveritwithyourteam,andleaveownershipbehind.
Senior people. Clear ownership. Work that holds up.
Small roster. Named owners. Shipped outcomes.
Adamass AB is a boutique IT consultancy in Malmö, Sweden, founded in 2019. Senior people take named ownership of embedded software delivery, modernisation, technical due diligence, and generative AI for founders, investors, and engineering leaders. Most work is embedded delivery with written scope and milestones — engagements have run from a few months to about three years.
Most problems arrive between strategy and engineering, prototype and production, or documentation and operations. We structure the work, deliver it with your team, and keep one person accountable.
We do not add process for its own sake. Decisions, assumptions, and changes are written down so the work remains understandable after we leave.
Engagements close with source, configuration, deployment notes, and operational documentation transferred as agreed in scope.
Organisations we can name in public.
What we take on.
Four ways in. The closed row already carries the sentence that matters, so a visitor who never clicks still leaves knowing what we do.
Named lead inside your team
Work in your repositories and ceremonies
Applications, platforms, data, or production AI
Accountability that stays with one person
Typically 3 months to 2 yearsApplicationsPlatformsDelivery
Our core services, bought the way your procurement already works. They run through the cloud agreement you already have and land on the bill you already pay. Senior delivery, one named lead, written handover.
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
Architect as a Service
Senior cloud architecture judgement in blocks of 40 hours, drawn down flexibly across up to two months. Every block produces written output: decision records, review reports and a roadmap you can act on.
Base unit
40 hours, used over up to two months
Scope
Governance, AI platform design, cost, automation, enablement
Stacking
Buy multiple blocks, or attach one to an implementation
Sovereign AI Perimeter
A private AI assistant running inside your own cloud account, on managed foundation models. Reachable only over VPN or another controlled channel, never the open internet. No new vendor holds your data.
Location
Your account, your region, your security boundary
Access
Private channel only, no public endpoint
Control
Model access, spend limits and audit logs stay yours
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.
Private offers, issued within a week
Tell us which package, and what you're trying to get done.
Or write straight to hello@adamass.se
Structure without the consultancy theatre.
The exact shape changes with the assignment. The principles do not: visible scope, senior ownership, useful documentation, and a clear transfer of responsibility.
Selected work.
One public engagement. A specialist regulatory model developed from an expert-labelled workflow, evaluated on held-out work, and deployed inside the client's AWS account.
Regulatory model
A first-pass regulatory auditor, private to the client's cloud.
It reads one regulatory article and returns the risks and controls that bind, or nothing when the text does not. Built with supervised fine-tuning and reinforcement learning. A reviewer still signs.
ComplianceSynthetic dataPrivate cloud
The architecture
Control TowerOrganisationsIAMAmazon S3SageMakerAmazon VPCCloudWatchBudgets
The model
27B
parameter specialist model
Held-out evaluation
94 in 100 match the reviewer6 the reviewer corrects
Scored on a held-out gold set — expert labels withheld from training.
What the model does
- Returns the risks a regulatory article creates94% match
- Maps every risk to the control that answers it93% match
- Emits output the downstream system can parse100%
- Covers rare labels through synthetic datasynthetic
- Returns nothing when the text does not bindguardrail
- Leaves the client's own AWS accountnever
- Signs the compliance opinionnever
Next step
Ask about a similar model.
Now that you've seen the work,see how we actually run it.
Write the problem down first.
We write down objectives, constraints, assumptions, and success criteria before delivery begins.
- ObjectivesObjectives, success criteria, and the shape of the outcome are written down before delivery gets expensive.
- ConstraintsAssumptions, limits, and open questions stay explicit so later changes can be judged against the original brief.
- Named ownerOne lead is named at the start and remains accountable for scope, decisions, and the quality of the write-up.
Deliver in the open.
We work in your systems, keep decisions visible, and adjust against evidence without losing ownership.
- Your systemsWe work in your repositories, tools, and ceremonies so the work lives where your team already operates.
- Visible decisionsProgress, decisions, and changes stay written and traceable. Nothing important lives only in a call.
- EvidenceWe adjust when the evidence changes, without losing ownership or turning the assignment into open-ended theatre.
Leave the work in their hands.
Source, configuration, operating notes, and context move to your team when the assignment closes.
- SourceSource, configuration, and deployment notes move to your team when the assignment closes, as agreed in scope.
- Operating notesContext, decisions, and how to run the work are written so the next person does not have to reconstruct them.
- Your teamOwnership should not depend on us staying. The engagement closes when the work is demonstrably yours.
hello@adamass.se
Send a short brief to Adamass AB in Malmö. We reply with availability, then use an intro call to confirm fit, scope, and timing.