Introducing the North America Region

We are finally landing in America! As most of our customers are outside of Europe, our hosting service has made its way to a new continent. Same service, same price, same dashboard and now a regional choice on top.

Our team has been working on this development for a long time. We wanted to improve the user experience for American users, and we are very excited that everything is working out today, just as we wanted.

Why Canada?

We have selected a great partner, Netelligent, to ensure high quality and high availability of your applications. Users throughout Canada, US and Latin America will benefit from an enhanced connectivity and enjoy a better experience of PaaS with Clever Cloud.

Here at Clever Cloud, we care about your data privacy. Our European data-centers suit our security standards and that’s why we chose to partner up with Netelligent in Quebec, Canada.

Simple and Easy Migration

Migrating existing apps to a new location is quite simple. To switch from a location to another, you simply have to change the Zone field in the Information tab of your apps:

Once you're done, if you're using a .cleveraps.io domain name, everything is automatic, otherwise you will have to update your DNS settings to go directly to Montreal without going through Paris.

Note that this quick migration isn't currently supported for php applications, or for applications using File-System buckets.

Deploying on both continents

For reasons of clarity, we ask you to choose one zone per app. So you need to create two Clever Cloud applications.

Running the same code base on both regions is pretty straightforward:

  • Create a second app in the new region via the dashboard
  • Get the new git push URL and add it to your git config via the following command line:
# Assuming you added a "clever" remote as described in the documentation like this:
# git remote add clever git+ssh://git@push.par.clever-cloud.com/appid1.git

# Set your first specific push URL for Paris on the "clever" remote
$ git remote set-url --push clever git+ssh://git@push.par.clever-cloud.com/appid1.git

# Set your second specific  push URL for montreal on the "clever" remote
$ git remote set-url --add --push clever git+ssh://git@push.mtl.clever-cloud.com/appid2.git

Then your project config file located in .git/config should contain something like this:

[remote "clever"]
  url = git+ssh://git@push.par.clever-cloud.com/appid1.git
  pushUrl = git+ssh://git@push.par.clever-cloud.com/appid1.git
  pushUrl = git+ssh://git@push.mtl.clever-cloud.com/appid2.git

Note that, due to git internal behaviour, you explicitely need to re-add the first remote url (the Paris one) as a pushUrl too, otherwise it would only push to Montreal.

Now, one push will deploy your code both in Paris and Montreal.

Security and Patriot Act

We care about our customers privacy. We have selected this location because it is Patriot Act-free, and Canada has IP laws to protect your data. Privacy is a strong part of our core values at Clever Cloud.

Blog

À lire également

SuperBOL: The COBOL revolution in the Cloud

COBOL, a programming language that is over 60 years old, continues to power a large proportion of the IT systems of the world's major companies, particularly in the financial and insurance sectors.
Features

Clever Cloud welcomes the first startups to the UP Programme

Clever Cloud is proud to announce the arrival of the first five startups selected to join its UP Programme, an initiative dedicated to supporting young technology companies in their growth phase.
Company

A minor update resulted in a cascade of errors: how it went wrong, what we’ve learnt

On Friday, August 2nd, 2024 Clever Cloud’s platform became very unstable, leading to downtime of varying duration and scope, for customers using services on the EU-FR-1 (PAR) region, and remote zones depending on the EU-FR-1 control plane (OVHcloud, Scaleway, and Oracle). Privates and on-premise zones weren’t impacted.
Company Engineering