Integration

Redis and Better-PaaS

Last updated June 15, 2026
Reviewed by Better-PaaS team

How Better-PaaS works with Redis to support cache, queues, and session-heavy workloads in a self-hosted deployment workflow.

Overview

Redis helps Better-PaaS support cache, queues, and session-heavy workloads. The integration keeps the platform workflow practical without hiding the underlying infrastructure from you.

Role in the workflow

Redis is used to support cache, queues, and session-heavy workloads. It supports the broader Better-PaaS goal: deploy from source or image, run in containers, route traffic securely, and keep operations understandable.

Setup considerations

Configuration depends on the integration. Always verify credentials, network access, DNS, and app health before switching production traffic.

  • Confirm credentials and permissions
  • Check environment variables
  • Inspect logs after setup
  • Document any external dependency

Operational guidance

Treat integrations as part of your deployment system. Rotate secrets when needed, back up stateful services, and keep the server updated.

FAQ

Is Redis required for Better-PaaS?

Some integrations are core platform dependencies, while others are optional workflow integrations. The setup guide for each feature explains when it matters.

Can I use Redis with custom Docker images?

Usually yes when the app image exposes the right port and accepts configuration through environment variables.