IT infrastructure services for small and mid-sized companies

We build and run IT systems.

The systems include hosting platforms, monitoring, sign-in, support portals and integrations. The services cover environment setup, reviews, backup and recovery, and day-to-day operations. We work with Windows, Linux and custom applications on Azure, AWS, Oracle or on-premises. AI is added where it helps, on self-hosted models.

Systems

What we build and run

Each system is built to agreed requirements, then run by us or handed over to your team with its documentation.

Services

Work we do on your environment

Each service is a piece of work on a new or existing environment: setting it up, reviewing it, designing and testing its backups, or running it day to day.

Problems

Common problems and what we do about them

  • ProblemUsers report outages before IT notices, because alerts go to a mailbox nobody reads.

    SolutionEach system reports its status on a schedule. When one goes quiet or fails a health check, an alert goes to a named owner.

    Monitoring and alerting
  • ProblemRequests get lost between email, chat and memory, with no view of what is waiting.

    SolutionRequests from email, chat and phone land in one queue. Each becomes a ticket with an owner, a priority and its own history.

    Service desk and ITSM
  • ProblemThe infrastructure bill keeps growing, and no one can say which systems cause it.

    SolutionWe break spend down by system and owner, find idle and oversized resources and unused licences, rank the cuts with reversible ones first, and set budget alerts.

    Cost optimisation
  • ProblemAccess granted temporarily stays in place, and leavers keep their accounts for months.

    SolutionWe review who can reach what, including service accounts and keys, move permissions into role-based groups, and run onboarding and offboarding from one identity provider such as Entra ID.

    Identity and access management
  • ProblemBackup jobs report success, but no full system has ever been restored from them.

    SolutionWe map what must come back first, write step-by-step recovery procedures, and restore each critical system end to end, recording how long each restore takes.

    Backup and recovery
  • ProblemThe environment grew in pieces. Changes get put off because no one is sure what they will break.

    SolutionWe map networks, routing, DNS, identity and dependencies from the deployed state, mark single points of failure, and plan changes in steps that are each safe to stop at.

    Architecture review

Cases

Systems we built and run

Each one is still in operation. Details on request.

Multi-shop webshop platform

Requirement
One platform had to host many shops, with online payments, subscriptions and custom domains.
What we built
A multi-tenant webshop platform. Stripe handles payments and subscriptions, and each shop can run on a custom domain with its own certificate.
Result
Shops, Stripe payments and subscriptions, and custom domains with their own certificates all run on one platform.
Webshop and ERP systems

Central sign-in and support portal

Requirement
Internal apps needed one controlled way to sign in, open to invited users only, and requests needed one place to go.
What we built
Single sign-on for every internal app through one identity provider, with access by invitation only. People sign in with Microsoft or Google accounts; any OIDC or SAML provider, or on-premises Active Directory over LDAPS, can be added. Requests go to a branded support portal backed by Jira.
Result
Every internal app signs in through one place, only invited accounts get in, and requests are tracked in Jira.
Identity and access management

Release pipeline with automatic rollback

Requirement
Releases had to go to several servers, and a failed deploy could not stay live or wait for someone to notice it.
What we built
A release pipeline across several servers. Each release needs an approval, runs health checks after deployment, and rolls back on its own if something fails.
Result
No deploy goes out without an approval, and a failed one is rolled back without anyone stepping in.
Application platform and hosting

Delete reports for a company file share

Requirement
A company file share on Azure Files needed a record of who deleted what, and when.
What we built
Daily delete reports for the share, alerts within minutes, and a lookup in Active Directory that turns account IDs into real names.
Result
The daily report shows who deleted what and when, with real names, and alerts arrive within minutes.
File share audit and alerts

Servers without direct internet exposure

Requirement
The servers had to serve visitors without being directly reachable from the internet, and admin access needed a private path.
What we built
Visitor traffic passes through Cloudflare only. Servers that visitors do not need have no public IP address. Administration runs over a private mesh network.
Result
There is no direct way in from the internet: visitors come through Cloudflare, admins through the mesh network.
Network and connectivity

Private AI assistant

Requirement
An AI assistant was needed whose answers come from models on hardware we control, not from a public chatbot.
What we built
An assistant for invited users that answers from local AI models running on our own hardware.
Result
It runs on our own hardware, and every answer comes from a local model.
AI in everyday operations

What we work with

Platforms
  • Azure
  • AWS
  • Oracle
  • VMware / VCD
  • On-premises
  • Microsoft 365
Servers and containers
  • Windows Server and Linux
  • For exampleDocker
  • For exampleKubernetes, AKS, ECS / EKS
  • For exampleAzure App Service
Networking and edge
  • For exampleAzure Virtual Network, Network Security Groups
  • For exampleAzure Firewall, Private Endpoints
  • For exampleVPN Gateway, ExpressRoute
  • Private DNS
  • For examplenginx, Traefik
  • For exampleCloudflare
Identity and access
  • For exampleZITADEL, Keycloak, Okta
  • Entra ID and Active Directory
  • Directory sign-in over LDAPS
  • SCIM provisioning
  • For exampleHashiCorp Vault
  • For exampleAWS IAM
Data, storage and backup
  • For examplePostgreSQL
  • For exampleAzure Files
  • For exampleAzure Backup, AWS Backup
  • For exampleRestic, Borg
  • For exampleVelero
Monitoring and service management
  • For examplePrometheus, Loki, Azure Monitor
  • For exampleGrafana, Application Insights
  • For exampleLog Analytics
  • For exampleJira Service Management, GLPI, Zammad, ServiceNow
Integration and development
  • For exampleNode.js, Python
  • For examplePowerShell
  • For exampleGitHub Actions
  • For exampleAzure Logic Apps, n8n, Temporal
  • For exampleRabbitMQ, Kafka
  • For exampleMicrosoft Graph
  • For exampleStripe
AI
  • For exampleLlama, Mistral, Ollama
  • For examplepgvector, Qdrant, Weaviate
  • Data extraction with human review

How we work

How an engagement runs

Management gets cost, risk and priorities in plain terms. The IT team gets a plan of what to change and in which order.

  1. 01

    Look at what is there

    We read the configuration as deployed and note where problems occur today.

  2. 02

    Prioritise

    A short written list of issues and risks, each with its impact, effort and expected outcome, ranked by what matters to the business.

  3. 03

    Change in safe steps

    Small, reversible changes, each safe to stop at. We make them, or your team does, following the plan.

  4. 04

    Hand over, or keep it running

    Documentation and runbooks that match the running system. Your team takes over, or we keep it running on a monthly plan.

Contact

Describe what you need

A few lines are enough: what you need or what goes wrong, which systems are involved and where they run.

What happens next

  1. We read it and ask about anything that is missing.
  2. You get proposed next steps. If you do not need us, we say so.
  3. If there is work for us, we start with a short review of what is there.