It's helpful feedback, and something we'd love to work towards some day. The short of it is because of Citus architecture it does require multiple underlying no

It's helpful feedback, and something we'd love to work towards some day. The short of it is because of Citus architecture it does require multiple underlying nodes and there is some overhead that until you get to a larger scale Citus doesn't necessarily make sense. If you've only got 10 GB of data a single node instance on RDS should suit you just fine. We understand some of the costs of switching and have actively been working to build tools for you to plan to use something like Citus, but then migrate when the time comes. Libraries like activerecord-multi-tenant or django-multi-tenant ensure you're ready for Citus and work perfectly well on a single node Postgres database. Then when the time comes, which could be at $100 of RDS or $500 of RDS or larger, we have Citus warp [1] that allows you in a fully online way to replicate from RDS directly into a Citus cluster. Using it we've had customers with > 4 TB of data cutover with less than a minute of impact to their database. I know that's not as simple as starting on Citus and continuing to scale, so hopefully we can address this better in the future, but for now it's the best answer we have at the moment. [1]. https://www.citusdata.com/blog/2017/12/08/citus-warp-pain-free-migrations/ https://www.citusdata.com/blog/2017/12/08/citus-warp-pain-fr...