Skip to main content

Launch a cache with a console: managed Valkey with a browser admin UI, in minutes

· 4 min read
FoundryDB Team
FoundryDB Team
Engineering @ FoundryDB

A cache is the easiest part of your stack to stand up and the hardest part to see into. Valkey starts in seconds, but the moment you want to know what is actually in it you reach for a client, open a TLS connection, and type commands by hand just to confirm a key exists. The fast, ephemeral store that should be the simplest thing you run turns into the one you have the least visibility into.

The Launch a cache with a console stack fixes that in one button. You get a managed Valkey cache with Redis Commander attached: an EU-resident in-memory store plus a browser console to browse keys, inspect values, and run commands, wired and metered, in minutes.

cache-console stack composition & launch
RUNNING Stack wired · web console live
Stack Templatecache-consolelaunch ⇉Valkeycache · :6379Redis CommanderREDIS_* ← cacheserve →Web Consolebrowse keys · commands
Template · launchValkey (cache)Redis Commander (console)wiring (REDIS_* injected)

What you launch​

Pick Launch a cache with a console from the catalog and the platform stands up two things and connects them:

  • A managed Valkey cache. A Valkey 8.1 service: a fast in-memory key-value store for caches, session stores, rate limiters, and queues. Speaks the Redis protocol, so any standard client connects to it directly.
  • Redis Commander, attached to it. A web admin UI for Redis and Valkey. It lists every key, lets you drill into values and TTLs, and gives you a command console, all in the browser.

Redis Commander is stateless: it keeps no data of its own and reads everything live from the cache. By the time the stack reaches Running there is nothing left to configure. You open the URL, sign in, and you are looking at your cache.

A cache you can actually see into​

The console connects to Valkey through discrete connection variables that the engine injects during launch, so there is no host string to paste and no special character in a password that can break the connection. The console talks to the cache over the platform's private network, never the open internet.

Once you are in, the cache is no longer a black box. Set a key from the command console:

SET visits 1
INCR visits
INCR visits
GET visits
OK
(integer) 2
(integer) 3
"3"

That key now shows up in the key browser, value and TTL and all. And it is the same cache your application talks to over the wire. Connect any Redis or Valkey client over TLS on port 6380 and read back exactly what you set in the browser:

redis-cli -h <cache-host> -p 6380 --tls \
  --user <cache-user> --pass <cache-password> \
  GET visits

One cache, two ways in: a browser console for humans and the Redis protocol for your app. No proprietary store, no lock-in.

Trust, built into the launch​

Like every stack, the cache-console launch carries the platform guarantees in the flow itself.

A hard cost preview before you launch. You see exactly what the stack costs, the cache plus the console, broken down per resource, before anything is provisioned. You accept a number, then the launch runs.

Atomic rollback. A stack is two resources coming up together. If either step fails, the whole launch rolls back cleanly. You end up with the finished cache and console or with nothing, never with an orphaned service quietly costing you money.

EU data residency. The Valkey cache, the Redis Commander console, and the traffic between them all stay within the platform's European footprint. Residency is where the platform runs, not a setting you remember to flip.

Launch one​

# 1. Preview the cost
curl -X POST https://api.foundrydb.com/stacks/preview \
  -H "Authorization: Bearer $FOUNDRYDB_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"template_name": "cache-console"}'

# 2. Accept the previewed total and launch
curl -X POST https://api.foundrydb.com/stacks \
  -H "Authorization: Bearer $FOUNDRYDB_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"name": "my-cache", "template_name": "cache-console", "accepted_monthly_cost": 39.00}'

Poll the stack until it is Running, open the endpoint_url, sign in, and you are browsing your cache. Or do the whole thing from the Stacks catalog in the console with one click.

For the full walkthrough, including signing in to the console, setting and reading keys, connecting a client over TLS, and tearing the stack down atomically, read the Launch a cache with a console tutorial.

Stop flying blind on your cache. Launch a managed Valkey with a browser console attached, in Europe, today.