Isolated databases
Every database is a sealed namespace. Cross-tenant reads return 404, so the platform never confirms that another account’s database exists.
Serverless Redis · Free for every account
Cacheify gives you isolated Redis-compatible databases behind one connection string. Scoped keys, quotas and mandatory expiry are enforced before a command ever runs. Five databases are free.
/api/data/rdb_7f2c/commandawait fetch(url, {
method: "POST",
headers: { authorization: "Bearer rk_..." },
body: JSON.stringify({
command: "SET",
args: ["session:9942", "active", "EX", "3600"]
}),
});{ "success": true, "data": { "result": "OK" } }Works with the stack you already run
How it works
A continuous loop of the real path: the key is verified, the namespace is stamped, the TTL is armed, and the reply comes back through the same route.
SET greeting helloAny HTTP client or Redis driverGateway / HTTPS APIRESP wire or JSON requestKey · permission · quotaBearer rk_ verified; read-only writes refused before executionrh:<tenant>:Your database is a sealed namespaceStored · 24h TTLEvery key expires — even the ones you forgotThe key — the password slot of your connection string — is resolved on the first command.
Read-only writes and over-quota work are refused here, before anything runs.
Keys land inside an isolated namespace; cross-tenant reads return 404.
Writes without EX get the 24-hour default. PERSIST is rejected by design.
> SET session:9942 active EX 3600OKIllustrative preview of the authenticated console.
The console
Create a database, issue its scoped key, browse keys with their remaining TTL and run commands against the same API your application uses. No CLI to install.
Product
Everything that normally needs a platform team — isolation, scoped credentials, quotas and expiry — is part of the request path.
Every database is a sealed namespace. Cross-tenant reads return 404, so the platform never confirms that another account’s database exists.
Exactly one active key per database, read-only or read-write. A write from a read-only key is refused before the command executes.
Work with strings, lists, sets, hashes and sorted sets over JSON. No TCP client, Redis driver or special runtime required.
Every key carries a TTL — 24 hours by default, configurable per write. PERSIST is rejected, so forgotten keys cannot quietly accumulate.
Operators can point the data plane at a real Redis server. Each platform database becomes an isolated, namespaced tenant on that server.
Database, key and value limits are enforced with atomic rollback. Admins can search accounts, adjust quotas and suspend access.
Architecture
Permissions and quotas are checked on every request, before the command reaches an isolated database namespace.
A request-path diagram, not a region map. The deployment exposes a single API origin, whether the data plane runs on the embedded engine or on your own Redis server.
Defaults verified in the product — not marketing estimates.
Trade-offs
Cacheify optimizes for a browser console, the native Redis protocol and strong defaults. Those choices are not free — here is the honest comparison.
| Capability | Cacheify | Self-managed Redis | Typical managed Redis |
|---|---|---|---|
| Start cost | $0 | Server, time and maintenance | Provider billing |
| Connection | One redis:// string | Redis TCP client | Redis TCP client |
| Credentials | Per database · read-only or read-write | ACLs you configure | Provider IAM and network rules |
| Expiry | Enforced on every key | Policy you operate | Optional or provider setting |
| Where data lives | Embedded engine or your Redis server | Your VM | Provider account and region |
| Time to first key | Create a database, issue a key, send a request | Provision, harden and deploy | Account, billing and network setup |
A general comparison of deployment categories, not a specific vendor. Managed Redis offerings vary by provider.
Quick start
No region picker, no network wiring. The dashboard sets everything up, and your application connects like any other Redis client.
Sign up with an email and password, verify the code, then create a database. Five are included from the first minute.
Dashboard: Databases → New databaseCreate an accountOpen the database and create its single active key. Choose read-only or read-write; the plaintext token is shown once.
Dashboard: database page → Create keyRead the quick startAny native Redis client dials the redis:// string with your key as the password. Add an expiry when a key needs to live longer than a day.
redis-cli -u "$REDIS_URL" PINGSee the gateway guideredis-cli -u "redis://:<your-key>@node18.botkeep.cloud:61350/0" PING # -> PONGPricing
One plan with the full platform included. No card, no trial clock and no gateway to the data plane.
0forever
For prototypes, side projects and production services that want strong defaults without another bill.
Already have an account? Sign in
Free for every account
Create a database, issue a scoped key and send a command. No card and no server to run.