Skip to main content
Version: 2.7

Deployment Options

Olympe has four modes of operations:


This is the free version of Olympe. You don't have to setup anything: just open the Community and register for free.

Olympe Cloud

A dedicated instance running as SaaS and operated by Olympe. Please contact us for more information about how to setup a fully managed Olympe instance.


The hybrid approach is Olympe Cloud with additional back-ends running elsewhere: on the edge, on premise or in a private cloud.

On Premise / Private Cloud

A full installation on your own infrastructure or a cloud provider of your choice. The best and easy way to install an on premise version of Olympe is by using Kubernetes and our Helm Chart.

For more information, please check the related documentation


The capabilities of the different options are as follows. The Hybrid option is omitted as it is really a mix of Olympe Cloud and On Premise: everything running within Olympe Cloud is treated according to Olympe Cloud rules, while the components running on your infrastructure are subject to your own guidelines and best practices, as per On Premise below.

CommunityOlympe CloudOn Premise / Private Cloud
Custom domain nameN/AAvailableAvailable
LoggingN/AAvailableManage logs using your existing tooling and according to your current best practices.
MonitoringN/AAvailableMonitor Olympe components using your existing monitoring tooling and best practices.
CI/CD PipelinesN/AAvailableImplement deployment pipelines within your existing CI/CD infrastructure.
Code repositoryN/AAvailable. Builds are triggered from the Olympe git repository. Integrations with your repositories are possible.Use your own repositories.
ConfigurationN/AManaged within a repository (GitOps)Manage configurations in line with your current best practices.
Secrets managementN/AAvailableUse your existing secret management infrastructure.
Platform upgradesN/AAvailableCan be supported by Olympe.
Artefact registry (NPM and Docker)N/AAvailable. Hybrid setups are possible.You provide artefacts registry (if relevant).

Migrating From One Mode To Another

From Community to Olympe Cloud and Hybrid

When moving from Community to Olympe Cloud, the following steps must be taken in consideration:

  • Consider adding SSO (SAML or OAuth) for user authentication
  • Projects initialized in the community must be imported into your dedicated environment
  • For code to be deployed on the Olympe Cloud, it must be available from the Olympe CI/CD. The simplest mechanism is to implement a replication between your git repository to the Olympe git repository.
  • The configuration of back-ends must be updated to point to the dedicated instance instead of the community. Also back-ends must be authenticated.

From Olympe Cloud / Hybrid to On Premise

On premise and private cloud deployments are typically performed by deploying Docker containers. These can be run both as a docker-compose for simpler scenarios, or more generally onto Kubernetes or OpenShift. Olympe provides a Helm chart for that purpose.