In-memory cache.
Sub-millisecond managed cache for sessions, hot data and rate limiting.
A managed, Redis-compatible in-memory cache for sub-millisecond access to hot data — offload your database, hold sessions and back rate limiters, with HA and persistence options.
- Category
- Databases
- Deployment
- Managed → air-gapped
- Governance
- IAM · encryption · audit
Three steps to running.
Redis-compatible, with replicas and optional persistence.
Existing Redis clients, data structures and Lua scripts work unchanged.
Cluster mode shards across nodes for memory and throughput.
In-memory cache, in full.
Drop-in for existing clients, data structures and Lua scripts.
In-memory reads and writes for the hottest paths.
Replicas, failover and optional durability.
Shard across nodes for memory and throughput beyond one machine.
Provision it in a few lines.
Every service is reachable from the same SDK, CLI and infrastructure-as-code — one identity, one bill, one audit trail across the whole catalog.
import { aether } from "@aether/sdk";
// Provision in-memory cache and query it
const in_memory_cache = await aether.databases.create({
service: "in-memory-cache",
name: "app",
region: "us-1",
});
const rows = await in_memory_cache.query(`select * from events limit 10`);At a glance.
- Compatibility
- Redis-compatible
- Latency
- Sub-millisecond
- HA
- Replicas + failover
- Persistence
- Optional
- Scale
- Cluster sharding
Built for real work.
Database offload caching
Session and token stores
Rate limiting and leaderboards
On one model, not stitched together.
The usual stack runs in-memory cache in one product, the model in another and the data in a third — and the seams between them are the cost. Aether Cloud runs it on the same platform that serves the model, governs your identity and deploys into your boundary, with the rest of the catalog one hop away.
No stitching a vector DB to one place, a warehouse to another and a model to a third — in-memory cache sits next to the rest of the catalog, one identity, one bill.
The provider that runs Aether runs your in-memory cache — so the data and the model never leave the same governed boundary to talk to each other.
Need a capability that isn’t here yet? The model writes and deploys it into the same boundary — the catalog is a starting point, not a ceiling.
Good to know.
Managed, Redis-compatible in-memory cache — for sessions, hot data and rate limiting next to your app.
Yes — drop-in for existing clients, data structures and Lua scripts.
Optionally — with replicas and durability where you need them.
Your boundary, your choice.
Pairs well with.
Managed Postgres-compatible SQL with HA, read replicas, backups and point-in-time restore.
Elastic document and key-value stores for low-latency, high-throughput workloads.
Managed embeddings and similarity search at scale — the retrieval layer under grounded apps.
Purpose-built time-series storage for telemetry, metrics and sensor streams.
A property-graph database for relationships, knowledge graphs and path queries.
Columnar, separation-of-storage-and-compute warehouse for analytics at scale.
Run In-memory cache on Aether Cloud.
Sub-millisecond managed cache for sessions, hot data and rate limiting. Deployable managed, in your VPC, on-prem or fully air-gapped — talk to us about the configuration your workloads and your boundary require.