Kestrel Cloud
Predictable performance, plain pricing.
Founded 2011 Paris, France +1 (555) 014-8582
Independent profile of Kestrel Cloud, a 2011-founded cloud provider from Paris, France. Compare products, data centers, certifications, deals and verified customer reviews on CloudRadar.
Popularity Rank
#6
Certifications
4
Products
11
DC Regions
8
Positive Reviews
12 approved
Company Profile
- Legal name
- Kestrel Cloud Ltd
- Founded
- Jan 24, 2011
- Registered capital
- $120M
- License / ICP No.
- —
- Listing
- —
Funding History
-
Jun 27, 2012
Seed $4.5M
Led by Trellis Growth Partners
-
Jan 19, 2014
Series D $160M
Led by Marshfield Capital
-
Nov 14, 2017
Series C $90M
Led by Pinegate Ventures
-
Nov 14, 2019
Series B $45M
Led by Marshfield Capital
Certifications
- C5
- CSA STAR
- GDPR-Ready
- HIPAA-Ready
Data Centers
Domestic
- Amsterdam · Amsterdam
- Dublin · Dublin
- Frankfurt · Frankfurt am Main
International
- Ashburn · Ashburn, Virginia
- Singapore · Singapore
- Sydney · Sydney
- Tokyo · Tokyo
- Toronto · Toronto
About Kestrel Cloud
Kestrel Cloud opened its first data hall in Paris in 2011 and has grown into a full cloud platform covering compute, storage, networking, and managed data services. The company is known for conservative engineering choices, support threads that actually get resolved, and invoices a CFO can read without a translator.
Every service on the platform — virtual machines, object storage, managed databases, and private networking — is exposed through one API surface, one console, and one bill. Capacity is pre-provisioned per region, so new instances launch in seconds without waiting on hardware, and standard images are rebuilt weekly with security patches applied automatically.
The customer base skews toward engineering-led companies: fintech platforms with strict audit requirements, media studios moving render farms to the cloud, and research labs with bursty compute needs. The company is board-governed with institutional investors and reports utilization targets twice a year. Every customer reads the same status page and files tickets in the same queue.