Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #17010

S

StackGres

Company blog · stackgres.io/blogdatasystems

StackGres is the company blog at stackgres.io, writing about data and systems. Since 2021, 4 different Hacker News readers have linked it 40 times, most often “Postgres sharding with Citus and StackGres – scaling coordinator nodes”. It is still writing: the last post was on 2026-10-16, and you can follow it by feed.

Visit the blog
40mentions?
4HN people?
2021–2026first – last linked?
Links on Hacker News per year · peak 11 in 2021

Too few sampled comments (2) to say how often HN recommends it.?

Why HN links it

Bare links suggesting StackGres to Kubernetes users, with one comment noting its Citus integration. The comments do not discuss the writing itself.

Summarised by Claude from a sample of 2 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

StackGres is a fully-featured platform for running PostgreSQL on Kubernetes. Deploy in minutes an Enterprise-Grade Postgres-as-a-Service, in your infrastructure. 100% Open Source.

Most-linked posts?

  1. /
    2 people · 8 mentions · first linked 2021-12-08
  2. Postgres sharding with Citus and StackGres – scaling coordinator nodes
    2 people · 2 mentions · first linked 2026-10-09

What Hacker News says?

  1. But it's not really accurate: > This adds some undesirable side effects, however. First, the coordinator becomes the bottleneck. Apart from being able to use any node as a coordinator (and you can load balance them to avoid having "multiple connection strings), there's a new pattern which effectively allows you to have as many coordinators as you want. They are effectively "data-less" nodes. We have devised and impl…

    Comment linking /doc/latest/administration/sharded-cluster/backup-restore/

    on “Neki – Sharded Postgres”
  2. Submitted Show HN: StackGres: open-source Postgres-aaS on Kubernetes with 120 Extensions as a story · 54 points

    HN discussion
  3. Shameless plug (StackGres team member here) but StackGres possibly has the largest selection of ready-to-use Postgres extensions [1]. Give it a quick try on any Kubernetes cluster, like k3s on your laptop (one command install), and install any extension from the Web Console or a 1-line in the SGCluster yaml. [1]: https://stackgres.io/extensions/

    Comment linking /extensions/

    on “Show HN: Pg_jsonschema – A Postgres extension for JSON validation”
  4. Submitted StackGres 1.0.0: open-source Postgres-aaS with 120 Extensions as a story · 11 points

    HN discussion
  5. I applaud the decision to use AGPL-3.0. For me, it's a license that provides forward guarantees to the Community: no proprietary forks can happen, so any fork will be an OSS fork from which the upstream project may benefit too, which benefits all users. That's the reason we chose this license for StackGres [1], another project in the Postgres space. [1]: https://stackgres.io

    Comment linking /

    on “Pg_lakehouse: Query Any Data Lake from Postgres”
  6. Submitted StackGres 1.0: open-source Postgres-aaS with 120 Extensions as a story · 4 points

    HN discussion
  7. For the K8S folks: https://stackgres.io

    Comment linking /

    on “PostgreSQL Streaming Replication (WAL); What It Is and How to Configure One”
  8. Submitted Postgres sharding with Citus and StackGres – scaling coordinator nodes as a story · 3 points

    HN discussion
  9. ToroDB founder here. Thank you for mentioning this. Unfortunately, yes, ToroDB is no longer being developed. I still believe it's a fantastic idea, and provides significant value. But when it was being built, 5 years ago, the NoSQL (as in "abandon SQL") state of mind was too strong, and the value proposition was not well understood. I moved to work on what's always been my passion and preference: Postgres, Postgres,…

    Comment linking /

    on “FerretDB: A truly open-source MongoDB alternative”
  10. Submitted StackGres 1.0.0: open-source Postgres-aaS with 120 Extensions as a story · 3 points

    HN discussion
  11. I agree. If the extension availability is the main concern, I'd recommend the open source StackGres [1] operator, which has, possibly, the largest Postgres extension catalog [2] available. [1] https://stackgres.io [2] https://stackgres.io/extensions/ Disclaimer: founder of OnGres, the company behind StackGres

    Comment linking /extensions/

    on “Custom SQL functions for data analytics in PostgreSQL”
  12. Submitted StackGres 1.0.0: open-source Postgres-aaS with 120 Extensions as a story · 3 points

    HN discussion
  13. I'm the founder of OnGres [1] the company behind StackGres [2]. I'd love to hear your feedback if you'd be interested in also trying StackGres. It's one of the most feature-full operators available, has a complete Web Console and REST API and supports close to 200 extensions. Hope it would be interesting for you. [1]: https://ongres.com [2]: https://stackgres.io

    Comment linking /

    on “Self-hosting a high-availability Postgres cluster on Kubernetes”
  14. Submitted Open-source Citus matches PlanetScale's Neki at 10M QPS on half the data nodes as a story · 2 points

    HN discussion
  15. > schema changes locking Schema changes need locking... everywhere. Citus is no different. And they need proper design everywhere. If you mean that it requires distributed transactions, well, yes, again: expected and solved . Not even all sharding solutions support this. > coordinator node Not sure what the problem is here. If what you mean is that a single coordinator, even with an HA replica, can saturate, that's…

    Comment linking /doc/latest/administration/sharded-cluster/citus/

    on “118M Queries per Second on Neki”
  16. Submitted Scaling Postgres without limits: announcing Query Routers for Citus as a story · 2 points

    HN discussion
  17. If building a list of alternatives, let me do a shameless plug for StackGres [1], the Postgres platform for Kubernetes with a fully featured Web Console, AMD64 and ARM64 support and more than a hundred available Postgres extensions [2]. Fully open source, no usage restrictions. [1] https://stackgres.io/ [2] https://stackgres.io/extensions/ Disclaimer: founder of the project.

    Comment linking /extensions/

    on “Pgo: The Postgres operator from crunchy data”
  18. Submitted Easily Running Babelfish for PostgreSQL on Kubernetes as a story · 2 points

    HN discussion
  19. Hi HN, I’m Alvaro Hernandez, Founder of OnGres (OnGres == “ON postGRES”) [01]. I started using Postgres before the year 2,000 --and never looked back. Postgres reliability, feature set, its incredible documentation, Community, and access to source code always fulfilled all mine and my customer’s needs. Postgres is trivial to install: $ apt-get install postgresql # will get Postgres installed on your laptop. But woul…

    Comment linking /doc/latest/reference/crd/

    on “Show HN: StackGres: open-source Postgres-aaS on Kubernetes with 120 Extensions”
  20. Submitted Easily Running Babelfish for PostgreSQL on Kubernetes as a story · 2 points

    HN discussion
  21. At StackGres [1] we find Timescale to be one of the most used extensions. Timescale is quite a successful project! StackGres is actually the first solution recommended by Timescale for self-hosting with Kubernetes operators [2]. So if you are into Kubernetes (or if not, consider it, using something like K3s [3] is quite straightforward and lightweight on resources), this is probably a great option to self-host which…

    Comment linking /

    on “How TimescaleDB compresses time-series data”
  22. Submitted Show HN: StackGres: open-source Postgres-aaS on Kubernetes with 120 Extensions as a story · 2 points

    HN discussion
  23. Interested in contributing/co-writing such a runbook for StackGres? [1] [1]: https://stackgres.io/doc/latest/runbooks/

    Comment linking /doc/latest/runbooks/

    on “SPQR: Scaling PostgreSQL via Sharding”
  24. Submitted Easily Running Babelfish for PostgreSQL on Kubernetes as a story · 1 points

    HN discussion
  25. This is conceptually similar to what we did for Postgres extensions at the StackGres [1] project. I gave a talk at a Kubecon about it [2]. However, this scheme is not perfect. Some Kubernetes security solutions enforce immutable containers, and once the agent pulls any additional file into the container, it will be flagged. It's also harder to reason about the security of the image (think CVEs, etc), given that its…

    Comment linking /

    on “Application Less Containers”
  26. This is good and interesting recipe to get Keycloak and Postgres on Kubernetes. There is an important improvement, though: the Postgres deployed here is not production ready (high availability, backups, monitoring, etc). We run Keycloak on StackGres [1] which gives us production-ready Postgres setup (disclaimer: it's dogfooding). Happy to share the YAML manifests used to deploy Keycloak with StackGres. Maybe we will…

    Comment linking /

    on “Keycloak with PostgreSQL on Kubernetes”
  27. The key for me is the level of automation that you can reach at a reasonable "development cost". Let me elaborate. K8s, if anything, is an API. An API that allows you to interact with compute, storage and networks in a way that is abstracted from the actual underlying infrastructure. This is incredibly powerful. You can, essentially, code and automate all your infrastructure. But this goes beyond deployment, somethi…

    Comment linking /doc/latest/reference/crd/sgdbops/

    on “Running Databases on Kubernetes”
  28. This is not from Supabase, but as a community contribution. See upthread [1]: "at StackGres we have built a Runbook [2] and companion blog post [3] to help you run Supabase on Kubernetes." [1]: https://news.ycombinator.com/item?id=36006308 [2]: https://stackgres.io/doc/latest/runbooks/supabase-stackgres/ [3]: https://stackgres.io/blog/running-supabase-on-top-of-stackgr...

    Comment linking /blog/running-supabase-on-top-of-stackgres/

    on “Migrating from Supabase”
  29. A mid way could be self-hosting Supabase, whether you use more or less Supabase features. I know self-hosting might be challenging, specially getting a production-ready Postgres backend for it. That's why at StackGres we have built a Runbook [1] and companion blog post [2] to help you run Supabase on Kubernetes. All required components are fully open source, so you are more than welcome to try it and give feedback i…

    Comment linking /blog/running-supabase-on-top-of-stackgres/

    on “Migrating from Supabase”
  30. IMO transparent proxies for observability are not the best pattern. And I speak from experience, we developed the Postgres plugin for Envoy [1], [2] and we use it in StackGres [3], among others, for this very same reason, observability. There's two main problems with said proxies: * Latency. Yes, yes, yes, they add "microseconds" vs "milliseconds for queries", and that's true, but just part of the story. There's an…

    Comment linking /

    on “Show HN: SQL-tap – Real-time SQL traffic viewer for PostgreSQL and MySQL”

Search all of HN for stackgres.io