Frequently Asked Questions

Common questions about 44s, performance, compatibility, and pricing.

General

How is 44s 1,910× faster than Redis?

Redis is single-threaded by design — it can only use one CPU core. 44s uses lock-free data structures that allow all CPU cores to process requests in parallel without contention.

On a 128-core server, Redis peaks at ~78K ops/sec while 44s achieves ~149M ops/sec — a 1,910× improvement. The speedup scales with core count.

Is 44s fully compatible with Redis?

44s implements the Redis RESP protocol. Any Redis client library (redis-py, ioredis, go-redis, etc.) works out of the box — just change the host and add your API key as the password.

We support all common commands: strings, hashes, lists, sets, sorted sets, and key management. See the Commands page for the full list.

What are "lock-free data structures"?

Traditional concurrent systems use locks (mutexes) to prevent data corruption when multiple threads access shared data. Locks create bottlenecks — threads wait for each other.

Lock-free structures use atomic CPU operations (compare-and-swap) to coordinate access without blocking. Every core makes progress independently, which is why performance scales linearly with core count.

Performance

Will I see 1,910× improvement in my application?

The 1,910× figure comes from high-contention benchmarks on 128-core servers. Your actual improvement depends on:

  • Server cores: More cores = more speedup
  • Workload: Read-heavy workloads see the biggest gains
  • Contention: High-concurrency scenarios benefit most

Typical production workloads see 10-100× improvements. Run our benchmark to measure your specific case.

What's the latency like?

Sub-millisecond for most operations. Network latency is typically the dominant factor — use a region close to your application servers.

For latency-critical applications, consider co-locating in the same availability zone.

How do you benchmark?

Our benchmarks use 128-core servers. We measure operations per second under high contention (thousands of concurrent connections) to stress-test the architecture. 1,910× at 128 threads.

The benchmark code is open source on GitHub — run it yourself.

Pricing & Billing

How does the Founding Member pricing work?

Founding Members pay once and get 20 years of access with no monthly fees. This includes:

  • Pro ($2,000): 50M requests/month, all services
  • Business ($10,000): 500M requests/month, priority support

Prices double when each wave sells out. Wave 1 is currently active.

What happens if I exceed my request limit?

We don't hard-cut access. If you consistently exceed your limit, we'll reach out to discuss upgrading. Occasional spikes are fine.

Is there a monthly option?

Yes — $29/month for standard access. The Founding Member program is better value if you plan to use 44s long-term.

Migration & Integration

How do I migrate from Redis?

Since 44s speaks the Redis protocol, migration is straightforward:

  1. Update your connection config (host, password)
  2. Deploy — your existing code works unchanged
  3. Optionally use our migration tool to copy existing data

See the Migration Guide for detailed steps.

Do I need to change my application code?

No. If you're using a standard Redis client, you only change the connection settings. Your application code stays exactly the same.

Data & Reliability

Is my data persisted?

Yes. 44s uses a write-ahead log (WAL) for durability. Data is persisted to disk before acknowledging writes. In case of server failure, data is recovered from the WAL.

What's the uptime SLA?

We target 99.9% uptime. Enterprise plans include formal SLAs with credits for downtime.

Where is data stored?

Data is stored on AWS infrastructure. We currently offer US regions, with EU and Asia-Pacific coming soon.

Support

How do I get help?

Email hello@44s.io for support. Founding Members and Business plans get priority response.