FAQ about Stackhero for Redis®* cloudRedis®*

Stackhero offers servers in 🇺🇸 USA and 🇪🇺 Europe according to your preferences.

About Redis®* on Stackhero

What is the provided version of Redis®*?

Stackhero aims to always deliver a recent and stable version of Redis®, ensuring access to recent features and full capabilities of your Redis® instance.

Is Redis open source?

Yes, Redis is open source again. Since Redis 8 (released May 2025), Redis has been published under the GNU AGPLv3, an OSI-approved open source license, as well as the source-available RSALv2 and SSPLv1 licenses. Redis was open source under the permissive BSD 3-Clause license from 2009, then moved to source-available licensing only in March 2024 (version 7.4), before returning to open source with the AGPLv3 option in Redis 8. On Stackhero, Redis is provided under the AGPLv3 open source license.
Sources: Redis is now available under the AGPLv3 license and Redis licenses.

What is the license of Redis?

Redis 8 and later are tri-licensed. Redis can be used under the GNU AGPLv3 (an OSI-approved open source copyleft license, proposed on Stackhero), the Redis Source Available License v2 (RSALv2), or the Server Side Public License v1 (SSPLv1).
AGPLv3 is a true open source license, while RSALv2 and SSPLv1 are "source-available" licenses: the code is readable and modifiable, but you are limited in what you can do with Redis. Before Redis 8, Redis used the permissive BSD 3-Clause open source license through version 7.2, and RSALv2 and SSPLv1 starting with version 7.4 (March 2024).
Stackhero provides Redis under the AGPLv3 open source license. See the official Redis licenses page for more information.

When did Redis change its license?

Redis was released under the permissive BSD 3-Clause open-source license in 2009 and remained that way through version 7.2.
In March 2024, with the release of version 7.4, "Redis, Inc." (the company behind Redis) moved to dual source-available licensing (RSALv2 and SSPLv1), which are not OSI-approved open-source licenses. This prompted the Linux Foundation and the community to create Valkey, a BSD-licensed open-source fork of the last open-source Redis version.
In May 2025, with Redis 8, Redis, Inc. added the GNU AGPLv3 open-source license, making Redis open source again.
Sources: 2024 license change and 2025 AGPLv3 announcement.

Are some Redis®* commands restricted?

We do not restrict access on any Redis®* command. You have full and unlimited access.

Which modules are included?

All modules bundled with Redis Open Source are included at no extra cost: the query engine (RediSearch) for full-text search, secondary indexing, and vector search; JSON (RedisJSON) for native JSON documents; Bloom (RedisBloom) for probabilistic structures; and time series (RedisTimeSeries).
They are disabled by default. You can enable the ones you need from the "Modules" option in your service configuration, and your Redis service restarts with them loaded. Vector sets (the VADD and VSIM commands) are built into Redis itself, so they are always available with nothing to enable.
A couple of details to keep in mind: search indexes only work on database 0. Also, once you have stored data of a module type, you should keep that module enabled, because Redis needs it to read that data back.

Can I do vector search and RAG with Redis?

Yes. The Redis query engine indexes vector embeddings and answers similarity queries (KNN and approximate search with HNSW), so you can build semantic search, recommendations, and retrieval-augmented generation using the Redis instance you already run, without adding a separate vector database to your stack.
You can combine a vector query with regular filters on numeric, tag, and text fields in the same request. This makes it practical for real applications.
See the Redis vector search documentation for the query syntax.

Managing your service

Is it possible to connect to the instance using SSH?

No, and that is the value Stackhero provides. There is no server for you to manage: Stackhero handles the operating system, security patches, service configuration, TLS certificates, firewall, monitoring, and daily atomic backups.
Everything you would normally do over SSH is available as a supervised action in your dashboard, with a single click: change the configuration, upgrade to a new version, resize the instance, open or close a port, or restore a backup.
You keep full access to the service itself, its admin console, its APIs, and your data. Nothing that belongs to your application is out of your reach.
This also reduces your attack surface: there is no SSH key to rotate, leak, or brute-force.
If the dashboard does not offer an option you need, let us know. Extending the configuration page is how the platform grows.

Do I need a sysadmin or a DevOps team to run this?

No. That is the whole point of Stackhero: you get a production-grade Redis®* without hiring anyone to operate it. No provisioning, no operating system to patch, no backup script to write and test, no monitoring stack to assemble, no on-call rotation to staff.
Your team can focus on what makes your product different, and the infrastructure work that used to take weeks simply disappears.

Is it possible to restrict access based on IPs with a firewall?

Absolutely! Your instance has its own firewall where you can decide which IPs have access to which port in 2 clicks.

Support, guarantees, and billing

Is support included, and what happens if my service goes down at night?

Premium support is included in every plan at no extra cost. There is no support tier to buy and no priority support to pay for. Support is available by email and online chat during office hours, from 9am to 6pm Central European Time. The usual first response is within the hour.

Outside those hours, your services are still monitored. Stackhero watches them around the clock. If downtime is detected, automated remediation runs immediately, and an on-call engineer is paged if the problem is not resolved. You do not have to notice the incident first. You do not have to staff an on-call rotation of your own.

What is included in the price?

Everything. The price shown on the pricing page is the price you pay: the service itself, the dedicated and isolated infrastructure it runs on, unmetered and uncapped network traffic, daily atomic backups and their storage, free and unlimited backup restorations, updates and version upgrades, TLS certificates, your custom domain, the firewall, monitoring, and premium support.
There is no setup fee, no per-user or per-seat billing, no support add-on, no traffic bill, and no charge to restore a backup.

How does billing work?

At the beginning of each month, our system computes how many hours your services were up and a detailed invoice is created.
You receive a single monthly invoice, containing all your services, clearly explained and easy to understand. Your accounting department will love that!
There is no commitment: you stop the billing of a service in a single click, and you are billed only for the hours it ran.

Data and backups

Where is the data hosted?

Stackhero is a French company operating under European and French laws.
Servers are located, depending on your choice, either in the European Union (France) or in the USA.
Backups are stored in the European Union.

How long are my backups kept, and what does it cost to restore one?

Your data is backed up automatically at least once a day on every service and every plan. Extra backups are also taken automatically during sensitive operations such as updates or upgrades.
Retention: one backup per day is kept for 7 days, one per week for 1 month, and one per month for 3 months.
Every backup is stored in a vault located at least 200 km from the datacenter running your service, so a physical incident cannot affect both locations.
You can restore backups at any time, as often as you need, with a single click. There are no restoration fees or limits on the number of restores.

What is the atomic backup system?

The problem with traditional backup systems is that files are saved at different times interval.
Let's say you have 2 files, a.txt and b.txt. Your backup starts at 9am and it finishes at 10am.
The file a.txt will contain data from 9am and b.txt will contain data from 10am.
This is traditional in backups systems and is a big issue leading to consistency problems.

This is why we developed an in-house backup system that takes an atomic image of your instance at a precise moment.
Atomic in a way that we can guarantee that all files from the backup have been taken exactly at the same time.
If your backup starts at 9am, all files will have data from 9am. You have a perfect consistent and reliable backup.

Are backups encrypted?

Backups are first transmitted to a dedicated server, which verifies and validates the data. Once these checks have been approved, the backups are encrypted and archived.
Encryption uses ECDH and Curve25519 as part of the OpenPGP protocol, with a unique key generated for each backup.

Infrastructure and performance

What is the software infrastructure?

Your service is made up of multiple subservices, each running in containers within an environment dedicated entirely to you.
This environment is private and isolated from other customers, providing strong security and high performance.
The whole thing is hosted on a bare-metal server running Stackhero DC OS, our own Linux distribution, with disks physically attached to your instance to deliver maximum IOPS.

This isolation is enforced by a dedicated virtual machine for each customer, not by shared containers on a multi-tenant host.

What about disk performance?

We use disks physically plugged to your instances.
We don't use network disks, contrary to traditional cloud solutions, that are slow and expensive.
This way we ensure best performances and exceptional IOPS.

What cloud providers are used by Stackhero?

We created our own cloud software solution, making us completely independent from cloud providers. We deploy this innovative solution directly on bare-metal servers, providing you with incredible performance and stability.

Stackhero

How long has Stackhero existed, and who is behind it?

Stackhero is a French company founded in 2009. The platform itself launched in 2018, after two years of development, and has been running production workloads ever since.
The company is profitable and independent, with no external investors and no exit to prepare. This stability matters when you choose a provider to host a service you cannot easily move. Stackhero is built to be here in ten years.

Is Stackhero for small companies or large companies?

Both use the same platform. A startup can launch its first Redis®* in production in two minutes on the smallest plan, then scale to dozens of vCPUs as the product grows, without changing providers or migrating anything.
Larger organizations get the features they require (included for all companies on all plans): ISO 27001 certification, a GDPR-compliant Data Processing Agreement, a contractual 99.9% SLA, dedicated and isolated infrastructure, and a single monthly invoice that is easy for accounting to process.
In both cases, you only need to change the size of the instance.

What certifications does Stackhero hold?

The primary mission of Stackhero is to provide a platform that is easy to use, extremely reliable, and highly secure.
A key element in achieving this mission is the annual attainment of the ISO 27001 certification, a globally recognized quality and security label.
This certification, awarded following a rigorous audit conducted by an independent external body, attests to compliance with the strictest international standards in information security.
Start Redis®* in just 2 minutes.

No payment method required!