logo

Cloud platforms

Cloud platforms built on open foundations, so you are never locked in

We design and run your platform on AWS, Azure, Google Cloud, Hetzner or OVHcloud. We build it with Terraform, Kubernetes and open-source components, so you can move or mix providers later.

Review my cloud setup Cloud exit

We reply within one business day.

5 providers

AWS, Azure, GCP, Hetzner, OVHcloud

All as code

Terraform / OpenTofu

Fixed price

scope agreed in writing before work starts

One codebase, any provider

One codebase, any provider

Works with

AWS

Microsoft Azure

Google Cloud

Hetzner

OVHcloud

Cloudflare

Terraform

Kubernetes

In short

We design, build and operate cloud platforms on AWS, Microsoft Azure, Google Cloud, Hetzner and OVHcloud. Everything is defined in Terraform or OpenTofu; workloads run on Kubernetes, VMs or managed services where they genuinely save effort; and data, monitoring and identity use open standards. That keeps costs visible and leaves you free to move workloads between providers, or out of the cloud, later.

Services

What we do in cloud platforms

Architecture and landing zones

Accounts or subscriptions, networks, identity and guardrails set up for growth and audits.

Cloud operations

Monitoring, patching, backups and on-call for your platform.

Proof

Related work we delivered

Real projects. We name clients only with their permission.

Azure & Microsoft 365 securityAI startup (name withheld)

AI startup onboarded to Azure and Microsoft 365, secure and audit-ready

Challenge

A growing AI company needed a professional Microsoft environment and had to answer enterprise customers' security questionnaires.

What we did

We built the environment entirely in Terraform: Entra ID with 15 Conditional Access policies, groups and roles; Intune device compliance aligned with Cyber Essentials and BitLocker key backup; Microsoft Defender for Cloud; Microsoft Sentinel with analytics rules and log retention; Key Vault, segmented networks and AKS; plus an InfoSec implementation checklist.

Result

A documented, reproducible security baseline the company can show to customers and auditors, and change safely through code review.

TerraformEntra IDIntuneDefenderSentinelAKS
Azure & Microsoft 365 secure onboarding →

Examples

Typical cloud platforms projects

One accountOrg + accountsGuardrailsAudit-ready

Landing zone for a growing startup

Separate environments, central logging, least-privilege access and guardrails before the first enterprise customer asks.

Single regionTerraform modulesSecond siteFailover tested

Second region or provider

The same platform rebuilt in a second region or on Hetzner for resilience or cost.

CloudVPN / private linkOn-premOne operating model

Hybrid cloud

Cloud and on-premises managed with the same tools, identity and monitoring.

Unknown accountInventoryImport to codeDocumented

Taking over a legacy account

An inherited account mapped, imported into Terraform and documented resource by resource.

How to start

How to start with cloud platforms

Architecture review

Fixed priceagreed after a short call
  • Security, cost and reliability review

  • Lock-in assessment

  • Prioritised roadmap

  • About 1 week

Book the review
MOST POPULAR

Platform build

Fixed priceper phase, scoped in writing
  • Landing zone and networks

  • Terraform modules + pipeline

  • Monitoring and backups

  • Handover

Plan the build

Cloud operations

Monthly plansized to your needs
  • Monitoring and on-call

  • Patching and backups

  • Monthly cost review

  • Response times in writing

Ask about operations

Process

Getting started with cloud platforms

1

Review

Architecture, costs, security and how hard it would be to move.

2

Build

Landing zone and workloads from code, in phases.

3

Operate

Run it with your team or ours, with monthly cost reviews.

Why it matters

Why cloud platforms drift into cost and lock-in

Most cloud setups start with a few clicks in a console. Two years later nobody knows what runs where, what it costs, or how to rebuild it.

Click-built environments

Resources created by hand cannot be reviewed, copied or rebuilt reliably. We put them in Terraform or OpenTofu.

Costs nobody owns

Without tagging, budgets and reviews, idle and oversized resources keep adding to the bill.

Managed-service lock-in

Every proprietary service you adopt makes leaving harder. We use open building blocks where they work just as well.

Security gaps

Broad IAM roles, public buckets and missing logs are common in fast-grown accounts.

No disaster plan

Backups exist but restores and region failures have never been tested.

Know-how in one head

When the person who built it leaves, the platform becomes a risk. Code and documentation fix that.

When you may not need us

An honest note before you book.

  • A single small app on a PaaS that already works well.

  • An in-house platform team with infrastructure as code and reviews in place.

  • A cloud you are about to leave: see cloud exit instead.

Before and after

A click-built cloud vs a platform built by us

Area
Click-built account
Platform built as code
Rebuilding
Click-built account: Weeks of guesswork after an incident.
Platform built as code: Rebuild from code in hours, tested regularly.
Changes
Click-built account: Made in the console, untracked.
Platform built as code: Reviewed in Git and applied by a pipeline.
Cost control
Click-built account: Bill reviewed at quarter end.
Platform built as code: Tags, budgets and monthly reviews.
Portability
Click-built account: Tied to one provider's services.
Platform built as code: Open building blocks; moving providers stays possible.
Audit evidence
Click-built account: Screenshots collected by hand.
Platform built as code: Configuration and history in code.

FAQ

Cloud platforms FAQ

Straight answers. Ask us anything else on a call.

Which cloud should we choose?

It depends on your customers, data location, existing licences and skills. Microsoft-heavy companies often fit Azure; many startups start on AWS or GCP; steady EU workloads are often far cheaper on Hetzner or OVHcloud. We compare the options for your case.

Do you resell cloud?

No. You contract the provider directly and we charge only for our work, so our advice is not tied to a margin.

Do you work with Azure too?

Yes. Azure, AWS and Google Cloud, plus Hetzner and OVHcloud. For Microsoft-heavy companies see our Azure and Microsoft 365 secure onboarding.

Can you take over operations of our existing cloud?

Yes, after an onboarding review: we document what exists, fix the risky parts first and then run it with monitoring and on-call.

Related

Related services

Cloud exit

Next step

Talk to an engineer about cloud platforms

Send a few details, and pick up to 3 times if you would like a call. We reply within one business day.

You talk to the expert who would do the work

Written scope and price after the call

No obligation

info@opensource.consulting
+1 514 577 8599

OpenSource Consulting

Open source solutions integrator: we design, build, integrate and support Odoo, n8n, Zabbix, Grafana, Kubernetes and databases.

info@opensource.consulting

+1 514 577 8599

Canada · Netherlands · UAE

Services

© 2026 OpenSource Consulting. All rights reserved. · Privacy · Cookies · Terms

Our brands: elasticsearch.expert · zd-inc.net · opsfinitive.io

Review my cloud setup