Version: Next

Features

Any data technology, one platform

Provider-based. Each technology is added by installing a Provider. Providers are released independently of the core, so a technology can gain features without an OpenEverest release.
A growing catalog. The Plugin Hub lists the available providers and plugins, with their maturity and install command.
Your Kubernetes, your data. OpenEverest runs on any conformant Kubernetes cluster, in any cloud or on-premises. There is no vendor lock-in and no data leaves your infrastructure.

One-click creation. Pick a provider, a namespace and a name; the provider fills in sensible defaults. Expand Configure more options to control every setting.
Forms generated by the provider. The creation and edit forms come from the provider's UI schema, so each technology exposes the options that make sense for it — topology, version, resources, storage, proxies, engine configuration and more.
Topologies. A provider can offer several deployment architectures, for example a MongoDB replica set or sharded cluster, and you choose one when you create the instance.
Instance presets. Administrators can publish presets that pre-fill the creation form for common sizes and environments.
Pod placement. Edit affinity rules per component. Providers spread data-bearing members across nodes by default.

Edit and scale resources, replicas and storage after creation, as far as the provider allows.
Delete instances and choose whether to keep their backups.
Controlled maintenance. Choose which disruptive changes, such as rolling restarts, are applied automatically and approve the rest.
Clear status. Instances report why pods are not running — for example when they cannot be scheduled or are stuck in CrashLoopBackOff — in the UI and in the Instance status.

S3-compatible backup storage shared by all instances in a namespace.
On-demand and scheduled backups with count-based or time-based retention.
Point-in-time recovery where the provider supports it.
Restore a backup into the same instance, or create a new instance from a backup.

Built-in users and single sign-on with any OpenID Connect provider.
Role-based access control down to a single namespace or instance, including a separate permission for reading credentials.
TLS for the UI and API, with cert-manager integration.

Kubernetes-native API. Every object is a custom resource, so you can manage instances with kubectl, Helm or GitOps tools, as well as with the REST API.
Generic plugins add new pages, sidebar entries and backend APIs to OpenEverest — see Generic plugins.
Bring your own monitoring. Monitoring extensions connect instances to the monitoring system you already run, such as PMM or Prometheus. OpenEverest installs no monitoring stack of its own. See Monitoring.