StackGres
Kubernetes
TiDB
Google Cloud Spanner
Adaptive.live
k3s
KubeDB
CloudNativePG
RepDB
RepDB is a one-time-purchase exercise dataset for developers building fitness and workout apps โ not a subscription, not a rate-limited API. You download the data once and own it: JSON (and SQLite on the higher tier), WebP images, and full EN/DE/ES translations, with no per-request billing and no dependency on our servers staying up.
A free tier includes 400 exercises with flat-style 512ร512 images, attribution-licensed for commercial in-app use. The Starter tier ($199) adds the full catalog in classic white-background style. Standard ($399) adds transparent 1024px images, looping animations, exercise relations (similar/progressions/regressions), workout templates, and embeddings โ exclusive to that tier.
Every exercise includes muscle-group highlighting, equipment/muscle icons, MET values, and safety/goal tags. Compared to GIF- or JPG-based competitor APIs, RepDB images are transparent WebP with no watermarks, so they drop into any app UI without a white box around them.
StackGres RepDBRepDB's answer:
RepDB is sold as a one-time download, not a metered API โ you own the JSON/SQLite data and WebP images outright, with no rate limits, no per-request billing, and no risk of the vendor cutting off access. It's also the only dataset in this space with EN/DE/ES translations, transparent (alpha-channel) images with no watermark, muscle-group highlighting, safety/goal tags, and looping animations on the higher tier.
RepDB's answer:
RepDB grew out of a consumer workout app its creator was building solo. Sourcing exercise images and data meant either paying for a subscription API with usage caps and no caching rights, or producing everything from scratch. The illustrated, multi-language dataset was built for us first, then split out as its own product once it became clear other indie developers had the same problem and preferred to buy the data outright rather than rent it through an API.
RepDB's answer:
Most alternatives are subscription APIs โ you pay monthly, you're capped on requests, and ExerciseDB's terms of use explicitly forbid caching or storing the data at all, so every image render is a live paid API call. RepDB is the opposite: pay once, download the files, self-host with zero ongoing dependency. It's also the only option offering true DE/ES localization and transparent images instead of a white box behind every exercise.
RepDB's answer:
Solo developers and small teams building fitness or workout-tracking apps (iOS, Android, web) who need licensed exercise images and structured exercise data, but don't want to build their own media pipeline or depend on a rate-limited third-party API.
Based on our record, StackGres seems to be more popular. It has been mentiond 10 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
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... - Source: Hacker News / about 2 months ago
* Latency. Yes, yes, yes, they add "microseconds" vs "milliseconds for queries", and that's true, but just part of the story. There's an extra hop. There's two extra sets of TCP layers being traversed. If the hop is local (say a sidecar, as we do in StackGres) it adds complexity in its deployment and management (something we solved by automation, but was an extra problem to solve) and consumes resources. If it's a... - Source: Hacker News / 6 months ago
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... - Source: Hacker News / about 1 year ago
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. - Source: Hacker News / about 2 years ago
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... - Source: Hacker News / over 3 years ago
Kubernetes - Kubernetes is an open source orchestration system for Docker containers
TiDB - A distributed NewSQL database compatible with MySQL protocol
Google Cloud Spanner - Google Cloud Spanner is a horizontally scalable, globally consistent, relational database service.
Adaptive.live - Secure control plane to protect and access data
k3s - K3s is a lightweight Kubernetes distribution by Rancher Labs intended for IoT, Edge, and cloud deployments.
KubeDB - Kubernetes ready production-grade Databases