AWS, GCP or Azure for a Greek startup?

The right answer for most Greek teams isn't the one trending on Hacker News. It's the one that bills you in EUR, runs near Athens, and matches the cloud your hires already know.

The question lands on our desk every few weeks. A founder is starting something new in Athens or Thessaloniki and needs to pick a cloud before they've written a line of business logic. The Twitter discourse is unhelpful. Vendor sales decks are worse. Here's the honest read from someone who's deployed on all three from Greece.

The TL;DR

Default to AWS. Best documentation, deepest service catalog, the cloud most of your future hires already know. Pick this unless you have a specific reason not to.
Pick GCP if your product is data-heavy or AI-heavy. BigQuery, Vertex AI, and the data tooling are a generation ahead. Networking is also better by default.
Pick Azure if you're selling into Greek public sector, banking, or are on a Microsoft EA. Otherwise the developer experience drags.

Latency from Athens — what's actually close

None of the three has had a full production region in Athens for long. From an Athens broadband connection, you're looking at roughly:

Provider   Closest region(s)                       Approx RTT
─────────────────────────────────────────────────────────────
AWS        eu-south-1 (Milan)                      ~25–35 ms
           eu-south-2 (Spain)                      ~50–65 ms
           eu-central-1 (Frankfurt)                ~45–55 ms
           Athens Local Zone (limited services)    ~5–10 ms

GCP        europe-west8 (Milan)                    ~25–35 ms
           europe-west3 (Frankfurt)                ~45–55 ms

Azure      Italy North (Milan)                     ~25–35 ms
           Greece Central (Athens, when available) ~5–10 ms
           Germany West Central (Frankfurt)        ~45–55 ms

Real numbers vary with your ISP and the destination AZ. Run cloudping.co from your office before you commit. For most B2B SaaS, anything under 60ms is invisible to users — don't optimize for region without measuring.

EUR billing

All three will quote in USD if you let them. All three will bill in EUR if you set up the account correctly.

AWS: select EUR as preferred currency in account settings. The invoice converts at AWS's monthly rate; the conversion is mediocre but acceptable. Greek VAT (24%) is applied automatically once you add a valid VAT number.
GCP: EUR billing is the default for accounts created with a Greek billing address. Cleaner than AWS in our experience.
Azure: EUR by default for Greek tenants. Microsoft has the most predictable monthly conversion rate of the three.

Add your VAT number on day one. Nobody enjoys explaining to an accountant why six months of invoices need to be re-issued.

GDPR posture

All three offer GDPR-compliant configurations. None of them ship that way out of the box. The question isn't "is it GDPR-friendly" — it's "how easy is it to misconfigure". A few things to know:

Region pinning is on you. S3 buckets, Cloud Storage buckets, and Azure Blob containers can be created in any region. Use organization policies / service control policies to refuse resource creation outside EU regions. Don't rely on developers to remember.
Cross-region replication is a footgun. All three default to single-region; some managed services (Cognito, Firebase, certain Azure AD components) have global control planes. If a service is "global", assume it processes metadata in the US until proven otherwise.
Sub-processors matter. Datadog, Auth0, SendGrid — every SaaS you bolt on is a separate GDPR question. Cloud choice doesn't fix this.

Hiring reality

From the Athens market we work in, ranking the three by how many senior engineers we meet who can hit the ground running:

AWS — by a wide margin. Most seniors have shipped on it.
Azure — common in enterprise, fintech, and public-sector adjacent roles.
GCP — concentrated around data and ML teams, fewer overall.

If your second hire needs to be productive in week one, AWS minimises the onboarding tax. This is the strongest argument for AWS that nobody puts in a sales deck.

Where each one actually wins

AWS wins for

General-purpose web/SaaS, microservices, APIs.
Anywhere you need a long-tail service — Lambda, Step Functions, DynamoDB, Kinesis — without writing it yourself.
Teams that want hire-tomorrow-able skills.

GCP wins for

Anything analytics-heavy. BigQuery is the real reason GCP exists for many teams.
Kubernetes-native shops. GKE is genuinely the best managed Kubernetes.
ML/AI workloads where Vertex and TPUs are first-class.
Greenfield products with clean networking requirements — VPC design is years ahead of AWS.

Azure wins for

Organizations already on Microsoft 365 / Entra ID / Dynamics — identity integration is unbeatable.
Public-sector tenders that effectively require Azure Greece Central residency.
Windows-first stacks (.NET, SQL Server). The toolchain is mature.

What we'd actually pick, by stage

Pre-seed, MVP            →  AWS or GCP, free tier, single region (eu-west-1 or europe-west8)
Seed, first 10 customers →  AWS for breadth, GCP if data is the product
Series A, scaling team   →  Whichever your CTO has scars from. Stay there.
Selling B2G in Greece    →  Azure, with Greece Central residency in writing

One thing not to do. Don't go multi-cloud "for resilience" before you have a working single-cloud setup that's been on-call for six months. Multi-cloud is a tax you pay every day for an outage you might never have.

We help Greek and EU teams pick, set up and operate cloud infrastructure on all three. Tell us where you're stuck.