Opportunities › Self-hosted PostgreSQL database platform › Proposed app
Pondkeeper
Run PostgreSQL on your own servers with failover and backups handled
- Score
- 40
- confidence 35
- Evidence
- 1
- items on the page
- Rivals
- 4
- named in sources
- First version
- 60 d
- estimate
- Type
- Desktop and mobile
- PWA: on computers and phones alike
- Market since
- 2015
- Established market · AI estimate
ScreensConcept
Desktop and mobile: DevOps teams configure clusters and monitor dashboards at a desk, but need to approve failovers and check alerts from anywhere on their phone. Sample screens on a computer and a phone, in the proposed brand. Their numbers are sample data.
Clusters
1 needs attention4 healthy
About this appAI proposal
Pondkeeper is a control panel for PostgreSQL clusters that run on your own servers or in your own cloud account. You point it at machines you control, pick a cluster shape, and it sets up replication, failover, backups and upgrades through an agent you install.
It is for engineering and DevOps teams that want the everyday ease of a managed database service without handing data to a cloud provider. Reasons may be cost, lock-in or data residency rules.
The installable web app is built for the on-call moment. Check cluster health, approve a failover or start a restore from your phone, and every action leaves a plain-language log entry.
- Tagline
- Your Postgres, your servers, looked after.
- Voice
- calmdirectdependable
- Why this name
- A pond is a contained body of water that someone tends. It suggests data kept in a place you own, with a keeper watching over it.
In the first version
Members say which features they would use. It tells PWAS what people want; it changes no score.
Cluster setup from a form
Choose node count, Postgres version and target servers. Pondkeeper shows the plan, then applies it.
No member yet
Failover with an optional review step
Set a cluster to fail over by itself or to ask you first. Each switch logs the cause, timing and the node that took over.
No member yet
Backups with restore checks
Schedule backups to storage you own. Pondkeeper test-restores them on a schedule and marks each as verified or not.
No member yet
Rolling upgrades
Minor and major upgrades run one node at a time, with a downtime preview and a one-tap pause.
No member yet
Brand identityAI proposal
Check the name against trademark registers before using it.
Palette
#0F3D3EDeep Pond · primary#F4EFE6Cream · surface#14201FInk · text#F2A03DAmber · accent#2F7F79Reed · data
Typography
Aa
Pondkeeper
ABCDEFGHIJKLMNOPQRSTUVWXYZ 0123456789
Your Postgres, your servers, looked after.
PricingAI proposal
The material gives no competitor prices. These tiers, priced per month by cluster count, are a starting point to test against what teams now pay for managed databases.
Community
Free
- 1 cluster, up to 3 nodes
- Setup, failover and backups
- Email alerts
Team
$99 a month
- Up to 10 clusters
- Restore checks and rolling upgrades
- Push alerts and approvals
- Audit log, 90 days
Business
$399 a month
- Unlimited clusters
- Single sign-on and roles
- Location and cost report
- Audit log, 1 year
- Priority support
What it could be worthEstimate
What a software business making this much sells for today, from real deals. Pick a monthly revenue.
If it makes
Worth about
$194,000
Sale range $132,000 to $263,000
$120,000 a year in revenue
From 87 software businesses listed and sold on Empire Flippers in the last year, revenue vetted by the broker: they sell for about 19× their monthly revenue, most between 13× and 26×.
Measured on profit, the middle deal is 32× monthly net profit: about 2.7 years of profit.
An estimate, not an offer or financial advice. A real price depends on profit, growth, churn, how much of the work is the owner's, and the buyer.
How it would growAI proposal
How the product would reach new customers through its own use, and how the first ones would be found. A plan to test, not a result.
- Built-in loop
- No loop in the product. Pondkeeper runs inside a company's own infrastructure and nobody outside the team sees it. Growth comes from content, open-source communities, talks and direct sales to teams.
- Do they become customers?
- Readers of content can become buyers, as they are the engineers who run databases. To test: whether a free single-cluster tier turns into paid use once a team has a second cluster.
- First customers
- Platform and DevOps leads at software companies with 20 to 200 engineers that run 3 to 15 PostgreSQL clusters on their own servers or cloud accounts.
- Where to reach them
- PostgreSQL community forums: Answer failover and backup questions in public threads, and offer the free tier to people who describe the problem.
- DevOps newsletters and talks: Publish a guide on moving off a managed database to self-hosted, with a real cost comparison.
- Direct outreach: Write to platform leads at firms with data residency needs and offer a guided setup of one cluster.
- First milestone
- Five teams each running a production cluster on Pondkeeper, with two of them paying for the Team tier within 90 days.
Why people already pay for this
- VerifiedGitHub repository gained 4415 stars in 2685 days
Tech stack
Every proposal builds on the same PWA base, installable from the browser on any phone or computer. Dashed boxes are what this app adds.
- AppNext.js and TypeScript
- PWAManifest and service worker
- UITailwind CSS
- Data and authSupabase Postgres
- PaymentsStripe
- EmailResend
- HostingVercel
- This app · Node agentSmall agent that runs on each database serverRuns commands on the servers, reports health and connects outward so no inbound ports are needed.
- This app · Cluster automationOpen-source Postgres HA tooling driven by the agentFailover and replication are hard to build; wrapping proven tools shortens the first version.
RisksAI inference
- TechnicalFailover, upgrades and restores across varied servers are easy to get wrong. One bad automated switch can cause data loss, so scope and test must be narrow at first.
- CommercialOpen-source tools in this space are free and well followed. Teams may not pay for a control panel unless it clearly saves on-call time.
- CommercialBuyers must trust a new vendor with production databases. Sales cycles may be long, and the first sales may need to be hands-on.
- RegulatoryCustomers with residency rules will ask where metadata, logs and alerts are stored. The control plane itself may need to be self-hostable.
- PlatformWeb push on phones varies by platform and may be unreliable for urgent alerts. A fallback such as SMS or a pager may be needed.
Everything marked AI proposal or AI inference was written by a model from the evidence on the opportunity page. The proposed name must be checked against trademark registers before it is used.