Stop babysitting managed Redis™

A managed service should NOT be installing Redis on a server. With Thiicket there's no servers: we're a serverless provider

We provide a plug and play interface and charge only for what you use: commands, network bandwidth and the memory used by your objects at millisecond resolution with no minimum usage

No credit card required. Perpetual ~40 MB free tier, prototype commitment free

What is Thiicket?

It is a serverless, maintenance-free alternative to hosted Redis

Thiicket is a radically new approach to Redis; typically a managed service provider would provision a server, install Redis on it, and let you worry about the rest. As a consumer, you'd still have to worry about resource contention, distributing keys, clustering, persistence and a whole host of issues that would be the same if you ran Redis yourself

With Thiicket our aim is to completely abstract everything away, when you create an API key for Thiicket we do NOT allocate you a server and bill you for the privilege. Rather we distribute each and every one of your keys across a pool of servers across multiple availability zones and fault domains. The only settings to configure with Thiicket is the maximum bytes you may wish to store at any point, and what to do if your keys cumulatively hit this limit. Beyond that we handle persistence and ensuring availability, while only billing you for exactly the resources you use and not a byte more

Thiicket is compatible with all existing Redis clients and libraries, we provide a simple endpoint to connect to and using your API key to authenticate you can experience the difference in seconds

You only pay for the resources you use on a per millisecond and per byte basis as you use them

Being serverless is all about only using and paying for the resources you need. Thiicket charges for 3 main items: your total memory usage, network transfer and command execution time

Memory usage is all about what you actually use, if you have 5000 keys and they each take 1 kB, then you'll be charged for only 5 MB no matter how high you set your memory limit. Each key stored is measured to millisecond and byte accuracy, which means if your usage grows and shrinks throughout the day, week and month, you'll end up paying effectively the average usage each month

Command execution time is how long all of your commands and queries take to execute, these are measured in microseconds. Empirically we've found most basic commands (GET, SET, SADD, SPOP, INCR, RPOP, RPUSH, HSET, etc) take 3 microseconds on average. That means if you were to execute 100k basic commands / minute, 24x7, for a total of 4,380,000,000 commands a month, your cumulative execution time would be 219 minutes / month or at current prices $4.38.

What's the difference?

Decouple everything

With our serverless model your compute, memory and network requirements are all decoupled, with your keys being distributed among a huge pool of servers across multiple availability zones

Distributed Redundancy

All ours regions and your keys are distributed across multiple availability zones, with data regularly flushed to disk to ensure both availability and reliability

Serverless and Hassle-free

We provide a simple endpoint for any existing Redis client to connect to, you'll no longer worry about balancing resources, patching, uptime or resiliency. With no performance penalty for increasing your memory limit you can go from 0 to 100 at a moment's notice

Pay only for what you use

Set your memory limit as high as you like, we charge for the resources you actually use. If you set your limit to 10 GB but your keys/objects only use 6 GB, you'll only be charged for 6 GB.

Single digit latency

We have single digit latency to all major cloud providers

AWS / us-east-1 1.406 ms
Azure / East US 1.339 ms
GCP / us-east4 1.914 ms

TLS included standard

Security is paramount to both businesses and consumers alike, we support TLS as a standard feature with no separate charge nor need to manually enable it

How do I use it?

Step 1: Sign up

We support numerous social sign in providers

Sign Up

Step 2: Create an API key

API keys are how you connect to Thiicket using your existing Redis client. You can set a memory limit and an eviction policy if it's hit. You're only charged for keys stored, not memory limit, the limit is to prevent run-away clients


Step 3: Connect

Update your existing code to point to and use your API key as the password. That's it, you're now serverless!