Hyperscale (Citus) is now available on Azure Database for PostgreSQL. Want to learn more?
Update: We are no longer onboarding new users to Citus Cloud on AWS. The good news is, Citus is still available to you: as open source, as on-prem enterprise software, and in the cloud on Microsoft Azure, as a fully-integrated deployment option in Azure Database for PostgreSQL.
Because we’ve implemented Citus as an extension to Postgres, you get trusted and familiar Postgres with Citus, complete with all the data types and extensions in the Postgres ecosystem. Plus the reliability of Postgres and all of the ongoing innovation.
Citus is Postgres, which means we offer relational database features like ACID transactions, joins, foreign key constraints, and SQL.
Citus shards your Postgres database across multiple nodes to give your application more memory, compute, and disk storage. Which gives you massive parallelism, high performance, and a way to keep scaling as your SaaS business grows.
Distributed SQL query planner and executor distributes queries across shards, enabling massive parallelism and efficient resource utilization across the cluster. Citus also provides full SQL transactions across shards, making it easier than ever to migrate applications onto Citus.
Adding nodes to your Citus database cluster to scale out is as simple as dragging a slider.
Scaling the instance size for the Citus coordinator node and Citus worker nodes (memory, compute, disk storage) is as simple as clicking a radio button.
When adding nodes to a Citus cluster, the zero-downtime shard rebalancer enables you to redistribute shards across old and new worker nodes to better balance the data distribution and the performance of your Citus database.
Multi-tenant SaaS applications sometimes need to isolate the shards for a large customer to ensure that the large customer gets the resources they need and doesn’t negatively impact performance for everyone else. Hence: tenant isolation.
We continuously protect your database. We stream the write-ahead log (WAL) to S3 every 16 MB or 60 seconds, whichever happens first—and we perform backups every 24 hours. In the event of a complete infrastructure failure, we’ll restore your backup & replay the WAL to the exact moment before your system crashed.
With Auto-HA, any data that is written to the Citus cluster is instantly replicated using streaming replication onto its failover nodes, through a continuous stream called write-ahead log (WAL). To ensure proper function, Citus Cloud runs automated health checks on the cluster every 30 seconds.
PITR enables you to roll back your Citus database cluster to any point in the last 10 days to recover lost data, for internal data recovery or to help one of your customers who has inadvertently purged data.
2FA is supported via authentication apps such as Google Authenticator and Authy; also with hardware security keys such as Yubikey. 2FA is required for all Citus Cloud users after an organization exists for 30 days on Citus Cloud.
TLS encryption is required for in flight connections to Citus Cloud. All of the disk volumes on Citus coordinator nodes and worker nodes are encrypted, as are all of our automated backups to AWS S3 storage.
Granular access controls in Citus enable you to limit capabilities to certain types of users to control user access and reduce risk.
This feature enables you to seamlessly integrate virtual private clouds on AWS, enabling your Citus Cloud database instances to communicate with your other Amazon IT infrastructure as if the two VPCs were on the same network.
As a form of network perimeter control, on Citus Cloud we allow you to specify which IPs can communicate with your Citus Cloud instance.
We take care of responding and reacting to any newly-discovered vulnerabilities for you, according to their threat level.
You can use Citus Cloud to manage protected health information (PHI) & to build HIPAA-compliant apps on Postgres. Contact us for more info about Business Associate Agreements (BAA) with Citus Data.
Citus Cloud is audited at least annually against the SOC reporting framework by an independent third-party auditor—and has achieved the SOC 2 Type 2 report. The compliance audit covers controls for Security, Availability & Confidentiality.
We have automated checks in place to monitor your Citus database cluster’s health and availability, including disk capacity and your cache hit ratio.
An RSS feed is available to notify you of events such as server unavailable, failover events that are scheduled for the future, and failovers.
Our Citus Cloud dashboard shares metrics for cpu utilization, network throughput, read and write throughput, read and write latency, and WAL log backup performance.
The citus_stat_statements feature in Citus gives insights into query activity and per-tenant use of database resources, allowing you to determine cost per tenant, identify load hotspots, & optimize/tune performance as needed.
Our cloud dashboard shows you the most recent logs for each of the nodes in your Citus cluster. To analyze and retain your logs over time, Citus logs can be easily transmitted to log management applications such as Splunk, Loggly, Papertrail, Sumo Logic, and Logentries.
We take care of upgrading the Citus software on the cluster, as well as the underlying Postgres software, with minimal downtime.
Forking a Citus Cloud formation makes a copy of the cluster’s data at the current point in time and produces a new formation in precisely that state. A Citus fork gives you a sandbox to test, to experiment with, to query against—without impacting the production database.
Analysts & developers alike sometimes need to run complex queries without impacting the production database. Follower databases in Citus are read-only replicas of a Citus database cluster; changes are streamed in real-time to the Citus Cloud follower database.
Like Postgres, Citus is compatible with all the popular programming languages. And for Rails and Django we’ve created gems and libraries to make it easy for your application to adapt to a sharded, distributed Postgres database. With these gems, you can process queries as rapaciously as Chrome sucks up RAM.
You can now stream ongoing transactions from single-node Postgres databases into Citus Cloud as you prepare to migrate and ‘warp’ your application from single-node Postgres to Citus, reducing cutover time to minutes from hours or days, even for terabytes of data.
We were able to migrate relatively easily to run on top of Citus, even though our app had zero knowledge of sharding beforehand. And now that we’re using Citus, we don’t have to worry about how to manage our growth—not even 10X growth.Kelly Cheng, CTO & Co-Founder, Copper