The layer that decides whether everything above it works. We design, provision, tune and then operate the infrastructure a platform runs on — including the ongoing management that keeps a tuned system tuned.
Application performance, availability, security posture and cost all resolve to infrastructure decisions that are usually made once, early, and then inherited. A platform running on infrastructure designed for a much smaller version of itself will exhibit symptoms that look like application problems and are not.
You need the infrastructure layer owned, tuned and monitored rather than treated as an inherited constant.
You are running a platform whose reliability matters commercially, without an infrastructure engineer to own it.
Reliability problems are surfacing as user complaints, and you need the underlying cause identified.
Engineering faults are rarely confined to the engineering layer. These are the commercial consequences we see most often.
Application optimisation cannot overcome a platform that has run out of the resource it needs. Symptoms present as application faults and lead teams to optimise the wrong tier.
A server that was correctly tuned two years ago is not correctly tuned now: traffic, software versions and data volumes have all changed. Without review, configuration becomes progressively less appropriate.
Shared and general-purpose environments are economical at small scale and become a ceiling at larger scale, frequently at the least convenient moment.
Each of these is work we carry out, not an area we advise on.
Establishing what the platform actually needs — by resource, by concurrency and by growth trajectory — rather than what it currently has.
Dedicated and VPS environments sized and configured for the observed load profile, including the concurrency settings that default configurations rarely get right.
Designing what is served from where, and with what cache policy. Getting this right removes a large share of load from the origin entirely.
Distributing demand and removing single points of failure, so that capacity and availability are not the same resource.
Layered caching where the correctness of the invalidation policy matters as much as the hit rate.
Instrumentation that surfaces developing problems before they become incidents, with alerting calibrated to be actionable rather than ignored.
Backups that have been tested by restoring from them, and a recovery procedure that has been rehearsed rather than assumed.
Ongoing management of the infrastructure estate: patching, capacity review, incident response and continuous tuning as the platform changes.
The sequence is deliberate. The order is usually what determines whether the work holds or has to be repeated.
Capacity decisions are made from observed load profiles, including peaks, not from server specifications or rules of thumb.
Caching and edge delivery are almost always cheaper and more durable than provisioning to handle work that did not need to reach the origin.
Sizing must accommodate the worst case; day-to-day operation is tuned for the common case. Conflating the two produces either fragile systems or wasteful ones.
Infrastructure without instrumentation is infrastructure whose behaviour is unknown. Monitoring is delivered as part of the build, not as an addition.
A tuned system does not stay tuned. Continuous management is what converts an infrastructure project into sustained reliability.
Documentation is a deliverable, not an afterthought. On most of these engagements a large part of the value is a defect report precise enough for another team to act on.
Engagements where this capability was the substance of the work rather than a line item.
Since 2019, Soludome has managed infrastructure and platform operations for one of Spain's largest online communities. The work covers server and performance optimisation, CDN architecture, load balancing and site security under sustained traffic.
A stockbroking platform publishing at news velocity was losing search visibility to problems that had nothing to do with content quality. Two workstreams ran in parallel: sustaining a high-volume editorial output across business and market categories, and diagnosing the technical faults — a domain safety flag, recurring server errors, and a metadata defect on a templated page type — that were suppressing how much of that output search engines could actually reach.
A large marketplace platform in the United States was experiencing critical downtime from compounding traffic and application faults. Soludome analysed requests through the web application firewall, identified and blocked the DDoS patterns, and repaired a third-party payment flow that allowed links to be generated repeatedly without authentication. Server load fell and platform performance improved after the work.
Since 2021, Soludome has managed infrastructure, site performance and technical SEO across GuzziTech and RideMalibu as a connected web estate. The engagement includes dedicated infrastructure and continuing operational ownership.
These overlap at the edges. Sending you to the right page is more useful than having you work it out.
The constraint is in the page rather than beneath it. See Website Performance Engineering.
That is a concurrency and architecture problem. See High-Traffic Website Engineering.
We provision and manage infrastructure, sometimes on the client's own accounts and sometimes on ours, depending on what suits. Where we manage it, the client retains ownership and access — infrastructure a client cannot inspect is a dependency rather than a service.
It depends entirely on your load profile, and it is a question of when rather than whether. Shared environments are economical and perfectly adequate at small scale. The problem is that the ceiling arrives with growth, and the migration is far less disruptive if planned than if forced by an outage.
Monitoring and alerting, patching and version management, capacity review against growth, incident response, and continuous tuning as the platform changes. The point is that infrastructure is not a state you reach but a thing you maintain — most of the value in this practice is in the management rather than the initial build.
By testing restoration rather than the backup. An untested backup is a belief, not a control. We deliver backups that have been restored from, with a recovery procedure that has been rehearsed and a documented recovery time.
Describe what is happening rather than what you think the cause is. If we are not the right people for it, we will say so.