Each store is a named container for key-value pairs. After creating a store, link it to a FastEdge application before the application can access its data — linking instructions are in [Managing applications](/fastedge/manage-apps#edge-storage).
Data is replicated across Gcore's edge network, so reads are served from a local copy at the edge location handling each request.
## Create a storeCreating a store uses a two-step wizard. The first step sets the store name; the second step adds key-value pairs before saving.
To start, open the [Gcore Customer Portal](https://portal.gcore.com/accounts/reports/dashboard), navigate to **FastEdge**, and select **Edge Storage** in the sidebar.
1. Click **Add Edge Storage** in the top-right corner.
2. Enter a name and optionally a description.
3. Click **Create Edge Storage** to proceed to the second step.
4. In the second step, add key-value pairs using the **Insert item** button, or skip this step — pairs can be added later by opening the store from the list.
5. Click **Save Edge Storage**.
The store appears in the Edge Storage list.
## Insert key-value pairsKey-value pairs are added through the **Insert item** panel inside the store view. Pairs can be added during the creation wizard (step 2) or at any time by clicking the store name in the Edge Storage list to open it.
### Add a pair manuallyClick **Insert item** and select **KV pair**. In the panel that opens, enter the key and value. Click **+ Add value** to add another row. Click **Save** to apply the changes.
Keys are limited to 256 bytes.
### Upload a value from a file
To load a value from a file instead of typing it, click the upload icon in the value row. Text and binary files are supported — images, fonts, and similar assets. The maximum file size is 1 MB. After uploading, the portal displays a hash of the file content rather than the original filename.
### Set an expiration date
To assign an expiration to a value, click the expiry icon in the value row and select a date and time. After that point, the value stops being returned to applications. It may remain visible in the portal briefly after expiration.
## Edit a key-value pair
Once pairs are in a store, individual values can be updated at any time. Clicking a store name in the Edge Storage list opens the **Edit Edge Storage** page where all pairs are listed. To edit a pair, click the three-dot icon next to it, select **Edit**, update the value or expiration date, then click **Save**.
To remove outdated or incorrect data, pairs can be deleted individually or in bulk. Open the store by clicking its name in the Edge Storage list to access both options.
To delete a single pair, click the three-dot icon next to it, select **Delete**, and confirm.
To delete multiple pairs, select the checkboxes in the first column of the table, click **Group actions**, and select **Delete all**.
## BYOD: Bring Your Own Database
BYOD connects a FastEdge store to an external key-value database instead of Gcore's hosted storage. Applications access a BYOD store through the same [JavaScript SDK](https://g-core.github.io/FastEdge-sdk-js/reference/fastedge/kv/open/) or [Rust SDK](https://docs.rs/fastedge/latest/fastedge/key_value/struct.Store.html) as a regular store — no code changes required.
Any store implementing the Redis protocol is supported: Redis, [Apache Kvrocks](https://kvrocks.apache.org/), and other Redis-compatible key-value stores.
The external store must be publicly accessible. Gcore's edge nodes connect to it over the network on each request.
## Hosted Edge Storage vs BYODWith hosted Edge Storage, data lives at every edge location globally and reads are served locally — latency is typically in the single-digit milliseconds. With BYOD, each read is a live query to the external database, so response time depends on the network distance between the edge location and the database host.
BYOD is a practical choice for development, testing, or workloads where read speed is not critical. For latency-sensitive production workloads, hosted Edge Storage is recommended.
Supported URL schemes:
* `redis://` — standard Redis protocol * `rediss://` — Redis protocol over TLSURL format: `redis://:password@host:port/db-index` or `redis://username:password@host:port/db-index`
## Create a BYOD storeFollow steps 1–3 from [Create a store](#create-a-store), then:
4. Select the **BYOD: Bring Your Own Database** checkbox. Two additional fields appear: * **URL** — the connection URL for the Redis-compatible store. For example: `redis://:mypassword@redis.example.com:6379/0` * **Prefix** — a string prepended to every key when FastEdge reads or writes the store. For example, with prefix `app:prod:`, a read for key `greeting` retrieves `app:prod:greeting` from the external database. Use a prefix to namespace application data within a shared instance. Leave blank if no namespacing is needed.
5. Click **Create Edge Storage** to validate the connection and create the store.
After creation, link the BYOD store to a FastEdge application using the same process as a regular store — instructions are in [Managing applications](/fastedge/manage-apps#edge-storage). Once linked, the application accesses the BYOD store through the standard SDK API. The prefix is applied transparently and the application code does not need to know whether the store is BYOD or hosted.
Automate KV store management using the [Python SDK](/developer-tools/sdks/python) or [Go SDK](/developer-tools/sdks/go) for store-level operations, while key-value data operations require direct HTTP calls to the FastEdge REST API.
A store must exist before key-value pairs can be written to it. The response includes the store ID used in all subsequent requests.
The API returns the new store ID:
```json theme={null} { "id": 130, "name": "my-store", "comment": "Optional description", "app_count": 0, "size": 0 } ```Save the `id` value — it is required for all data operations.
To create a BYOD store backed by an external Redis-compatible database, add the `byod` object with the connection URL and an optional key prefix:
```bash theme={null} curl -X POST "https://api.gcore.com/fastedge/v1/kv" \ -H "Authorization: APIKey $GCORE_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "name": "my-byod-store", "byod": { "url": "redis://:mypassword@redis.example.com:6379/0", "prefix": "app:prod:" } }' ```Gcore validates the connection at creation time and returns an error if the external store is unreachable. The store type cannot be changed after creation.
## Insert or update key-value pairsUse PUT /fastedge/v1/kv/{store_id}/data to write or overwrite key-value pairs. Each entry in the request array requires an `op` field — use `"add"` to insert or overwrite a key.
The API returns write statistics:
```json theme={null} { "write_count": 2, "del_count": 0, "write_size": 37, "store_size": 37, "revision": 577 } ```To store binary content, set `"encoding": "base64"` and provide the Base64-encoded value instead of plain text. The key length limit is 256 bytes.
## List key-value pairsRetrieve all pairs in a store with GET /fastedge/v1/kv/{store_id}/data. Use the `limit` and `offset` query parameters for pagination.
The API returns:
```json theme={null} { "count": 2, "entries": [ { "key": "color", "datatype": "kv", "payload": { "encoding": "plain", "value": "blue" } }, { "key": "greeting", "datatype": "kv", "payload": { "encoding": "plain", "value": "Hello from FastEdge!" } } ] } ```To retrieve a single key, append the key name to the path: GET /fastedge/v1/kv/{store_id}/data/{key}.
Use the same PUT /fastedge/v1/kv/{store_id}/data endpoint with `"op": "del_key"` to delete one or more keys. Multiple keys can be deleted in a single request.
The API returns:
```json theme={null} { "del_count": 1, "write_count": 0, "write_size": 0, "store_size": 28, "revision": 578 } ``` ## Delete a storeDeleting a store permanently removes it and all its data. This action cannot be undone.
Returns HTTP 204 with no body on success. Returns HTTP 409 if the store is still linked to one or more applications — unlink the store from all applications before deleting.