Download

Radix — Redis replacement for critical IT infrastructure

Picodata Radix is a Russian solution providing compatibility with the Redis protocol. A plugin for the distributed Picodata DBMS, certified by the Russian FSTEC at trust level 4. Suitable for state information systems and critical IT infrastructure.

Request a demo Documentation

Key Radix advantages

  • FSTEC certification

    Radix runs on top of Picodata, certified at trust level 4 by the Russian FSTEC — suitable for use in state information systems and on critical-information-infrastructure (KII) facilities.

  • Redis compatibility

    Radix replaces Redis Cluster, supports RESP2, and works with the standard utilities (redis-cli, redis-benchmark and others). Clients connect without code changes.

  • Fault tolerance

    Picodata's distributed architecture gives Radix high availability and cluster-level fault tolerance via Raft consensus and a write-ahead log.

  • Drop-in Redis replacement

    Radix lets clients migrate from Redis while keeping existing applications and business processes — no code rewrites required.

  • Full cluster

    Every node sees and processes all data. Administrators configure the cluster either as a cache or for persistent storage.

Radix — a Russian alternative to Redis on the Picodata platform

Picodata is a Russian distributed DBMS, part of the Arenadata corporate data platform. PostgreSQL-compatible.

Radix is a Picodata plugin implementing a Redis-compatibility layer. It was created in response to import-substitution requirements and the need for stable in-memory data work.

What Radix is

Radix is a plugin for Picodata, a Russian Redis-compatible solution implementing the RESP2 protocol. Connect with familiar client libraries such as redis-cli; the Picodata cluster behaves like Redis, supporting more than 180 commands and the core data types. This makes Radix a convenient, reliable, and high-performance Redis replacement — especially in mission-critical applications with strict requirements for fault tolerance, security, and scalability.

Radix advantages:

  1. Automatic scaling on the Redis Cluster model. Linear performance growth as nodes are added — the system has been verified to operate stably at clusters of up to 10,000 nodes.
  2. Operation logging for control, analysis, and audit of events in the store.
  3. High availability and fault tolerance are built into the Picodata architecture — write-ahead log (WAL), Raft consensus, and replication. Separate Sentinel infrastructure or third-party monitoring is not required.

Radix can run on Picodata builds certified by the Russian FSTEC at trust level 4 and trust level 6 — making the solution suitable for state information systems and critical infrastructure.

Why Radix is more than Redis

Radix lets you use Redis commands and capabilities on top of Picodata: a single security perimeter, role model, audit, metrics, and the platform's cluster guarantees apply to all data the Redis client touches. This makes Radix not just a Redis-compatible plugin, but a full component of a trusted Russian DBMS.

Where it is used

Radix is used wherever fast data access is needed alongside fault-tolerance and security guarantees:

  • Hot-data caching in banking systems subject to Bank of Russia regulations and Regulation 851-P;
  • Session management and rate limiting in high-load web applications on KII facilities;
  • Replacing commercial Redis Enterprise licences after the western vendor's exit from the Russian market;
  • Storing transient application data in state information systems where FSTEC certification is required.
Who it is for

Radix is aimed at architects, SRE teams, and information-security specialists in banks, insurance companies, telecom operators, industrial enterprises, and government agencies — wherever the Redis interface and feature set must be preserved while complying with regulator constraints or internal security policies.

Architecture and scaling

Radix runs as a plugin inside Picodata cluster nodes. Each cluster node serves its share of keys on a Redis Cluster–compatible scheme: clients see familiar sharding and MOVED redirects. Unlike Redis, however, Picodata's underlying shard-per-core architecture means each CPU core serves its own independent shard with no contention for shared resources. This removes Redis's single-thread ceiling and yields linear throughput growth as the cluster scales horizontally.

When Picodata and Radix are not the right choice

Radix is not a fit if:

  • Only a narrow Redis feature set is needed and a single open-source Redis process on a developer laptop is enough;
  • The application code relies on Redis modules (RedisJSON, RediSearch, RedisGears) — Radix does not implement them yet;
  • The workload fits on a single server and there are no FSTEC, fault-tolerance, or audit requirements — for these cases the platform-level Picodata investment is excessive.

In other scenarios, Radix is a sound choice both economically and architecturally.

Quick start

The Picodata documentation site contains step-by-step instructions for running Picodata with plugin support and installing and activating Radix. Once installed, connect to Picodata exactly as you would to a regular Redis instance. For example:

redis-cli -p 7379

Core Redis commands are supported: GET, SET, DEL, EXPIRE, HGET, HSET, TTL, SCAN, TYPE, and others.

System requirements

Linux distributions on x86-64 and ARM are supported. The full list of compatible operating systems is on the download page.

What's new in Radix 0.13.0

Version 0.13.0 broadens Redis-protocol coverage and improves integration with cluster-deployment tooling. Details and the full change list are in the release note.

Feedback and support

Product questions, pilot requests, and bug reports — via the contact form. For commercial deployments, see Picodata services with SLA packages and the Smart Start package.