Documentation

Cacheify docs

Cacheify hosts isolated Redis-compatible databases. You keep your data behind scoped API keys, and the platform enforces permissions, quotas and expiry before a command ever runs.

One connection string RESP gateway Scoped keys Mandatory TTL

Connect your app

One credential, one line. Point any native Redis client — redis-cli, ioredis, redis-py, Jedis, Lettuce, Spring RedisTemplate — at:

Connection string — any native Redis client

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

Behind the scenes the gateway verifies the key, enforces the same command surface and quotas as the dashboard Console, and stamps every key into your database's sealed namespace. If you build tooling that prefers JSON over HTTPS, an advanced HTTP reference exists — but it is never required: the Redis string above is the full integration.

The guides

Quick startFrom sign-up to a first successful request in four steps.Redis gatewayConnect native Redis clients over the RESP protocol.HTTP data plane (advanced)Advanced: the JSON-over-HTTPS API behind the gateway.ArchitectureThe request path, tenant isolation and operator modes.TTL policyMandatory expiry on every key, by design.ErrorsStatus codes, error codes and how to retry safely.FAQShort answers to the questions we hear most.

Reading it with agents or tooling

For code assistants and automation, point tools at the machine-readable surfaces instead of these pages: llms.txt for the short index and openapi.json for the full OpenAPI 3.1 contract.

llms.txt index OpenAPI 3.1 spec