DGL.dev

Services

Cloud Infrastructure and Deployment

Infrastructure appropriate for the size of the business, rather than complexity for its own sake.

All services

Software needs somewhere reliable to run. The part that decides whether an application survives its first year is usually not the code.

We build and maintain production environments, deployment pipelines, databases, monitoring, backups, CDN and edge infrastructure, and cloud services.

We focus on infrastructure that is reliable and appropriate for the size of the business rather than adding complexity for its own sake. Most companies do not need the architecture of a company a hundred times their size, and paying for it slows everything down.

Problems this solves

You may recognise some of these.

  • Deploying is manual, risky, and only one person will do it
  • There is no staging environment, so production is the test
  • The cloud bill grows and nobody can attribute it
  • Backups exist and have never been restored
  • An outage is discovered by a customer

What we do

The work itself

Production environments

Staging and production that actually resemble each other.

Deployment pipelines

Automated, repeatable releases with a rollback that has been tested.

Databases and backups

Including restoring from one, which is the only way to know it works.

Monitoring and alerting

Finding out before your customers do.

CDN and edge

Delivery and caching, which is often the cheapest performance available.

Process

How an engagement runs

  1. Establish what exists

    Where it runs, what it costs, and who can change it.

  2. Make deployment boring

    Repeatable releases remove a whole class of incident.

  3. Add visibility

    Monitoring and alerting before optimisation, because you cannot fix what you cannot see.

  4. Right size it

    Match the infrastructure to actual load and actual budget.

  5. Document the operational reality

    So the next person can run it.

Technology

What we typically build this on

The technology is chosen around the project. The business problem comes first.

Questions

Things people ask before starting

Do we need Kubernetes?
Probably not. Most businesses are better served by simpler infrastructure they can reason about. Complexity has an ongoing cost that is easy to underestimate and hard to reverse.
Can you reduce our cloud bill?
Often, though the first step is attribution: knowing what each part costs. Savings usually come from right sizing and removing things nobody remembered were running.
Can you take over infrastructure someone else set up?
Yes. That normally starts with documenting what exists, because undocumented infrastructure is the real risk rather than the technology choice.

Tell us what you are trying to build

Tell us about the business, the problem, what you have today, and what you want to accomplish. If we are not the right team, we will tell you.

Start a Project