Services
What we do, specifically
Five areas we help with, and the concrete steps in each. Every service has its own page with more detail.
Infrastructure modernisation and cloud
Cloud, your own servers, or both – by cost, risk and operational effort.
- Inventory. We list your servers, applications and how they depend on each other, who has access to what, and what running it all costs per month, in one overview.
- Comparing options. Cloud, your own servers, or both. We weigh each on cost, risk, operational effort and how easy it is to leave later. You get a recommendation with the reasons.
- Target design. We design the network, identity and access, backups and monitoring to fit your applications, team and budget.
- Step-by-step move. We split the migration into smaller steps. Each has a test and a rollback procedure and is scheduled outside your peak hours, without a one-off switch-over of the whole environment.
- Code and documentation. The result is brought into IaC and documented. The environment can be rebuilt at any time and remains yours after the engagement ends.
For example: An application moves off an ageing server to the new environment piece by piece, without one big switch-over.
DevOps and automation
New versions in production without manual steps, and a clear view of what runs where.
- Deployment review. We look at how a new version reaches production today, what is done by hand and what slows it down. That tells us where to start.
- Faster, cheaper delivery. We automate and speed up builds and tests to shorten deployment time and reduce build costs.
- Containers. Applications are containerised so they run identically in development, test and production. Orchestration is added only when it pays off.
- App overview. An overview of which version runs in which environment. Every change is recorded and can be reverted.
- Safe rollouts. A new version reaches a small share of users first. On errors, the previous version is restored automatically.
For example: Once a change is approved, tests, deployment and a check of the new version run automatically.
Security and technical assessments
Priorities by risk, and controls put into practice.
- Technical review. We review your infrastructure and development processes: access and permissions, network, updates, logging, backups and how deployments work. We look at how the systems really are, not only at the documentation. The output is a report of the findings.
- Priorities. Findings are ranked by risk and effort: what to fix now, what later and what to accept as a risk. The output is a concise remediation plan.
- Remediation. We put controls in place in production: multi-factor authentication (MFA), network segmentation into zones, patches, removing unused accounts, and encryption, with everyday work in mind.
- Verification. Test restores of backups, access reviews and checks that alerts are delivered. Every control is verified, not assumed.
- Evidence for audits and NIS2. We write down what is in place, how it is evidenced and who is responsible. We can then keep monitoring the state.
For example: We remove former suppliers’ access, apply missing patches and check that backups actually restore.
Ongoing operations
Monitoring, updates, backups and incident handling.
- A foundation in code. Before taking over operations we bring the environment into IaC and document it. Every change is traceable and management does not depend on one person.
- Monitoring. We track the health of infrastructure and applications so that problems are caught before users notice them. Alerts are handled within the agreed response times.
- Updates. Systems and their dependencies are patched on a schedule, in agreed windows. Security patches are not put off.
- Backups. Backups kept apart from production, regularly verified by test restores, with a known recovery time.
- Incidents and reporting. Incidents are fixed, traced to their cause and followed up so they don’t repeat. A regular status and cost report is included.
For example: A full disk or an expiring certificate is handled when the alert comes, not after an outage.
AI platform
Company AI under control.
- Mapping. We look at which AI tools are already in use, where data goes and who holds which keys. That tells us what to bring together first.
- Company chat. Employees sign in with their company account and get approved models only. Model keys stay on the server, not with people.
- One gateway to models. Applications and agents reach models through one controlled entry point: approved models, limits and budgets per team.
- Visibility with Langfuse. A record of what applications and agents did, what they worked from, what it cost and whether the result was right.
- Rules for data. We set which data may go where, where it is processed and how long it is kept. Sensitive agent actions need human approval.
For example: An agent drafts a quote from an enquiry. You see which stock data it used, what it cost and whether sales approved it without changes.
Contact
Request a consultation
A short description of your environment and what you need solved is enough. We reply within one working day. If your team already covers operations, security and cover, we will tell you.