Category · In-memory cache and queue
Redis
In-memory cache, queue and pub/sub — millisecond response
Notify me
What Redis is, in plain words
Redis is a database that lives in RAM instead of disk — making it hundreds of times faster than Postgres or MySQL for simple reads. It stores "key → value" pairs: ask for "user:42" and it returns the JSON in microseconds. It also doubles as a queue: applications push heavy tasks to be processed in the background without blocking the user.
For a workflow
For a high-traffic workflow or bot, Redis is the lung: it caches stable answers, queues incoming messages and tracks active user sessions.
What you can do with it
API caching
Real-world use case
Expensive third-party API response is cached for 5 min — fewer calls, lower latency.
Job queue
Real-world use case
Heavy tasks (email sending, PDF generation) get queued and processed in the background.
Sessions and rate limiting
Real-world use case
Login sessions in memory and per-IP rate-limit counters — instant read/write.
Beta testers get special pricing
Want early access and a say in shaping the product? Get in touch. Beta testers receive special pricing for the whole beta period — no fixed % promise, just genuinely better pricing.
We'll let you know at launch
No spam. Just one email on the day it opens.
Frequently asked questions
Is it dedicated or shared?
Shared with key-prefix isolation + scoped ACL. Your application only sees its own keys.
Does it persist across restarts?
Yes. AOF + RDB persistence configurable per plan. You do not lose queues or sessions on maintenance.
Which commands are blocked?
FLUSHALL, FLUSHDB, CONFIG, KEYS (in production) and DEBUG. SCAN is allowed for iteration.
Does it work with BullMQ, Sidekiq, Celery?
Yes. The LIST/HASH/STREAM commands those queues rely on are enabled in the ACL.