Documentation

Quick start

The dashboard does the setup — account, database, key. Your project receives exactly one line, REDIS_URL, and from there any native Redis client connects as if nothing changed.

Four steps, all in the dashboard

01
Create your account in the dashboard
Open the dashboard, choose Sign up, then type the 6-digit code we email you. Verification is what unlocks databases and keys — no CLI, no forms to hand-write.
02
Create a database from Databases
Click New database and give it a name. Five isolated databases are included free; each is its own keyspace.
03
Mint its active key on the database page
Open the database and create its key — choose read-only or read-write. The plaintext rk_… token is shown exactly once: paste it into the connection string now (step 04).
04
Put the connection string in your project
Copy the one-line URL below into the .env of the service that will talk to Cacheify as REDIS_URL, and connect — your Redis client needs nothing else.

The one env value your project needs

Create a .env file in the project that will use Cacheify and copy this line — only the key slot changes. No SDK ships, nothing to configure beyond the Redis driver you likely already use.

.env — the whole integration in one value (server-side only)

# .env — add this line to YOUR project (server-side only, never commit it)
# One value is the whole integration: database + key travel together in one URL.
REDIS_URL=redis://:<your-key>@node18.botkeep.cloud:61350/0

REDIS_URL — the full connection: gateway host, port and database in one URL, with your active key as the password slot.
Every client that speaks Redis loads it straight in: redis-cli -u, ioredis, redis-py from_url, Jedis/Lettuce URI config, Spring RedisTemplate.
Server-side only: this string is database-wide access within the key's permission — never ship it to a browser, never commit it, never log it.

The connection string, one line

Connection string — any native Redis client

redis://:<your-key>@node18.botkeep.cloud:61350/0

Optional sanity check once REDIS_URL is in place:

Optional sanity check (PING, SET, GET)

# sanity check with any Redis client you already have (optional)
redis-cli -u "$REDIS_URL" PING        # -> PONG
redis-cli -u "$REDIS_URL" SET greeting "hello world"
redis-cli -u "$REDIS_URL" GET greeting  # -> "hello world"

What to read next

The Redis gateway guide covers AUTH semantics, the supported verb surface and TLS. For quota behavior, isolation and the operator modes behind that URL, read the architecture page.

One platform rule worth knowing before you write code: every key expires — a plain SET gets a 24-hour TTL unless you ask for something specific. Details in the TTL policy.