Skip to content
OperationalLast ship · 4h agoIn flight · 6 engagementsReply within · 4hSenior partners onlyMMXXVIOperationalLast ship · 4h agoIn flight · 6 engagementsReply within · 4hSenior partners onlyMMXXVIOperationalLast ship · 4h agoIn flight · 6 engagementsReply within · 4hSenior partners onlyMMXXVI
SmartyDevs
← All practicesCloud & Infrastructure
Cloud · 01

Cloud architectures that fit the workload.

AWS, GCP, Azure, Hetzner — chosen for your workload, sized for your scale, priced honestly. The reference architecture you can defend in three years.

Start a conversationExplore all practices
§In this practice
§ 01The problem

The problem we solve

Most cloud architectures are an accumulation of decisions made under time pressure. Resources nobody owns, services that should have been on a different cloud, a NAT gateway that costs more than the application — and no one wants to be the person who refactors it. We design cloud architectures the way they should have been done in the first place, and we migrate you to them without theatre.

§ 02Capabilities

What we ship

  • 01Reference architecture for AWS, GCP, Azure or hybrid
  • 02Multi-account / multi-project landing zones
  • 03Networking: VPC design, peering, transit, private connectivity
  • 04Identity & access: SSO, IAM strategy, least privilege
  • 05Compute: when to use serverless, containers, VMs, managed
  • 06Data: managed databases, object storage, archival
  • 07Edge: CDN, WAF, DNS, anti-DDoS
  • 08Infrastructure-as-code with Terraform or Pulumi
  • 09Security baselines and guardrails
  • 10Cost models with realistic growth projections
§ 03Deliverables

What you receive

  • Architecture document with diagrams, ADRs and trade-offs
  • Terraform / Pulumi modules implementing the architecture
  • Cost model with realistic growth scenarios
  • Migration plan from current to target state
§ 04Stack

Stack we reach for

AWS · GCP · Azure
Hetzner · OVH · DigitalOcean
Cloudflare
Terraform · Pulumi · OpenTofu
Atlantis · Spacelift
Vault · AWS Secrets Manager
§ 05Ideal for

Ideal for

  • → Companies whose cloud setup has accrued without a plan
  • → Teams moving from a single AWS account to a real landing zone
  • → Engineering leaders inheriting an undocumented cloud estate
  • → Founders setting up cloud properly for the first time
§ 06Process

How an engagement runs

  1. 01

    Inventory & audit

    Map what you have. Account structure, services, networking, IAM, costs. Almost always reveals surprises.

  2. 02

    Target architecture

    Designed for your workload and team size. Written down with trade-offs explicit.

  3. 03

    Implementation

    Infrastructure as code, rolled out in phases. Parallel running where it makes sense.

  4. 04

    Handoff

    Documentation, training, runbook. Your team operates it from day one.

§ 07Engagement

How to engage

01

Cloud Audit

1 — 2 weeks

Architecture, cost and security review with prioritized recommendations.

02

Architecture & Migration

6 — 16 weeks

Design target state and execute the migration, phased and de-risked.

03

Cloud Advisory

Ongoing

Retained architectural review for major cloud decisions on a monthly cadence.

§ 08Common questions

Frequently asked.

01AWS, GCP or Azure?

Depends on your workload, team and integrations. We don't have a default. Hetzner for plain compute if cost is the bottleneck. We'll cost-model your options before recommending.

02Serverless or containers?

Serverless for spiky workloads with low operational appetite. Containers for steady workloads where you want control. Often both. We'll match each part of your system to the right shape.

Have a problem worth solving well?

Tell us the outcome you want. We'll tell you what it takes — honestly, within a week, in writing.

Start a conversation