Our mission: we make developers’ life easier

If you are here, it means you want to know what makes us wake up every morning at Go2Scale. We are going to make it short!

Our mission is written in a few words: we make developers life easier. Nothing less, nothing more.

And it is useless to complicate things! Our goal is to provide to all DevOps and to increase the potential of this methodology, that’s it.

The 4 pillars of our success

An Agile and DevOps personalized support

Everything begins with a complete support on DevOps and Agile methodologies. A solid basics, reinforced with powerful tools, will allow all development’s team to reach their goals while emphasizing their internal abilities.

Powerful tools

Speaking of tools, Go2Scale develops its own platform: R2Devops. This hub was initially thought to boost the support to our clients, and as proven to be a real success. Who wouldn’t like to create a CI/CD pipeline thanks to plug and play jobs in only 3 clicks !

A treasure of community

No mystery here, we develop this platform for and with our community. Many contributors take part in R2Devops, publishing and maintaining jobs, which makes all R2Devops’ power!

Long live the open source

Our solution is open source: anyone can access to the source code. This way, we hope to inspire developers to create community projects that will simplify the life of many others!

Go2scale’s values

Go2Scale’s philosophy is centered around 4 key values:

Transparency for our user, our community and also in our team! From transparency comes trust. It’s the reason everything is possible for Go2Scale!

Utilisateur au cœur de l'expérience| valeur Go2Scale

The user is at the core of our priorities : this is why we rely on our community to develop a product that answers the developers real needs.

Alone you go faster, but together we go further away! We think long term: we rely on a team of passionate, to share and debate on all our ideas.

Finally, the cornerstone of our engagement: make development processes smart, in order to always optimize your performances.

Meet the team

The cream of the crop, the motor of Go2Scale: a team that give 200% to bring your projects to life!

Alexandre

DevOps

Mohamed

DevOps

Thibaud

DevOps

Sandra

Marketing & communication

Thomas

CTO

Aurélien

CEO

Alexandre

DevOps

Mohamed

DevOps

Thibaud

DevOps

Sandra

Market’ & comm

Thomas

CTO

Aurélien

CEO



You want to join Go2Scale's adventure?

You want to join a team where it’s nice to live and move some line (of code)?

Send an “Hello world” at [email protected]

Cookie	Duration	Description
CJDofTuXBW	1 d
cookielawinfo-checkbox-analytics	11 months	This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional	11 months	The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary	11 months	This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others	11 months	This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance	11 months	This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
IdsHDWg	1 d
JNSyKUXW_ngQD	1 d
pll_language	1 y
viewed_cookie_policy	11 months	The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.

Cookie	Duration	Description
_hjAbsoluteSessionInProgress	30 min	This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie.
_hjCachedUserAttributes	session	This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. Collected attributes will only be saved to Hotjar servers if the user interacts with a Hotjar Feedback tool, but the cookie will be used regardless of whether a Feedback tool is present.
_hjClosedSurveyInvites	365 d	Hotjar cookie that is set once a user interacts with an External Link Survey invitation modal. It is used to ensure that the same invite does not reappear if it has already been shown.
_hjDonePolls	365 d	Hotjar cookie that is set once a user completes a survey using the On-site Survey widget. It is used to ensure that the same survey does not reappear if it has already been filled in.
_hjFirstSeen	session	This is set to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions.
_hjid	365 d	Hotjar cookie that is set when the customer first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.
_hjIncludedInPageviewSample	30 min	This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's pageview limit.
_hjIncludedInSessionSample	30 min	This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's daily session limit.
_hjLocalStorageTest	under 100ms	This cookie is used to check if the Hotjar Tracking Script can use local storage. If it can, a value of 1 is set in this cookie. The data stored in_hjLocalStorageTest has no expiration time, but it is deleted almost immediately after it is created.
_hjMinimizedPolls	365 d	Hotjar cookie that is set once a user minimizes an On-site Survey widget. It is used to ensure that the widget stays minimized when the user navigates through your site.
_hjRecordingEnabled	session	This is added when a Recording starts and is read when the recording module is initialized to see if the user is already in a recording in a particular session.
_hjRecordingLastActivity	session	This should be found in Session storage (as opposed to cookies). This gets updated when a user recording starts and when data is sent through the WebSocket (the user performs an action that Hotjar records).
_hjSessionRejected	session	If present, this cookie will be set to '1' for the duration of a user's session, if Hotjar rejected the session from connecting to our WebSocket due to server overload. This cookie is only applied in extremely rare situations to prevent severe performance issues.
_hjSessionResumed	session	A cookie that is set when a session/recording is reconnected to Hotjar servers after a break in connection.
_hjSessionTooLarge	session	Causes Hotjar to stop collecting data if a session becomes too large. This is determined automatically by a signal from the WebSocket server if the session size exceeds the limit.
_hjShownFeedbackMessage	365 d	Hotjar cookie that is set when a user minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if the user navigates to another page where it is set to show.
_hjTLDTest	session	When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed.
_hjUserAttributesHash	session	User Attributes sent through the Hotjar Identify API are cached for the duration of the session in order to know when an attribute has changed and needs to be updated.
_hjViewportId	session	This stores information about the user viewport such as size and dimensions.