Valkey
Valkey is a high-performance in-memory key-value store suited for caching, transient state, queues, and lightweight messaging patterns.
| Property | Value | Notes |
|---|---|---|
| Provider name | valkey | Use this in landscape provider definitions. |
| Version | v0 | Current schema version exposed by the provider. |
| Category | Key-Value Store | Shown in the managed services catalog. |
| Scope | global | Available at team scope rather than being tied to a single workspace runtime. |
| Team singleton | false | Teams can create multiple Valkey service instances. |
| Pause support | false | This provider does not support pausing. |
Closed testing
This provider is currently in an early testing state and is only available on dedicated installations (closed testing). The provider is still evolving, its schema, plans, and behavior may change in the future.
Schema
Config
| Field | Type | Required on create | Notes |
|---|---|---|---|
version | string | No | Valkey engine version. Default and only allowed value: 9.0. |
Secrets
| Field | Type | Required on create | Notes |
|---|---|---|---|
superuserPassword | string | Yes | Password for the administrative user. |
Details / Output
| Field | Type | Availability | Notes |
|---|---|---|---|
hostname | string | Exposed after provisioning | Internal service hostname. |
port | integer | Exposed after provisioning | Valkey service port. |
ready | boolean | Exposed after provisioning | Indicates whether the instance is ready for connections. |
Plans
The provider exposes multiple plans: Small (id: 0), Medium (id: 1), and Large (id: 2).
Example plan: Small (id: 0).
| Parameter | Type | Default | Minimum | Maximum | Static | Notes |
|---|---|---|---|---|---|---|
storage | integer | 1024 | - | - | No | Priced as storage-mib. |
cpu | number | 5 | - | - | No | Priced as cpu-tenths. |
memory | integer | 512 | - | - | No | Priced as ram-mib. |
Example in a Landscape
schemaVersion: v0.2
run:
cache:
provider:
name: valkey
version: v0
plan:
id: 0
parameters:
storage: 1024
cpu: 5
memory: 512
config:
version: "9.0"
secrets:
superuserPassword: "${{ vault.valkeySuperuserPassword }}"
Within other runtimes, connect to the returned hostname and port with any Redis-compatible or Valkey-native client and authenticate with the stored password.
The same endpoint is reachable from other Codesphere runtimes, including reactives, managed containers, and Virtual Cluster workloads.