Cloud & infrastructure
Infrastructure your team can run, understand and develop. For companies and agencies that run many websites and services in the cloud, where costs and risk grow faster than the team.
The first conversation is free: 30 minutes online, no preparation and no commitment.
Who this is for
Companies with many websites and brands
A dozen or more sites built in different years, by different agencies, on different hosting. Marketing waits for IT, IT does not know who owns which site, and every update is a separate project. If the CMS and the publishing process are part of the problem, see digital products & platforms.
Teams where deployments depend on one person
One person knows the passwords, the servers and the order of steps. Their holiday stops deployments, and their departure would be an incident. The documentation lives mostly in their head.
Organisations facing a migration or a cost review
The cloud bill grows every month and nobody can say what could be switched off. Or you are planning a move from a dedicated server or between clouds and want to know the dependencies before anything is touched.
What we usually find
The same problems come up in most environments we review:
- Machines running around the clock for sites that a few hundred people visit a day.
- CMS admin panels reachable from the public internet, protected by a password alone.
- Access granted years ago to people and agencies that no longer work with you.
- Backups that nobody has ever tried to restore.
- Every site configured differently, so none of them can be updated in bulk.
- Several billing accounts and no single place where the whole cost is visible.
Most of these can be fixed without rebuilding everything. We start with the ones that cut cost or risk the fastest. The last two are often also a compliance question: who has access to personal data and on what basis, which is part of our digital compliance work.
What we work on
Architecture & migrations
We map services, data and dependencies, choose the target architecture and plan the move in stages. Each stage has acceptance criteria and a way back if validation fails.
Delivery & operations
Repeatable environments, CI/CD, monitoring, backups and recovery procedures. Routine tasks that can be written down as steps become automations, so the team runs them without manual work.
Costs & resource use
We review what is running, why it is running and how it is billed. Right-sizing, static publishing and workloads that run only when needed are options we assess against actual usage.
What we have done before
The founders’ experience from projects delivered before the company was set up, directly and in cooperation with agencies, for large organisations and startups. More under achievements.
- Infrastructure and operating costs down by 80% after a platform rebuild, while the number of sites, integrations and automations kept growing.
- More than 100 virtual machines: every site on its own isolated machine, which starts for the time of work and switches itself off when nobody needs it.
- More than 6 years without a security incident on the sites we ran: the admin panel behind a private tunnel and a sign-in gate.
- More than 250 cloud projects under one model of roles and permissions, using more than 40 Google Cloud and Firebase services.
- A technical team of a few people running dozens of sites. Scale comes from architecture, not headcount.
Example: many brands, one platform
A typical starting point and what we built from it. The client’s name, figures and configuration details are something we discuss in a meeting.
Before
All brand sites in one environment: a shared server, shared passwords, one line on the invoice. A failure or break-in on one site threatened all of them, and every update needed a maintenance window for the whole platform.
After
Each site as its own Google Cloud project: its own machine, its own permissions, its own cost visible on the bill. Content published statically, the CMS panel behind a private tunnel, machines switched on only while editors work.
Result
Infrastructure and operating costs down by 80% while the number of sites grew. More than 6 years without a security incident. One model of roles and access for the client, agencies and media houses, run by a team of a few people.
Three steps, each one you can stop after
Free consultation
30 minutes online. You tell us what you have and what hurts. We tell you whether and how we can help, and what we would do first. No preparation, no access to the environment, no commitment.
Infrastructure review
Fixed scope and a fixed price agreed before we start. Up to two weeks from receiving read-only access. We change nothing at this stage. A report and a review session with your team.
Implementation
Changes from the report delivered in stages, with acceptance criteria and a price agreed for each stage. After every stage you decide whether we continue or your team takes over.
What the review covers
- Inventory: services, machines, domains, billing accounts and who has access to what.
- Costs: what costs how much and why; which items can be switched off, reduced or replaced with static publishing.
- Risks: single points of failure, untested backups, public admin panels, dependence on one person.
- Plan: a list of changes ordered by effect and effort, with estimated savings and a proposed sequence.
- A review of the findings with your team and a decision on whether and what to implement next.
This is what a fragment of the cost section looks like. The figures are illustrative, the layout is real:
| Item | Current state | Recommendation | Effect |
|---|---|---|---|
| Company website, 4 vCPU machine | Runs around the clock for a few hundred visits a day | Static publishing, machine on only while editing | Machine cost down by about 90% |
| Database shared by 12 sites | One instance, a failure affects all of them | A separate database in each site’s project | Failures and costs isolated |
| CMS admin panel | Public, password login | Private tunnel and sign-in with company accounts | Attack vector closed |
| Access | 23 accounts, 9 inactive, 3 shared | Remove inactive ones, roles instead of shared accounts | Auditable permissions |
| Backups | Daily, never restored | Restore test every quarter, written procedure | Confirmed recovery time |
The review is also the first stage of a migration: the inventory and the dependency map are what you need anyway before moving anything.
What stays on your side
We work in your cloud accounts, on your domains and in your repository. Administrative access stays with the company, not with the contractor.
- Environment configuration and deployment procedures written as code, not held as one person’s knowledge.
- Operational documentation: what runs, where, who has access and how to restore it after a failure.
- Tidy permissions for the team, agencies and partners, reviewable in one place.
- Knowledge transfer to your team, as workshops where useful, or an agreed monthly scope of continued maintenance.
Technology follows the workload
We work with Google Cloud Platform, Firebase, Kubernetes, Linux and CI/CD tooling. The choice depends on the workload and the team that will maintain it. A small static site and a platform with several services need different solutions. We do not move things to the cloud for its own sake: sometimes the best result is switching off half of what is running. When no ready-made tool exists, we build it as custom R&D, such as panels for managing machines or static publishing from a CMS.
FAQ
Do we have to move everything?
No. Often the best result comes from switching off unnecessary resources and tidying access in the current environment. Migration is one option, not the starting point.
Will we lose control of the environment?
The opposite. We work in your accounts, document every step, and administrative access stays on your side from day one.
What about our current agency or IT department?
We can work alongside the existing team or take over a clearly defined part. The split of responsibilities is written down before we start.
Is a small company too small for you?
No. One site and a few services are often the fastest return. We size the scope to the environment, not the other way round.
How do you charge?
First consultation: free, 30 minutes online. Review: fixed price. Implementation: stages with acceptance criteria and a price agreed for each stage. Operations: a monthly scope agreed after handover.
What about data and confidentiality?
We sign a non-disclosure agreement and a data processing agreement before receiving access. Access is personal, limited to the scope of work and revoked when it ends. How we handle data from the contact form is described in the privacy policy.
Let’s look at your infrastructure
Tell us how many sites and services you run, where they run and what worries you most: cost, risk or dependence on one person. We will propose a time.
The first conversation is free: 30 minutes online, no preparation and no commitment.