ProgrammableMarketing/pgdog.dev (opens in a new tab)
PDF

Views

  • Plan
  • Roadmap
  • Research

On this page

  • The brief
  • Start here
  • Idea portfolio
  • Effort vs impact
  • This week · 7
  • This quarter · 10
  • Big bets · 3
  • Wildcards · 2
  • How we can help
Generated Nov 10, 2026
  1. Programmable
  2. Playbooks
  3. PgDog
PgDog logo

growth playbook · Nov 10, 2026

pgdog.dev (opens in a new tab)

PgDog growth playbook

Diagnosis

PgDog has the distribution most infrastructure startups want: about 5.6k GitHub stars, millions of image downloads, a 548-point Hacker News launch, 17 published customer logos and a blog that already compares it with PgBouncer, Citus and RDS Proxy. The gaps sit between that attention and revenue.

The marketing site has no real sitemap and serves the homepage for every unknown address, so search engines index copies of the homepage instead of the blog. Enterprise has no price, no customer stories and no answer for AGPL reviewers. The docs only explain migrating from PgBouncer, although RDS Proxy users are the stated target.

The team is three people hiring a fourth, so this playbook favors fixes a founder can ship in a day, docs and tools that sell while the team sleeps, and partners who add capacity: first the crawl fix, Enterprise pricing anchors, case studies and an AGPL FAQ; then migration guides, a config converter, a CI action and honest comparison, HA and resharding pages; then AWS Marketplace, a one-command AWS install and a consultancy partner program.

Growth Score

7/10

Biggest Opportunity

Turn open-source reach (millions of downloads, thousands of engineers testing it daily) into named Enterprise conversations, by making the site findable, the price legible and the migration path from RDS Proxy as easy as the one from PgBouncer.

Biggest Risk

Well-funded rivals now offer sharded Postgres too (PlanetScale's Neki, Multigres, Citus from Microsoft), and a three-person team promising 15-minute support can be overwhelmed before Enterprise revenue pays for more people.

01

Start here

The three moves to make first. Each one is written up in full below.

  1. 1

    Give pgdog.dev a real sitemap and real 404s, so search engines index the 23 blog posts instead of copies of the homepage

    Open pgdog.dev/sitemap.xml and pgdog.dev/any-made-up-path, confirm both show the homepage, and find the hosting rule that falls back to index.html.

    High impact First result in 2-4 weeks
  2. 2

    Publish how Enterprise is priced, so an engineer can take a number to their manager before the call

    Write down the price of the last three Enterprise deals and what drove each.

    High impact First result in 1 month
  3. 3

    Turn three of the 17 published logos into case studies with before-and-after numbers

    Email the five quoted customers and ask which would do a 30-minute interview.

    High impact First result in 1 month

02

Your idea portfolio

22 ideas, grouped by when to run them. Open any idea for how to run it: the steps, who to approach, copy you can use, and how to measure it.

  • 7 ideas are marked Unexpected: plays you are unlikely to have tried.

Every idea placed by the effort it takes against the impact it could have. Quick wins sit top left; select a number to open that idea. The filters below narrow the list by status, timing, category and what Programmable can build.

Effort vs impactEach number is an idea. Select one to open it.
Impact →
Quick wins · 2Big bets · 8Fill-ins · 6Reconsider · 6
Effort →

Showing 22 of 22 ideas

This week 7

Quick wins with a clear first action.

  • 01

    pgdog.dev/sitemap.xml does not return a sitemap. It returns the homepage as an ordinary page, and so does every address that does not exist (/about, or any made-up path), instead of a 404. robots.txt has no Sitemap line either. Search engines therefore get no list of the 23 blog posts, and they index the copies: a site: search shows /sitemap.xml as a page titled with the funding banner ("We raised a $5.5M seed round"), a blog post under that same banner text, /about as a separate page, and the homepage under its old headline, "Postgres scales with PgDog". The docs site already publishes a proper 104-URL sitemap, and the marketing site is fast (real visitors pass Core Web Vitals), so crawl hygiene is the one gap.

    High impactLow effort First result in 2-4 weeks Founding Software Engineer

    First action

    Open pgdog.dev/sitemap.xml and pgdog.dev/any-made-up-path, confirm both show the homepage, and find the hosting rule that falls back to index.html.

    How to measure it

    Indexed posts and organic blog clicks

    Now
    –
    Target
    All 23 posts indexed; +50% organic clicks to /blog
    By
    60 days

    Steps

    1. 1

      Find the fallback

      Locate the static-host or Cloudflare rule that serves the homepage for every unknown path.

      Founding Software Engineer 1 hour

    2. 2

      Generate the sitemap

      A build step that writes /sitemap.xml with the homepage, /enterprise, /blog and all posts, with lastmod from the RSS dates.

      Founding Software Engineer 2 hours

    3. 3

      Update robots.txt

      Add Sitemap lines for pgdog.dev and docs.pgdog.dev.

      Founding Software Engineer 15 minutes

    4. 4

      Serve real 404s

      Status 404 with links to docs, blog and Enterprise; 301 /about and /enterprise.html to their canonical pages.

      Founding Software Engineer 2 hours

    5. 5

      Fix titles

      Each post gets its own title, description and canonical; the funding banner stays out of the title.

      Founding Software Engineer 2 hours

    6. 6

      Submit and recrawl

      Submit both sitemaps in Search Console and Bing Webmaster Tools; request recrawl of the homepage and the three comparison posts.

      Founder & CEO 1 hour

    7. 7

      Watch coverage

      Weekly check of indexed pages, soft-404 reports and clicks to the comparison posts.

      Founder & CEO weekly for 8 weeks

    First result
    2-4 weeks
    Cost
    $0, about one engineer-day
    Owner
    Founding Software Engineer

    Smallest test

    Ship the sitemap and the robots.txt line today, then check in Search Console a week later how many posts it has discovered.

    Why it works

    Generate /sitemap.xml at build time, listing the homepage, /enterprise, /blog and every post, with lastmod dates taken from the RSS feed. Add Sitemap lines for pgdog.dev and docs.pgdog.dev to robots.txt. Make unknown paths return a real 404 page with links to the docs, the blog and Enterprise, and redirect /about and /enterprise.html to their canonical pages. Give every post its own title tag, meta description and canonical, so the funding banner can never become a page title. Then submit both sitemaps in Google Search Console and Bing Webmaster Tools and ask for the homepage to be recrawled, so search results show "Scale Postgres n times".

    A sitemap is how search engines learn which pages exist and when they change. Soft 404s spread duplicate copies of the homepage and waste crawl on addresses that do not exist. For a three-person team with no marketing hire, the comparison posts (vs. PgBouncer, Citus and RDS Proxy) ranking for the searches engineers make before switching is the cheapest acquisition channel there is, and it costs a day of work.

    Ready to use

    Checklistpgdog.dev crawl fix list

    [ ] /sitemap.xml returns XML (urlset) listing /, /enterprise, /blog and all 23 posts with lastmod
    [ ] robots.txt: Sitemap: https://pgdog.dev/sitemap.xml and Sitemap: https://docs.pgdog.dev/sitemap.xml
    [ ] Unknown paths return HTTP 404 with links to docs, blog, Enterprise
    [ ] /about and /enterprise.html 301 to canonical pages
    [ ] Every post: unique <title>, meta description, rel=canonical
    [ ] Funding banner not used as a title
    [ ] Both sitemaps submitted to Search Console and Bing Webmaster Tools
    [ ] Homepage recrawl requested so results show "Scale Postgres n times"

    Risks and how to handle them

    • A real 404 breaks old links that relied on the fallback

      Before switching, list paths that got traffic in the last 90 days and redirect any that still matter.

    • Duplicates take time to drop out

      Use the removal and URL inspection tools for /sitemap.xml and /about.

    Evidence

    • Your websiteCrawl check (fetched twice, November 10, 2026): pgdog.dev/sitemap.xml returns the homepage as an HTML page, not an XML sitemap; made-up addresses such as /this-page-does-not-exist-xyz, and /about, also return the full homepage instead of a 404; the site links to both /enterprise and /enterprise.html; robots.txt contains only "User-agent: *" and "Allow: /", with no Sitemap line. The docs site, by contrast, publishes a 104-URL sitemap.Source
    • Search resultsA site:pgdog.dev web search (November 10, 2026) lists pgdog.dev/sitemap.xml as an indexed page titled with the funding banner, "We raised a $5.5M seed round. Read the post→"; shows the post "Why we built yet another Postgres connection pooler" under the same banner text; lists /about, a copy of the homepage, as its own page; and still shows the homepage under the old headline "Postgres scales with PgDog".Source
    • Your websiteBlog (checked November 10, 2026): 23 posts from March 2025 to November 2026, including "PgDog vs. PgBouncer", "PgDog vs. Citus", "PgDog vs. RDS Proxy", "Sharding a real Rails app", "Sharding pgvector" and "Multi-tenant Postgres can be easy"; no newsletter signup; a valid RSS feed exists at /feed.xml but the blog page does not link to it; a sampled post ends with a link to the installation docs and no enterprise or support offer.Source
    • Google PageSpeedPageSpeed (November 10, 2026): mobile performance 99 and desktop 100; real visitors pass Core Web Vitals (75th percentile LCP 755 ms, INP 48 ms, CLS 0); accessibility 93, with two issues (no main landmark; ARIA roles missing required children).Source
  • 02

    The Enterprise page describes a control plane, Insights and support that arrives "within 15 minutes", and mentions an SLA, but it gives no price, plan, terms or compliance information. The only way to learn the cost is a Calendly call. Meanwhile PgDog's own philosophy is that everything is public, with no waiting list or credit card, and the Enterprise image is already downloaded millions of times.

    High impactLow effort First result in 1 month Founder & CEO

    First action

    Write down the price of the last three Enterprise deals and what drove each.

    How to measure it

    Enterprise call bookings

    Now
    –
    Target
    +30%
    By
    90 days

    Steps

    1. 1

      Review past deals

      Price, size and what was bought in each.

      Founder & CEO 2 hours

    2. 2

      Pick the unit

      Cluster, pod or database: whatever customers already understand.

      Founder & CEO 1 day

    3. 3

      Define support levels

      Response times, channels and architecture reviews per level.

      Founder & CEO 1 day

    4. 4

      Write the section

      Starting price, what's included, license and procurement documents.

      Founder & CEO 1 day

    5. 5

      Publish

      On /enterprise with a link from the homepage.

      Founding Software Engineer 2 hours

    6. 6

      Ask on calls

      Whether the visitor saw the price first, and whether it helped.

      Founder & CEO ongoing

    First result
    1 month
    Cost
    $0
    Owner
    Founder & CEO

    Smallest test

    Add one line, "Enterprise starts at $X per year", and compare bookings for a month.

    Why it works

    Add a "How Enterprise is priced" section: what the price is based on (for example per production cluster), a "starting at" figure or range, what each support level includes (Slack channel, P0 response time, architecture reviews), contract length, the non-AGPL license, and the documents procurement will ask for (security questionnaire, DPA). Keep the call as the way to get a quote, but let people arrive already knowing the price is in range.

    Infrastructure buyers have to justify spend upward before they can book a vendor call. A public anchor filters out poor fits, shortens the first call and matches the brand's "no gatekeeping" message.

    Risks and how to handle them

    • Anchoring too low for large customers

      Publish a starting price and say large deployments are quoted.

    • Competitors see the price

      They can already learn it on one call; the buyer benefits more.

    Evidence

    • Your websiteEnterprise page: a control plane (real-time metrics, pause, resume and block queries across pods, high availability, SSO), Insights (live and slow queries with automatic query plans, Prometheus and OTEL exporters, alerts with an Incident.io integration) and dedicated support in a Slack channel, with the team there "within 15 minutes" when something breaks; an SLA is mentioned without terms; no prices, plans, compliance information or customer stories; calls to action "Talk to us", "Live demo" and the enterprise docs.Source
    • Your website"The 3 D's of software: distribution, distribution, distribution" (November 4, 2026): 3.69M downloads of the open-source version, 5.16M of PgDog Enterprise Edition and 323k of the EE control plane; about 500 issues in a year; "thousands of engineers" test PgDog daily; no waiting list, contact form or credit card, and the EE image and Helm chart are public; a GitHub Actions example runs an app's test suite through PgDog; no marketplace listing is mentioned.Source
    • GitHubGitHub (pgdogdev/pgdog, checked November 10, 2026): about 5.6k stars, 312 forks, 134 open issues and 137 open pull requests; licensed AGPL-3.0; the README says the Enterprise edition is available under a separate license for organizations that do not allow AGPL software.Source
  • 03

    A sampled blog post ends with a link to the installation docs and no offer of help, and the PgBouncer migration guide, read by people who are already moving production traffic, has no mention of migration help or Enterprise support, although the Enterprise page sells "architecture reviews for migrations".

    Medium impactLow effort First result in 2 weeks Founder & CEO

    First action

    Add the box to the PgBouncer migration guide and the RDS Proxy post.

    How to measure it

    Content-sourced calls

    Now
    –
    Target
    8 a month
    By
    60 days

    Steps

    1. 1

      Write the box

      One sentence, one link, what the review covers.

      Founder & CEO 1 hour

    2. 2

      Tag the links

      A Calendly link or UTM per page.

      Founder & CEO 1 hour

    3. 3

      Add to the blog template

      So every post, old and new, shows it.

      Founding Software Engineer 2 hours

    4. 4

      Add to the docs

      Migration overview, PgBouncer guide, sharding and deployment pages.

      Founding Software Engineer 2 hours

    5. 5

      Track

      Bookings by source page each month.

      Founder & CEO monthly

    6. 6

      Iterate

      Rewrite the box on pages with views but no bookings.

      Founder & CEO quarterly

    First result
    2 weeks
    Cost
    $0
    Owner
    Founder & CEO

    Smallest test

    Add the box to the PgBouncer guide only and count bookings for a month.

    Why it works

    Add one short box to every post and to each migration page: "Moving production traffic? Get an architecture review from the people who wrote PgDog", linking to /enterprise and to a Calendly link tagged with the page it came from. On the migration guide, also list what the review covers (pool sizing, unsupported PgBouncer settings, cutover plan).

    Readers of a migration guide are mid-project and at their most willing to pay to reduce risk. Tagged booking links also show which content creates pipeline.

    Risks and how to handle them

    • Feels salesy to an open-source audience

      Keep it one line, below the content, and make it about risk, not features.

    Evidence

    • Your websiteBlog (checked November 10, 2026): 23 posts from March 2025 to November 2026, including "PgDog vs. PgBouncer", "PgDog vs. Citus", "PgDog vs. RDS Proxy", "Sharding a real Rails app", "Sharding pgvector" and "Multi-tenant Postgres can be easy"; no newsletter signup; a valid RSS feed exists at /feed.xml but the blog page does not link to it; a sampled post ends with a link to the installation docs and no enterprise or support offer.Source
    • Your docsPgBouncer migration guide: manual mapping tables from pgbouncer.ini and userlist.txt to pgdog.toml and users.toml, with no conversion tool; lists PgBouncer features with no equivalent (auth_query, reserve pools, UNIX sockets, LDAP, HBA files, statement pooling); no offer of migration help or Enterprise support.Source
    • Your websiteEnterprise page: a control plane (real-time metrics, pause, resume and block queries across pods, high availability, SSO), Insights (live and slow queries with automatic query plans, Prometheus and OTEL exporters, alerts with an Incident.io integration) and dedicated support in a Slack channel, with the team there "within 15 minutes" when something breaks; an SLA is mentioned without terms; no prices, plans, compliance information or customer stories; calls to action "Talk to us", "Live demo" and the enterprise docs.Source
  • 04

    PgDog runs a public live demo of the Enterprise control plane, but only the Enterprise page links to it. The homepage offers "Get PgDog", "For enterprise" and "Talk to us", so the fastest way to see what Enterprise adds is two clicks deep. The homepage is already fast for real visitors, so there is room to add it without a speed cost.

    Medium impactLow effort First result in 2 weeks Founding Software Engineer

    First action

    Add the demo link to the homepage hero.

    How to measure it

    Demo-sourced Enterprise calls

    Now
    –
    Target
    5 a month
    By
    60 days

    Steps

    1. 1

      Add the button

      Third button in the hero, tagged.

      Founding Software Engineer 1 hour

    2. 2

      Add a screenshot

      Live queries and query plans, in the Enterprise teaser.

      Founding Software Engineer 2 hours

    3. 3

      Banner in the demo

      Link back to pricing and a call.

      Founding Software Engineer 2 hours

    4. 4

      Keep the demo lively

      Make sure the demo shows realistic traffic and alerts.

      Founding Software Engineer 1 day

    5. 5

      Fix accessibility

      Add a main landmark and fix the ARIA role issue while editing the page.

      Founding Software Engineer 1 hour

    6. 6

      Measure

      Demo visits and bookings each month.

      Founder & CEO monthly

    First result
    2 weeks
    Cost
    $0
    Owner
    Founding Software Engineer

    Smallest test

    Add the hero link today and compare demo visits for two weeks.

    Why it works

    Add a "See the live demo" button to the hero and a screenshot of the control plane's live query view in the Enterprise teaser, linking to the demo with a tracking tag. In the demo itself, add a small banner back to Enterprise pricing and a call.

    Engineers trust what they can click. A working control plane answers "what do I pay for?" faster than any feature list, and it fits the brand's "everything public" approach.

    Risks and how to handle them

    • Demo traffic spikes

      Rate-limit and keep it read-only.

    Evidence

    • Your websiteHomepage (checked November 10, 2026): H1 "Scale Postgres n times"; "3M+ queries/s in production"; 17 customer logos including Coinbase, Ramp, Modal, Huntress, Pennylane, PrizePicks and TRM Labs; five short customer quotes, one comparing PgDog favorably with RDS Proxy; DDL runs on every shard so Alembic and ActiveRecord migrations work; no pricing; calls to action "Get PgDog" (docs), "For enterprise" and "Talk to us" (a Calendly booking). The live demo is linked only from the Enterprise page.Source
    • Your websiteEnterprise page: a control plane (real-time metrics, pause, resume and block queries across pods, high availability, SSO), Insights (live and slow queries with automatic query plans, Prometheus and OTEL exporters, alerts with an Incident.io integration) and dedicated support in a Slack channel, with the team there "within 15 minutes" when something breaks; an SLA is mentioned without terms; no prices, plans, compliance information or customer stories; calls to action "Talk to us", "Live demo" and the enterprise docs.Source
    • Google PageSpeedPageSpeed (November 10, 2026): mobile performance 99 and desktop 100; real visitors pass Core Web Vitals (75th percentile LCP 755 ms, INP 48 ms, CLS 0); accessibility 93, with two issues (no main landmark; ARIA roles missing required children).Source
  • 05

    PgDog ships a release every Thursday and has a valid RSS feed, but the blog does not link to the feed and there is no newsletter signup anywhere. Thousands of engineers test PgDog, and PgDog has no way to reach them again once they leave the site.

    Medium impactLow effort First result in 1 month Founder & CEO

    First action

    Add the RSS link and a signup form to the blog page.

    How to measure it

    Subscribers

    Now
    –
    Target
    1,000
    By
    90 days

    Steps

    1. 1

      Pick a tool

      Any simple email tool with a double opt-in.

      Founder & CEO 1 hour

    2. 2

      Add the forms

      Blog, docs footer, installation page.

      Founding Software Engineer 2 hours

    3. 3

      Link the feed

      RSS icon and a link tag on the blog.

      Founding Software Engineer 30 minutes

    4. 4

      Write the first digest

      Last month's releases in plain language.

      Founder & CEO 2 hours

    5. 5

      Announce

      Discord, GitHub README and release notes.

      Founder & CEO 1 hour

    6. 6

      Send monthly

      Same format, first week of each month.

      Founder & CEO monthly

    First result
    1 month
    Cost
    Under $50 a month
    Owner
    Founder & CEO

    Smallest test

    Link the RSS feed and add one signup form, then count subscribers after two weeks.

    Why it works

    Add a "Get release notes" email signup to the blog, the docs footer and the installation page, and link the RSS feed. Send a short monthly digest: the four releases, one fixed issue a user asked for, one new doc and one production story. Let the signup ask, optionally, for company and Postgres setup.

    Release notes are the one email infrastructure engineers actually want, and an owned list turns anonymous downloads into an audience PgDog can tell about Enterprise, guides and case studies.

    Risks and how to handle them

    • Founder time each month

      Draft the digest from the changelog and GitHub release notes.

    Evidence

    • Your websiteBlog (checked November 10, 2026): 23 posts from March 2025 to November 2026, including "PgDog vs. PgBouncer", "PgDog vs. Citus", "PgDog vs. RDS Proxy", "Sharding a real Rails app", "Sharding pgvector" and "Multi-tenant Postgres can be easy"; no newsletter signup; a valid RSS feed exists at /feed.xml but the blog page does not link to it; a sampled post ends with a link to the installation docs and no enterprise or support offer.Source
    • Your websiteFunding post (June 10, 2026): a $5.5M seed from Basis Set, YC, Pioneer Fund and others; over 2M queries per second in production across dozens of deployments; more than 20 TB sharded; over 1.4M Docker pulls; a three-person team; new releases every Thursday; an Enterprise edition to make AWS deployment easier, with SLA-backed support.Source
    • Your website"The 3 D's of software: distribution, distribution, distribution" (November 4, 2026): 3.69M downloads of the open-source version, 5.16M of PgDog Enterprise Edition and 323k of the EE control plane; about 500 issues in a year; "thousands of engineers" test PgDog daily; no waiting list, contact form or credit card, and the EE image and Helm chart are public; a GitHub Actions example runs an app's test suite through PgDog; no marketplace listing is mentioned.Source
  • 06

    The homepage shows 17 customer logos, including Coinbase, Ramp and Modal, and five one-line quotes, one of them comparing PgDog favorably with RDS Proxy. The RDS Proxy post says customer production results exist but there are no case studies yet, and the Enterprise page has no customer stories at all.

    High impactMedium effort First result in 1 month Founder & CEO

    First action

    Email the five quoted customers and ask which would do a 30-minute interview.

    How to measure it

    Published case studies

    Now
    –
    Target
    3
    By
    45 days

    Steps

    1. 1

      Ask

      The customers who gave homepage quotes.

      Founder & CEO 1 day

    2. 2

      Interview

      30 minutes each, with their numbers.

      Founder & CEO 1 week

    3. 3

      Write

      One page each, with a diagram of the setup.

      Contract technical writer 1 week

    4. 4

      Approve

      Customer sign-off on names and numbers.

      Founder & CEO 1 week

    5. 5

      Publish

      /customers plus links from Enterprise and the comparison posts.

      Founding Software Engineer 1 day

    6. 6

      Reuse

      In the digest, on Hacker News and in sales calls.

      Founder & CEO ongoing

    First result
    1 month
    Cost
    A contract writer, about $1,500
    Owner
    Founder & CEO

    Smallest test

    Publish one case study from the customer whose quote compares PgDog with RDS Proxy.

    Why it works

    Pick three customers who already gave a public quote and cover the three paths buyers take: one that left RDS Proxy, one that left PgBouncer and one that sharded. For each, publish one page: the problem, the setup, the cutover, and numbers (connections, latency, queries per second, incidents). Put them on the Enterprise page, at the end of the matching comparison post and in the release-notes digest.

    Infrastructure buyers copy peers. A named company with numbers is the strongest answer to "is a three-person company safe for our database?".

    Risks and how to handle them

    • Large customers need legal approval

      Offer an anonymized version with numbers while approval is pending.

    Evidence

    • Your websiteHomepage (checked November 10, 2026): H1 "Scale Postgres n times"; "3M+ queries/s in production"; 17 customer logos including Coinbase, Ramp, Modal, Huntress, Pennylane, PrizePicks and TRM Labs; five short customer quotes, one comparing PgDog favorably with RDS Proxy; DDL runs on every shard so Alembic and ActiveRecord migrations work; no pricing; calls to action "Get PgDog" (docs), "For enterprise" and "Talk to us" (a Calendly booking). The live demo is linked only from the Enterprise page.Source
    • Your website"PgDog vs. RDS Proxy" (August 17, 2026): PgDog "doesn't pin connections" and is "2x faster than RDS Proxy" on average, measured with pgbench SELECT 1 at 1, 10 and 100 connections, with results shown only in a chart; the Helm chart is described as production-grade and an AWS ECS Terraform module as experimental; no managed cloud; customer production results are mentioned but there are no case studies yet; no migration steps; it ends with a Calendly call.Source
    • Your websiteEnterprise page: a control plane (real-time metrics, pause, resume and block queries across pods, high availability, SSO), Insights (live and slow queries with automatic query plans, Prometheus and OTEL exporters, alerts with an Incident.io integration) and dedicated support in a Slack channel, with the team there "within 15 minutes" when something breaks; an SLA is mentioned without terms; no prices, plans, compliance information or customer stories; calls to action "Talk to us", "Live demo" and the enterprise docs.Source
  • 09

    PgDog is AGPL-3.0, and the README says the Enterprise edition is offered under a separate license for organizations that do not allow AGPL software. That makes the license itself a sales trigger, but neither the homepage nor the Enterprise page explains it, and in the funding thread readers had to ask what is open source and what is Enterprise.

    Medium impactLow effort First result in 1 month Founder & CEO

    First action

    Ask counsel to approve a one-page FAQ draft.

    How to measure it

    Calls citing licensing

    Now
    –
    Target
    4 a month
    By
    90 days

    Steps

    1. 1

      Collect questions

      From calls, Discord and GitHub issues about the license.

      Founder & CEO 1 day

    2. 2

      Draft

      Plain answers; no legal advice to readers.

      Founder & CEO 1 day

    3. 3

      Counsel review

      Approve every answer.

      Outside counsel 1 week

    4. 4

      Publish

      /license with an email for license questions.

      Founding Software Engineer 2 hours

    5. 5

      Link

      README, installation docs and Enterprise.

      Founding Software Engineer 1 hour

    6. 6

      Track

      Tag license-driven calls.

      Founder & CEO monthly

    First result
    1 month
    Cost
    A few hours of counsel time
    Owner
    Founder & CEO

    Smallest test

    Add a two-line "Need a non-AGPL license?" note to the Enterprise page.

    Why it works

    Publish /license, a short FAQ written with PgDog's counsel and aimed at the open-source review an engineer's legal team will run: which license covers which component, what is open source versus Enterprise (as the founder described it publicly), how to get the commercial license, and who to email with license questions. Link it from the README, the installation page and Enterprise.

    Many companies' open-source policies send AGPL to legal review, and the engineer who wants PgDog cannot answer the questions alone. A clear page turns a blocker into an Enterprise lead.

    Risks and how to handle them

    • Readers treat the FAQ as legal advice

      Say clearly that readers should check with their own counsel.

    Evidence

    • GitHubGitHub (pgdogdev/pgdog, checked November 10, 2026): about 5.6k stars, 312 forks, 134 open issues and 137 open pull requests; licensed AGPL-3.0; the README says the Enterprise edition is available under a separate license for organizations that do not allow AGPL software.Source
    • Your websiteEnterprise page: a control plane (real-time metrics, pause, resume and block queries across pods, high availability, SSO), Insights (live and slow queries with automatic query plans, Prometheus and OTEL exporters, alerts with an Incident.io integration) and dedicated support in a Slack channel, with the team there "within 15 minutes" when something breaks; an SLA is mentioned without terms; no prices, plans, compliance information or customer stories; calls to action "Talk to us", "Live demo" and the enterprise docs.Source
    • Hacker News"PgDog is funded and coming to a database near you": 548 points and 261 comments. Readers asked how PgDog differs from PgBouncer, Citus, Multigres and PlanetScale's Neki, and what is open source versus Enterprise (the founder replied that sharding stays open source, while the control plane and query QoS are Enterprise); objections centred on high availability (PgDog relies on tools such as Patroni or RDS to promote a new primary), modulo-based shard placement making rebalancing hard, and two-phase commit; one commenter asked for more credit to the founder's earlier project, PgCat; users praised stable production use and easy migration from PgBouncer, and asked for binaries and cargo install.Source

This quarter 10

The core plays for the next three months.

  • 07

    RDS Proxy is the rival PgDog targets most directly: a dedicated post, a homepage quote and an RDS IAM auth page. Yet the docs' "Migrating to PgDog" section only covers PgBouncer, and the RDS Proxy post itself gives no migration steps. The reader who has just been convinced has nowhere to go next.

    High impactMedium effort First result in 1 month Founder & CEO

    First action

    Write the settings mapping table from the last customer who switched.

    How to measure it

    RDS Proxy migrations started

    Now
    –
    Target
    10 a quarter
    By
    2 quarters

    Steps

    1. 1

      Map settings

      RDS Proxy options to pgdog.toml.

      Founding Software Engineer 2 days

    2. 2

      Write deployment

      Helm on EKS with IAM auth; ECS marked experimental.

      Founding Software Engineer 3 days

    3. 3

      Write cutover

      Endpoint switch, rollback and checks.

      Founder & CEO 2 days

    4. 4

      Test end to end

      Follow the guide on a fresh AWS account.

      Founding Software Engineer 2 days

    5. 5

      Publish and link

      From the RDS Proxy post, Enterprise and the docs home.

      Founder & CEO 1 day

    6. 6

      Add the help offer

      Architecture review box at the top.

      Founder & CEO 1 hour

    First result
    1 month
    Cost
    Engineer time and a small AWS bill
    Owner
    Founder & CEO

    Smallest test

    Publish the mapping table and cutover checklist first, then expand.

    Why it works

    Publish /migrating-to-pgdog/from-rds-proxy/: how RDS Proxy settings map to pgdog.toml, IAM authentication, deploying with the Helm chart on EKS (and ECS while it is experimental), a cutover by switching the application endpoint, a rollback plan, and what to monitor in the first week. Link it from the RDS Proxy post and the homepage quote.

    People searching for an RDS Proxy migration are already decided. A guide written by the maintainers removes the main risk they are weighing.

    Risks and how to handle them

    • AWS options change

      Date the guide and retest each quarter.

    Evidence

    • Your website"PgDog vs. RDS Proxy" (August 17, 2026): PgDog "doesn't pin connections" and is "2x faster than RDS Proxy" on average, measured with pgbench SELECT 1 at 1, 10 and 100 connections, with results shown only in a chart; the Helm chart is described as production-grade and an AWS ECS Terraform module as experimental; no managed cloud; customer production results are mentioned but there are no case studies yet; no migration steps; it ends with a Calendly call.Source
    • Your docsDocs sitemap (104 URLs, last modified November 2, 2026): a "Migrating to PgDog" section with only an overview and a PgBouncer guide (nothing for RDS Proxy, PgCat, Citus or Supavisor); auth pages for RDS IAM and Azure workload identity, but no deployment guides for AWS RDS or Aurora, Google Cloud SQL or Azure, and no Kubernetes page; a comparison page that covers only PgBouncer and PgCat; a benchmarks page; resharding pages; 12 Enterprise edition pages.Source
    • Your websiteHomepage (checked November 10, 2026): H1 "Scale Postgres n times"; "3M+ queries/s in production"; 17 customer logos including Coinbase, Ramp, Modal, Huntress, Pennylane, PrizePicks and TRM Labs; five short customer quotes, one comparing PgDog favorably with RDS Proxy; DDL runs on every shard so Alembic and ActiveRecord migrations work; no pricing; calls to action "Get PgDog" (docs), "For enterprise" and "Talk to us" (a Calendly booking). The live demo is linked only from the Enterprise page.Source
  • 08

    The funding thread's most common question was how PgDog differs from PgBouncer, Citus, Multigres and PlanetScale's Neki. The docs comparison page covers only PgBouncer and PgCat, and the blog has three one-off "vs." posts. Meanwhile PlanetScale now sells sharded Postgres, Multigres offers a proxy with built-in failover, and Supavisor is a permissively licensed pooler.

    High impactMedium effort First result in 6 weeks Founder & CEO

    First action

    List every alternative named in the funding thread and on recent sales calls.

    How to measure it

    Comparison-sourced calls

    Now
    –
    Target
    6 a month
    By
    90 days

    Steps

    1. 1

      List rivals

      From the HN thread and calls.

      Founder & CEO 1 hour

    2. 2

      Check facts

      Each rival's current docs, license and pricing.

      Contract technical writer 1 week

    3. 3

      Write pages

      Same table on every page, plus when to pick the other one.

      Contract technical writer 2 weeks

    4. 4

      Founder review

      Technical accuracy and tone.

      Founder & CEO 2 days

    5. 5

      Publish the hub

      /compare, linked from docs and the homepage footer.

      Founding Software Engineer 1 day

    6. 6

      Refresh

      Recheck each page every quarter.

      Contract technical writer quarterly

    First result
    6 weeks
    Cost
    A contract writer, about $3,000
    Owner
    Founder & CEO

    Smallest test

    Publish the Supavisor page first, since no current page covers it.

    Why it works

    Build /compare with one fair, dated page per alternative: what each is (proxy, extension, managed service), where it runs (your RDS, your Kubernetes, their cloud), license, pooling, read/write split, sharding, resharding, failover and what migration takes. Say plainly where the alternative is the better choice. Fold the three existing posts in and link the docs comparison page to the hub.

    Comparison searches come from engineers in an active evaluation, and honest pages are what they share with their team. Search engines and AI assistants also use these pages to explain the differences.

    Risks and how to handle them

    • Claims about rivals go stale or are disputed

      Cite each rival's own docs, date every page and correct quickly.

    Evidence

    • Hacker News"PgDog is funded and coming to a database near you": 548 points and 261 comments. Readers asked how PgDog differs from PgBouncer, Citus, Multigres and PlanetScale's Neki, and what is open source versus Enterprise (the founder replied that sharding stays open source, while the control plane and query QoS are Enterprise); objections centred on high availability (PgDog relies on tools such as Patroni or RDS to promote a new primary), modulo-based shard placement making rebalancing hard, and two-phase commit; one commenter asked for more credit to the founder's earlier project, PgCat; users praised stable production use and easy migration from PgBouncer, and asked for binaries and cargo install.Source
    • Your docsDocs sitemap (104 URLs, last modified November 2, 2026): a "Migrating to PgDog" section with only an overview and a PgBouncer guide (nothing for RDS Proxy, PgCat, Citus or Supavisor); auth pages for RDS IAM and Azure workload identity, but no deployment guides for AWS RDS or Aurora, Google Cloud SQL or Azure, and no Kubernetes page; a comparison page that covers only PgBouncer and PgCat; a benchmarks page; resharding pages; 12 Enterprise edition pages.Source
    • Competitor researchRivals' own pages: PlanetScale Postgres, managed Postgres on AWS, GCP and Azure from $5 a month, with Neki, its sharded Postgres, now available, plus guided zero-downtime migrations; Multigres, a horizontally scalable Postgres architecture with its own gateway, pooler, Raft-based failover and a Kubernetes operator.Source
    • Competitor researchRivals' own pages: Supavisor, "a cloud-native, multi-tenant Postgres connection pooler" (Apache-2.0, about 2.3k GitHub stars) claiming millions of client connections per cluster; Citus, a distributed Postgres extension, "100% open source" and part of Microsoft, aimed at multi-tenant SaaS and real-time analytics.Source
  • 10

    PgBouncer users are PgDog's easiest converts (Hacker News users praised the easy migration), but the migration guide is a set of manual mapping tables, with a separate list of PgBouncer features that have no equivalent. Every migrating team does the same translation by hand.

    High impactMedium effort First result in 1 month Founding Software Engineer

    First action

    Turn the guide's mapping tables into a test fixture.

    How to measure it

    Converter uses

    Now
    –
    Target
    300 a quarter
    By
    2 quarters

    Steps

    1. 1

      Encode the tables

      Guide mappings as data and tests.

      Founding Software Engineer 2 days

    2. 2

      Build the CLI

      pgdog convert, with warnings.

      Founding Software Engineer 1 week

    3. 3

      Build the web page

      Runs fully in the browser.

      Founding Software Engineer 3 days

    4. 4

      Link it

      Top of the PgBouncer guide and the vs. PgBouncer post.

      Founder & CEO 1 hour

    5. 5

      Count warnings

      An opt-in count of which unsupported settings appear.

      Founding Software Engineer 2 days

    6. 6

      Announce

      Release notes, Discord and Hacker News.

      Founder & CEO 1 day

    First result
    1 month
    Cost
    About two engineer-weeks
    Owner
    Founding Software Engineer

    Smallest test

    Ship the CLI only and mention it in one release note.

    Why it works

    Add a "pgdog convert" subcommand, plus a small browser page in the docs, that reads pgbouncer.ini and userlist.txt and writes pgdog.toml and users.toml. It warns about each unsupported setting (auth_query, reserve pools, UNIX sockets, LDAP, HBA files, statement pooling) and links to the workaround. Never upload the file: in the browser, convert it locally.

    A tool that turns an hour of careful mapping into ten seconds removes the first step of switching. The warnings also show which missing features block the most migrations, which feeds the roadmap.

    Risks and how to handle them

    • Edge-case configs convert wrongly

      Show a diff and ask users to report failures with one click to GitHub.

    Evidence

    • Your docsPgBouncer migration guide: manual mapping tables from pgbouncer.ini and userlist.txt to pgdog.toml and users.toml, with no conversion tool; lists PgBouncer features with no equivalent (auth_query, reserve pools, UNIX sockets, LDAP, HBA files, statement pooling); no offer of migration help or Enterprise support.Source
    • Hacker News"PgDog is funded and coming to a database near you": 548 points and 261 comments. Readers asked how PgDog differs from PgBouncer, Citus, Multigres and PlanetScale's Neki, and what is open source versus Enterprise (the founder replied that sharding stays open source, while the control plane and query QoS are Enterprise); objections centred on high availability (PgDog relies on tools such as Patroni or RDS to promote a new primary), modulo-based shard placement making rebalancing hard, and two-phase commit; one commenter asked for more credit to the founder's earlier project, PgCat; users praised stable production use and easy migration from PgBouncer, and asked for binaries and cargo install.Source
    • HiringY Combinator (Spring 2025 batch, team of 3, San Francisco): an open Founding Software Engineer role, $150K-$225K and 1-3% equity, Rust and Postgres, roughly 30% bug fixes, 60% new features and 10% infrastructure; PgDog is "used by dozens of companies, large and small"; the roadmap names an advanced OLAP query engine for sharded Postgres and in-place data redistribution to make resharding push-button.Source
  • 11

    PgDog's own distribution post argues that CI and staging are where engineers try PgDog safely, and it includes a hand-written GitHub Actions example that runs an app's test suite through PgDog. That example lives only in a blog post, not on the GitHub Marketplace where engineers search for actions.

    Medium impactLow effort First result in 1 month Founding Software Engineer

    First action

    Move the blog example into its own repository with a README.

    How to measure it

    Public repos using setup-pgdog

    Now
    –
    Target
    100
    By
    2 quarters

    Steps

    1. 1

      Package

      Action repository from the blog example.

      Founding Software Engineer 2 days

    2. 2

      Add modes

      Pooling, read/write split, two shards.

      Founding Software Engineer 3 days

    3. 3

      Test

      Against Rails and Django sample apps.

      Founding Software Engineer 2 days

    4. 4

      List it

      GitHub Marketplace, with a clear description.

      Founding Software Engineer 1 hour

    5. 5

      Link

      README, installation docs, release notes.

      Founder & CEO 1 hour

    6. 6

      Track

      Dependents and Marketplace installs.

      Founder & CEO monthly

    First result
    1 month
    Cost
    About one engineer-week
    Owner
    Founding Software Engineer

    Smallest test

    Publish the action with transaction pooling only.

    Why it works

    Package the example as a versioned action (setup-pgdog) that starts PgDog in front of the job's Postgres service, with options for transaction pooling, read/write split and a two-shard mode. List it on the GitHub Marketplace, link it from the installation docs and the README, and add a line in its output pointing to the docs.

    Running the test suite through PgDog is a zero-risk trial that surfaces compatibility issues early. Once it is in CI, moving to staging and production is the natural next step, and every repository that uses the action is a visible sign of adoption.

    Risks and how to handle them

    • Maintenance across PgDog versions

      Pin to tagged releases and test the action in PgDog's own CI.

    Evidence

    • Your website"The 3 D's of software: distribution, distribution, distribution" (November 4, 2026): 3.69M downloads of the open-source version, 5.16M of PgDog Enterprise Edition and 323k of the EE control plane; about 500 issues in a year; "thousands of engineers" test PgDog daily; no waiting list, contact form or credit card, and the EE image and Helm chart are public; a GitHub Actions example runs an app's test suite through PgDog; no marketplace listing is mentioned.Source
    • GitHubGitHub (pgdogdev/pgdog, checked November 10, 2026): about 5.6k stars, 312 forks, 134 open issues and 137 open pull requests; licensed AGPL-3.0; the README says the Enterprise edition is available under a separate license for organizations that do not allow AGPL software.Source
  • 12

    PgDog says the Enterprise edition image has been downloaded 5.16M times and the control plane 323k times, more than the open-source image, because both are public with no sign-up. That is great for adoption, but PgDog cannot tell which companies are running Enterprise features in production and might need support or a license.

    High impactMedium effort First result in 1 quarter Founder & CEO

    First action

    Decide what registration unlocks that users actually want (upgrade notices are the safest start).

    How to measure it

    Registered clusters

    Now
    –
    Target
    50
    By
    2 quarters

    Steps

    1. 1

      Choose the value

      Upgrade and security notices, alert email routing.

      Founder & CEO 1 day

    2. 2

      Design the prompt

      One dismissible card in the control plane.

      Founding Software Engineer 2 days

    3. 3

      Build it

      Company, contact, cluster size; nothing collected without consent.

      Founding Software Engineer 1 week

    4. 4

      Write the privacy note

      Exactly what is sent, in the docs and the UI.

      Founder & CEO 1 day

    5. 5

      Review weekly

      Offer reviews to production-scale clusters.

      Founder & CEO weekly

    6. 6

      Measure

      Registrations and resulting calls.

      Founder & CEO monthly

    First result
    1 quarter
    Cost
    About two engineer-weeks
    Owner
    Founder & CEO

    Smallest test

    Add an "Email me upgrade notices" link in the control plane footer and count signups.

    Why it works

    Add an optional "Register this cluster" prompt in the control plane UI, with a real reason to accept: email alerts, security and upgrade notices for the version in use, and a direct line to the team. Never gate a feature behind it. Registered clusters go into a simple list the founder reviews weekly, offering an architecture review to the ones with production-sized traffic.

    Open-core companies grow revenue by finding the teams already getting value from the product. An optional, useful registration keeps the no-gatekeeping promise while turning anonymous downloads into conversations.

    Risks and how to handle them

    • Users see it as a step away from "everything public"

      Keep it optional, explain it in a release note and never gate features.

    • Download counts include automated CI pulls

      Judge success by registered production clusters, not downloads.

    Evidence

    • Your website"The 3 D's of software: distribution, distribution, distribution" (November 4, 2026): 3.69M downloads of the open-source version, 5.16M of PgDog Enterprise Edition and 323k of the EE control plane; about 500 issues in a year; "thousands of engineers" test PgDog daily; no waiting list, contact form or credit card, and the EE image and Helm chart are public; a GitHub Actions example runs an app's test suite through PgDog; no marketplace listing is mentioned.Source
    • Your websiteEnterprise page: a control plane (real-time metrics, pause, resume and block queries across pods, high availability, SSO), Insights (live and slow queries with automatic query plans, Prometheus and OTEL exporters, alerts with an Incident.io integration) and dedicated support in a Slack channel, with the team there "within 15 minutes" when something breaks; an SLA is mentioned without terms; no prices, plans, compliance information or customer stories; calls to action "Talk to us", "Live demo" and the enterprise docs.Source
  • 13

    High availability was the loudest objection in the funding thread: commenters said HA, not scale, is the real Postgres pain, and pointed out that PgDog relies on tools such as Patroni or RDS to promote a new primary. Meanwhile the homepage says PgDog detects failovers and moves writes without config changes, and Multigres advertises built-in Raft-based failover.

    Medium impactMedium effort First result in 1 month Founding Software Engineer

    First action

    Run one forced failover on RDS Multi-AZ behind PgDog and record the timings.

    How to measure it

    Calls where HA is the blocker

    Now
    –
    Target
    -50%
    By
    2 quarters

    Steps

    1. 1

      Build the Patroni lab

      Three nodes behind PgDog.

      Founding Software Engineer 2 days

    2. 2

      Build the RDS lab

      Multi-AZ behind PgDog on EKS.

      Founding Software Engineer 2 days

    3. 3

      Force failovers

      Ten runs each, recording client errors and recovery.

      Founding Software Engineer 2 days

    4. 4

      Write the page

      Diagrams, settings, results and limits.

      Founding Software Engineer 3 days

    5. 5

      Publish the scripts

      So anyone can rerun them.

      Founding Software Engineer 1 day

    6. 6

      Share

      Reply in the original discussion threads and the digest.

      Founder & CEO 1 day

    First result
    1 month
    Cost
    Engineer time and a small cloud bill
    Owner
    Founding Software Engineer

    Smallest test

    Publish the RDS Multi-AZ result alone.

    Why it works

    Write one docs page with two tested designs: PgDog in front of a Patroni cluster, and PgDog in front of RDS Multi-AZ. For each, show the diagram, the PgDog settings, and measured results from a forced failover (seconds of write errors, how fast reads recover, what clients see). Be explicit about what PgDog does and what the HA tool does.

    A measured, honest answer turns the top objection into proof. It also helps the Enterprise SLA conversation, because buyers can see what "within 15 minutes" is backing up.

    Risks and how to handle them

    • Results show a weakness

      Publish them anyway with the fix planned; honesty is the point.

    Evidence

    • Hacker News"PgDog is funded and coming to a database near you": 548 points and 261 comments. Readers asked how PgDog differs from PgBouncer, Citus, Multigres and PlanetScale's Neki, and what is open source versus Enterprise (the founder replied that sharding stays open source, while the control plane and query QoS are Enterprise); objections centred on high availability (PgDog relies on tools such as Patroni or RDS to promote a new primary), modulo-based shard placement making rebalancing hard, and two-phase commit; one commenter asked for more credit to the founder's earlier project, PgCat; users praised stable production use and easy migration from PgBouncer, and asked for binaries and cargo install.Source
    • Competitor researchRivals' own pages: PlanetScale Postgres, managed Postgres on AWS, GCP and Azure from $5 a month, with Neki, its sharded Postgres, now available, plus guided zero-downtime migrations; Multigres, a horizontally scalable Postgres architecture with its own gateway, pooler, Raft-based failover and a Kubernetes operator.Source
    • Your websiteEnterprise page: a control plane (real-time metrics, pause, resume and block queries across pods, high availability, SSO), Insights (live and slow queries with automatic query plans, Prometheus and OTEL exporters, alerts with an Incident.io integration) and dedicated support in a Slack channel, with the team there "within 15 minutes" when something breaks; an SLA is mentioned without terms; no prices, plans, compliance information or customer stories; calls to action "Talk to us", "Live demo" and the enterprise docs.Source
  • 14

    In the funding thread, an expert commenter objected that modulo-based shard placement makes rebalancing hard. PgDog's docs do have resharding pages, and the open job post names in-place data redistribution (push-button resharding) as a top roadmap item. What is missing is proof of how resharding works today, with times.

    Medium impactMedium effort First result in 6 weeks Founder & CEO

    First action

    Choose the dataset and the load generator.

    How to measure it

    Sharding-docs visits from the walkthrough

    Now
    –
    Target
    2,000
    By
    2 quarters

    Steps

    1. 1

      Set up

      Dataset, load and monitoring.

      Founding Software Engineer 3 days

    2. 2

      Reshard

      1 to 2 to 4 shards, recording each phase.

      Founding Software Engineer 3 days

    3. 3

      Write

      Steps, timings, limits and the roadmap.

      Founder & CEO 3 days

    4. 4

      Publish the scripts

      A repository anyone can rerun.

      Founding Software Engineer 1 day

    5. 5

      Launch

      Blog, Hacker News and Postgres communities.

      Founder & CEO 1 day

    6. 6

      Update

      Rerun when in-place redistribution ships.

      Founding Software Engineer when shipped

    First result
    6 weeks
    Cost
    Engineer time and a cloud bill of a few hundred dollars
    Owner
    Founder & CEO

    Smallest test

    Publish the one-to-two-shard run first.

    Why it works

    Take a public dataset of a few hundred GB, run a realistic write load, and reshard from one to two to four shards with PgDog's logical-replication resharding. Publish the steps, the elapsed time, write latency during the move, and the cutover pause. Explain shard placement and how in-place redistribution will change it, and update the post when that ships.

    "What happens when I need more shards?" is the question that decides whether a team will commit to sharding. Showing the answer with numbers is more persuasive than a feature list, and it gives the roadmap item a launch story.

    Risks and how to handle them

    • Today's resharding looks slow

      Present it as the baseline the roadmap improves.

    Evidence

    • Hacker News"PgDog is funded and coming to a database near you": 548 points and 261 comments. Readers asked how PgDog differs from PgBouncer, Citus, Multigres and PlanetScale's Neki, and what is open source versus Enterprise (the founder replied that sharding stays open source, while the control plane and query QoS are Enterprise); objections centred on high availability (PgDog relies on tools such as Patroni or RDS to promote a new primary), modulo-based shard placement making rebalancing hard, and two-phase commit; one commenter asked for more credit to the founder's earlier project, PgCat; users praised stable production use and easy migration from PgBouncer, and asked for binaries and cargo install.Source
    • HiringY Combinator (Spring 2025 batch, team of 3, San Francisco): an open Founding Software Engineer role, $150K-$225K and 1-3% equity, Rust and Postgres, roughly 30% bug fixes, 60% new features and 10% infrastructure; PgDog is "used by dozens of companies, large and small"; the roadmap names an advanced OLAP query engine for sharded Postgres and in-place data redistribution to make resharding push-button.Source
    • Your docsDocs sitemap (104 URLs, last modified November 2, 2026): a "Migrating to PgDog" section with only an overview and a PgBouncer guide (nothing for RDS Proxy, PgCat, Citus or Supavisor); auth pages for RDS IAM and Azure workload identity, but no deployment guides for AWS RDS or Aurora, Google Cloud SQL or Azure, and no Kubernetes page; a comparison page that covers only PgBouncer and PgCat; a benchmarks page; resharding pages; 12 Enterprise edition pages.Source
  • 15

    The RDS Proxy post says PgDog is "2x faster" on average, but the method was pgbench SELECT 1 at 1, 10 and 100 connections, and the numbers appear only in a chart. Supavisor publishes connection-count claims, and the Hacker News audience pushed back on other unsupported numbers. Skeptical engineers want to rerun benchmarks themselves.

    Medium impactMedium effort First result in 1 month Founding Software Engineer

    First action

    Move the RDS Proxy benchmark scripts into a public repository.

    How to measure it

    Links and mentions

    Now
    –
    Target
    10
    By
    2 quarters

    Steps

    1. 1

      Publish scripts

      The existing benchmark, as a repository.

      Founding Software Engineer 1 day

    2. 2

      Add workloads

      TPC-B, prepared statements, idle clients.

      Founding Software Engineer 3 days

    3. 3

      Add rivals

      PgBouncer and Supavisor on the same hardware.

      Founding Software Engineer 3 days

    4. 4

      Run and record

      Hardware, versions, dates, raw output.

      Founding Software Engineer 2 days

    5. 5

      Update the docs

      Tables on the benchmarks page.

      Founding Software Engineer 1 day

    6. 6

      Invite review

      Ask other maintainers to check their settings.

      Founder & CEO 2 weeks

    First result
    1 month
    Cost
    Engineer time and a small cloud bill
    Owner
    Founding Software Engineer

    Smallest test

    Add the existing results as a table to the RDS Proxy post.

    Why it works

    Publish a benchmark repository with Terraform and scripts that compare PgDog, PgBouncer, RDS Proxy and Supavisor on the same hardware, using a realistic workload (pgbench TPC-B, prepared statements, many idle clients) as well as SELECT 1. Put the result tables in the docs benchmarks page with hardware, versions and dates, and invite pull requests from other maintainers.

    Numbers anyone can reproduce get cited in comparison threads and evaluations. Numbers in a chart get argued with.

    Risks and how to handle them

    • A rival's setup is accused of being unfair

      Use their recommended settings and accept fixes by pull request.

    Evidence

    • Your website"PgDog vs. RDS Proxy" (August 17, 2026): PgDog "doesn't pin connections" and is "2x faster than RDS Proxy" on average, measured with pgbench SELECT 1 at 1, 10 and 100 connections, with results shown only in a chart; the Helm chart is described as production-grade and an AWS ECS Terraform module as experimental; no managed cloud; customer production results are mentioned but there are no case studies yet; no migration steps; it ends with a Calendly call.Source
    • Competitor researchRivals' own pages: Supavisor, "a cloud-native, multi-tenant Postgres connection pooler" (Apache-2.0, about 2.3k GitHub stars) claiming millions of client connections per cluster; Citus, a distributed Postgres extension, "100% open source" and part of Microsoft, aimed at multi-tenant SaaS and real-time analytics.Source
    • Hacker News"PgDog is funded and coming to a database near you": 548 points and 261 comments. Readers asked how PgDog differs from PgBouncer, Citus, Multigres and PlanetScale's Neki, and what is open source versus Enterprise (the founder replied that sharding stays open source, while the control plane and query QoS are Enterprise); objections centred on high availability (PgDog relies on tools such as Patroni or RDS to promote a new primary), modulo-based shard placement making rebalancing hard, and two-phase commit; one commenter asked for more credit to the founder's earlier project, PgCat; users praised stable production use and easy migration from PgBouncer, and asked for binaries and cargo install.Source
  • 16

    PgDog is designed for managed Postgres such as AWS RDS, and its Enterprise edition exists to make AWS deployment easier. But the 104-page docs have no deployment guide for RDS or Aurora, Google Cloud SQL or Azure, and no Kubernetes page, even though the Helm chart is the production-grade install. Only the auth pages (RDS IAM, Azure workload identity) mention a cloud.

    Medium impactMedium effort First result in 6 weeks Contract technical writer

    First action

    Write the EKS + RDS guide first, since most published customers run on AWS.

    How to measure it

    Deploy-guide visits

    Now
    –
    Target
    5,000 a quarter
    By
    2 quarters

    Steps

    1. 1

      Outline

      One template for all four guides.

      Contract technical writer 1 day

    2. 2

      EKS + RDS

      Tested end to end.

      Contract technical writer 1 week

    3. 3

      Kubernetes

      Helm values explained.

      Contract technical writer 3 days

    4. 4

      GKE and AKS

      Cloud SQL and Azure Database.

      Contract technical writer 2 weeks

    5. 5

      Technical review

      Each guide checked by an engineer.

      Founding Software Engineer 1 day each

    6. 6

      Link

      Docs home, installation page and README.

      Founder & CEO 1 hour

    First result
    6 weeks
    Cost
    A contract writer, about $4,000, plus cloud costs
    Owner
    Contract technical writer

    Smallest test

    Publish the EKS + RDS guide and watch its search traffic for a month.

    Why it works

    Write four guides under one "Deploy" section: EKS + RDS/Aurora (Helm, IAM auth, Multi-AZ), GKE + Cloud SQL, AKS + Azure Database for PostgreSQL, and generic Kubernetes with the Helm chart values explained. Each ends with a production checklist and the Enterprise support offer.

    Engineers search for "<tool> on <their cloud>". A guide for their exact setup is often the difference between "try it this sprint" and "later".

    Risks and how to handle them

    • Guides fall out of date with releases

      Test them in CI against the Helm chart.

    Evidence

    • Your docsDocs sitemap (104 URLs, last modified November 2, 2026): a "Migrating to PgDog" section with only an overview and a PgBouncer guide (nothing for RDS Proxy, PgCat, Citus or Supavisor); auth pages for RDS IAM and Azure workload identity, but no deployment guides for AWS RDS or Aurora, Google Cloud SQL or Azure, and no Kubernetes page; a comparison page that covers only PgBouncer and PgCat; a benchmarks page; resharding pages; 12 Enterprise edition pages.Source
    • Your websiteFunding post (June 10, 2026): a $5.5M seed from Basis Set, YC, Pioneer Fund and others; over 2M queries per second in production across dozens of deployments; more than 20 TB sharded; over 1.4M Docker pulls; a three-person team; new releases every Thursday; an Enterprise edition to make AWS deployment easier, with SLA-backed support.Source
    • Your website"PgDog vs. RDS Proxy" (August 17, 2026): PgDog "doesn't pin connections" and is "2x faster than RDS Proxy" on average, measured with pgbench SELECT 1 at 1, 10 and 100 connections, with results shown only in a chart; the Helm chart is described as production-grade and an AWS ECS Terraform module as experimental; no managed cloud; customer production results are mentioned but there are no case studies yet; no migration steps; it ends with a Calendly call.Source
  • 17

    PgDog's homepage says DDL runs on every shard so Alembic and ActiveRecord migrations work out of the box, and one of its best-known posts is "Sharding a real Rails app". The teams most likely to hit Postgres limits without wanting to rewrite their app are on these frameworks, but the docs have no ORM-specific pages.

    Medium impactMedium effort First result in 1 quarter Founder & CEO

    First action

    Turn "Sharding a real Rails app" into a docs guide and submit a talk proposal.

    How to measure it

    Framework-sourced installs

    Now
    –
    Target
    2 talks accepted; 3 guides live
    By
    2 quarters

    Steps

    1. 1

      Rails guide

      From the existing post.

      Founder & CEO 3 days

    2. 2

      Django guide

      Pooling, replicas, sharding keys.

      Contract technical writer 1 week

    3. 3

      SQLAlchemy guide

      Including Alembic migrations.

      Contract technical writer 1 week

    4. 4

      Submit talks

      Rails, Python and Postgres events.

      Founder & CEO 2 days

    5. 5

      Pitch newsletters

      Framework and Postgres weeklies.

      Founder & CEO 1 day

    6. 6

      Measure

      Referral traffic and installs.

      Founder & CEO monthly

    First result
    1 quarter
    Cost
    Writer time and conference travel
    Owner
    Founder & CEO

    Smallest test

    Publish the Rails guide and share it in one Rails newsletter.

    Why it works

    Write three framework guides (Rails/ActiveRecord, Django, SQLAlchemy/Alembic) covering pooling settings, prepared statements, read replicas and sharding keys. Pitch a talk on sharding a real Rails app to Rails and Python conferences and Postgres events, and offer the guides to framework newsletters.

    Framework communities trust practical guides from people who solved their problem. One accepted talk reaches thousands of the exact engineers who will need PgDog.

    Risks and how to handle them

    • Travel takes the founder away from customers

      Prefer recorded talks and one event a quarter.

    Evidence

    • Your websiteHomepage (checked November 10, 2026): H1 "Scale Postgres n times"; "3M+ queries/s in production"; 17 customer logos including Coinbase, Ramp, Modal, Huntress, Pennylane, PrizePicks and TRM Labs; five short customer quotes, one comparing PgDog favorably with RDS Proxy; DDL runs on every shard so Alembic and ActiveRecord migrations work; no pricing; calls to action "Get PgDog" (docs), "For enterprise" and "Talk to us" (a Calendly booking). The live demo is linked only from the Enterprise page.Source
    • Your websiteBlog (checked November 10, 2026): 23 posts from March 2025 to November 2026, including "PgDog vs. PgBouncer", "PgDog vs. Citus", "PgDog vs. RDS Proxy", "Sharding a real Rails app", "Sharding pgvector" and "Multi-tenant Postgres can be easy"; no newsletter signup; a valid RSS feed exists at /feed.xml but the blog page does not link to it; a sampled post ends with a link to the installation docs and no enterprise or support offer.Source
    • Your docsDocs sitemap (104 URLs, last modified November 2, 2026): a "Migrating to PgDog" section with only an overview and a PgBouncer guide (nothing for RDS Proxy, PgCat, Citus or Supavisor); auth pages for RDS IAM and Azure workload identity, but no deployment guides for AWS RDS or Aurora, Google Cloud SQL or Azure, and no Kubernetes page; a comparison page that covers only PgBouncer and PgCat; a benchmarks page; resharding pages; 12 Enterprise edition pages.Source

Big bets 3

Larger plays that can change the trajectory.

  • 18

    PgDog promises architecture reviews, migration help and a response "within 15 minutes" when something breaks, but the company is three people hiring a fourth engineer, and that engineer's time is mostly features and bug fixes. Every new Enterprise customer adds support load, and enterprise sales cycles are long, as a commenter noted in the funding thread.

    High impactHigh effort First result in 2 quarters Founder & CEO

    First action

    List ten Postgres consultancies whose clients run RDS at scale and contact three.

    How to measure it

    Partner-sourced deals

    Now
    –
    Target
    4
    By
    3 quarters

    Steps

    1. 1

      Shortlist

      Ten Postgres consultancies.

      Founder & CEO 1 week

    2. 2

      Define terms

      Referral fee or resale margin, training and escalation.

      Founder & CEO 2 weeks

    3. 3

      Train

      A one-day workshop and a certification checklist.

      Founding Software Engineer 1 month

    4. 4

      Publish

      /partners page and docs links.

      Founder & CEO 1 day

    5. 5

      Share leads

      Send migration-heavy leads to partners.

      Founder & CEO ongoing

    6. 6

      Review

      Quality and deals each quarter.

      Founder & CEO quarterly

    First result
    2 quarters
    Cost
    Founder time; referral fees from revenue
    Owner
    Founder & CEO

    Smallest test

    Co-deliver one migration with one consultancy.

    Why it works

    Recruit three to five Postgres consultancies as certified PgDog partners. Partners run migrations and architecture reviews, PgDog trains them, lists them on a /partners page, sends them leads that need hands-on help, and keeps the Enterprise license and escalations. Partners earn the services revenue, and PgDog earns the license and broader reach into the consultancies' clients.

    Consultancies are already in the room when a company outgrows Postgres. Giving them a reason to recommend PgDog adds sales and delivery capacity without hiring.

    Risks and how to handle them

    • Poor partner work hurts PgDog's reputation

      Certify partners and review their first migrations.

    Builds on

    Evidence

    • Your websiteEnterprise page: a control plane (real-time metrics, pause, resume and block queries across pods, high availability, SSO), Insights (live and slow queries with automatic query plans, Prometheus and OTEL exporters, alerts with an Incident.io integration) and dedicated support in a Slack channel, with the team there "within 15 minutes" when something breaks; an SLA is mentioned without terms; no prices, plans, compliance information or customer stories; calls to action "Talk to us", "Live demo" and the enterprise docs.Source
    • HiringY Combinator (Spring 2025 batch, team of 3, San Francisco): an open Founding Software Engineer role, $150K-$225K and 1-3% equity, Rust and Postgres, roughly 30% bug fixes, 60% new features and 10% infrastructure; PgDog is "used by dozens of companies, large and small"; the roadmap names an advanced OLAP query engine for sharded Postgres and in-place data redistribution to make resharding push-button.Source
    • Hacker News"PgDog is funded and coming to a database near you": 548 points and 261 comments. Readers asked how PgDog differs from PgBouncer, Citus, Multigres and PlanetScale's Neki, and what is open source versus Enterprise (the founder replied that sharding stays open source, while the control plane and query QoS are Enterprise); objections centred on high availability (PgDog relies on tools such as Patroni or RDS to promote a new primary), modulo-based shard placement making rebalancing hard, and two-phase commit; one commenter asked for more credit to the founder's earlier project, PgCat; users praised stable production use and easy migration from PgBouncer, and asked for binaries and cargo install.Source
  • 19

    PgDog is built for AWS RDS users, its Enterprise edition exists to make AWS deployment easier, and RDS Proxy is the product it replaces, yet no marketplace listing is mentioned anywhere. Today buying means a call, a contract and a new vendor in procurement.

    High impactHigh effort First result in 2 quarters Founder & CEO

    First action

    Read the AWS Marketplace seller requirements and estimate the listing work.

    How to measure it

    Marketplace deals

    Now
    –
    Target
    3
    By
    3 quarters

    Steps

    1. 1

      Check requirements

      Seller registration, tax and banking.

      Founder & CEO 1 week

    2. 2

      Package

      Container product for EKS from the Helm chart.

      Founding Software Engineer 3 weeks

    3. 3

      Set pricing

      Matching the published Enterprise anchors.

      Founder & CEO 1 week

    4. 4

      Publish the listing

      Description, docs and support terms.

      Founder & CEO 2 weeks

    5. 5

      Use private offers

      For negotiated deals.

      Founder & CEO ongoing

    6. 6

      Promote

      Enterprise page, RDS guide and calls.

      Founder & CEO 1 day

    First result
    2 quarters
    Cost
    Marketplace fees on transactions, plus about a month of work
    Owner
    Founder & CEO

    Smallest test

    Close one existing deal as an AWS Marketplace private offer.

    Why it works

    List PgDog Enterprise on AWS Marketplace with private offers for negotiated deals and a container listing that deploys the Helm chart to EKS. Link the listing from the Enterprise page and the RDS Proxy migration guide, and tell RDS-heavy prospects they can buy through their existing AWS account.

    Buying through an AWS account avoids onboarding a new vendor, which can shorten procurement at the large companies PgDog already counts as users. The listing also makes PgDog easy to find for engineers browsing for RDS tools.

    Risks and how to handle them

    • Listing work distracts a small team

      Start with private offers only, then add the public listing.

    Builds on

    Evidence

    • Your websiteFunding post (June 10, 2026): a $5.5M seed from Basis Set, YC, Pioneer Fund and others; over 2M queries per second in production across dozens of deployments; more than 20 TB sharded; over 1.4M Docker pulls; a three-person team; new releases every Thursday; an Enterprise edition to make AWS deployment easier, with SLA-backed support.Source
    • Your website"The 3 D's of software: distribution, distribution, distribution" (November 4, 2026): 3.69M downloads of the open-source version, 5.16M of PgDog Enterprise Edition and 323k of the EE control plane; about 500 issues in a year; "thousands of engineers" test PgDog daily; no waiting list, contact form or credit card, and the EE image and Helm chart are public; a GitHub Actions example runs an app's test suite through PgDog; no marketplace listing is mentioned.Source
    • Your website"PgDog vs. RDS Proxy" (August 17, 2026): PgDog "doesn't pin connections" and is "2x faster than RDS Proxy" on average, measured with pgbench SELECT 1 at 1, 10 and 100 connections, with results shown only in a chart; the Helm chart is described as production-grade and an AWS ECS Terraform module as experimental; no managed cloud; customer production results are mentioned but there are no case studies yet; no migration steps; it ends with a Calendly call.Source
  • 20

    PgDog has no managed cloud, so customers deploy and run it themselves: the Helm chart is production-grade, but the ECS Terraform module is still experimental. The funding post says the Enterprise edition is meant to make AWS deployment easier, and rivals such as PlanetScale offer fully managed Postgres from $5 a month.

    High impactHigh effort First result in 2 quarters Founding Software Engineer

    First action

    List the manual steps a new Enterprise customer took on AWS last month.

    How to measure it

    Days to production

    Now
    –
    Target
    -50%
    By
    3 quarters

    Steps

    1. 1

      Map the steps

      From the last three AWS rollouts.

      Founding Software Engineer 1 week

    2. 2

      Harden ECS

      Take the Terraform module out of experimental.

      Founding Software Engineer 1 month

    3. 3

      Add EKS

      Same module, Helm underneath.

      Founding Software Engineer 3 weeks

    4. 4

      Add CloudFormation

      For non-Terraform teams.

      Founding Software Engineer 2 weeks

    5. 5

      Upgrade command

      Follows weekly releases safely.

      Founding Software Engineer 2 weeks

    6. 6

      Pilot

      Two new customers, measured end to end.

      Founder & CEO 1 month

    7. 7

      Launch

      Docs, blog and the Marketplace listing.

      Founder & CEO 1 week

    First result
    2 quarters
    Cost
    About a quarter of one engineer's time
    Owner
    Founding Software Engineer

    Smallest test

    Make the ECS module the default in the RDS Proxy migration guide and collect feedback from three users.

    Why it works

    Ship a supported Terraform module (and a CloudFormation template for teams without Terraform) that deploys PgDog Enterprise, the control plane and monitoring into the customer's VPC next to RDS, across availability zones, with IAM auth wired up and sensible defaults. Promote the ECS path out of experimental, and give it an upgrade command that follows the Thursday releases.

    It closes most of the convenience gap with managed services while the data stays in the customer's account, which is PgDog's advantage over moving to a new database provider.

    Risks and how to handle them

    • Supporting many AWS setups

      Support one reference layout and document the rest as best effort.

    Builds on

    Evidence

    • Your website"PgDog vs. RDS Proxy" (August 17, 2026): PgDog "doesn't pin connections" and is "2x faster than RDS Proxy" on average, measured with pgbench SELECT 1 at 1, 10 and 100 connections, with results shown only in a chart; the Helm chart is described as production-grade and an AWS ECS Terraform module as experimental; no managed cloud; customer production results are mentioned but there are no case studies yet; no migration steps; it ends with a Calendly call.Source
    • Your websiteFunding post (June 10, 2026): a $5.5M seed from Basis Set, YC, Pioneer Fund and others; over 2M queries per second in production across dozens of deployments; more than 20 TB sharded; over 1.4M Docker pulls; a three-person team; new releases every Thursday; an Enterprise edition to make AWS deployment easier, with SLA-backed support.Source
    • Competitor researchRivals' own pages: PlanetScale Postgres, managed Postgres on AWS, GCP and Azure from $5 a month, with Neki, its sharded Postgres, now available, plus guided zero-downtime migrations; Multigres, a horizontally scalable Postgres architecture with its own gateway, pooler, Raft-based failover and a Kubernetes operator.Source

Wildcards 2

Unexpected experiments, each with a cheap way to test it.

  • 21

    In the funding thread, a commenter said the founder's earlier project, PgCat, should be credited more prominently. PgDog's own docs comparison page sets PgDog against PgCat feature by feature, yet the "Migrating to PgDog" section has no PgCat guide. PgCat users are the closest possible audience: same author, same problem.

    Medium impactLow effort First result in 1 month Founder & CEO

    First action

    Draft the config mapping from PgCat's TOML to pgdog.toml.

    How to measure it

    PgCat-guide visits

    Now
    –
    Target
    1,000
    By
    2 quarters

    Steps

    1. 1

      Map configs

      PgCat settings to pgdog.toml.

      Founding Software Engineer 2 days

    2. 2

      Write the guide

      Steps, differences and cutover.

      Founding Software Engineer 2 days

    3. 3

      Write the post

      History and design choices, credit included.

      Founder & CEO 2 days

    4. 4

      Link

      Comparison page and migration overview.

      Founding Software Engineer 1 hour

    5. 5

      Share

      Where PgCat users gather, and the digest.

      Founder & CEO 1 day

    6. 6

      Measure

      Visits and installs from the guide.

      Founder & CEO monthly

    First result
    1 month
    Cost
    $0
    Owner
    Founder & CEO

    Smallest test

    Publish the guide alone and link it from the comparison page.

    Why it works

    Write one post, "From PgCat to PgDog": what PgCat taught, what was redesigned (automatic routing, prepared statements with sharding, two-phase commit, COPY) and what that means for PgCat users. Pair it with a /migrating-to-pgdog/from-pgcat/ guide built from the comparison table, and link both from the comparison page.

    Owning the lineage turns a credibility question into a story of experience, and gives a natural home to every engineer searching for PgCat alternatives.

    Risks and how to handle them

    • Reads as criticism of PgCat's current maintainers

      Keep it about design lessons and thank the project.

    Evidence

    • Hacker News"PgDog is funded and coming to a database near you": 548 points and 261 comments. Readers asked how PgDog differs from PgBouncer, Citus, Multigres and PlanetScale's Neki, and what is open source versus Enterprise (the founder replied that sharding stays open source, while the control plane and query QoS are Enterprise); objections centred on high availability (PgDog relies on tools such as Patroni or RDS to promote a new primary), modulo-based shard placement making rebalancing hard, and two-phase commit; one commenter asked for more credit to the founder's earlier project, PgCat; users praised stable production use and easy migration from PgBouncer, and asked for binaries and cargo install.Source
    • Your docsDocs sitemap (104 URLs, last modified November 2, 2026): a "Migrating to PgDog" section with only an overview and a PgBouncer guide (nothing for RDS Proxy, PgCat, Citus or Supavisor); auth pages for RDS IAM and Azure workload identity, but no deployment guides for AWS RDS or Aurora, Google Cloud SQL or Azure, and no Kubernetes page; a comparison page that covers only PgBouncer and PgCat; a benchmarks page; resharding pages; 12 Enterprise edition pages.Source
  • 22

    PgDog can see what few others can: more than 3M queries per second in production, over 20 TB sharded, thousands of engineers testing daily, and a community asking the same questions about pooling, replicas and sharding. Nobody publishes a regular, data-backed view of how teams actually scale Postgres before they leave it.

    Medium impactMedium effort First result in 1 quarter Founder & CEO

    First action

    Write ten survey questions and post them in Discord.

    How to measure it

    Report downloads

    Now
    –
    Target
    3,000
    By
    2 quarters after launch

    Steps

    1. 1

      Design the survey

      Ten questions, five minutes.

      Founder & CEO 2 days

    2. 2

      Collect

      Discord, email list, partners, social.

      Founder & CEO 6 weeks

    3. 3

      Add fleet data

      Aggregate, opt-in, anonymized.

      Founding Software Engineer 1 week

    4. 4

      Analyze

      Charts and key findings.

      Contract technical writer 2 weeks

    5. 5

      Publish

      Report page plus raw data.

      Founding Software Engineer 2 days

    6. 6

      Launch

      Hacker News, newsletters and a talk.

      Founder & CEO 1 week

    First result
    1 quarter
    Cost
    Writer and design time, about $3,000
    Owner
    Founder & CEO

    Smallest test

    Post a three-question poll in Discord and publish the results as a blog post.

    Why it works

    Run a short survey through Discord, the release-notes list and partners (database size, connection counts, pooler used, when they considered sharding, what blocked them), add anonymized, aggregate figures from customers who agree, and publish a yearly report with charts and a raw-data download. Launch it on Hacker News and in Postgres newsletters, and give each customer a private comparison against the benchmarks.

    Original data earns links, press and conference slots that product posts don't, and it positions PgDog as the authority on the moment teams outgrow a single Postgres.

    Risks and how to handle them

    • Low survey response

      Offer each respondent the full data and a summary of their peers.

    Builds on

    Evidence

    • Your websiteFunding post (June 10, 2026): a $5.5M seed from Basis Set, YC, Pioneer Fund and others; over 2M queries per second in production across dozens of deployments; more than 20 TB sharded; over 1.4M Docker pulls; a three-person team; new releases every Thursday; an Enterprise edition to make AWS deployment easier, with SLA-backed support.Source
    • Your website"The 3 D's of software: distribution, distribution, distribution" (November 4, 2026): 3.69M downloads of the open-source version, 5.16M of PgDog Enterprise Edition and 323k of the EE control plane; about 500 issues in a year; "thousands of engineers" test PgDog daily; no waiting list, contact form or credit card, and the EE image and Helm chart are public; a GitHub Actions example runs an app's test suite through PgDog; no marketplace listing is mentioned.Source
    • Your websiteHomepage (checked November 10, 2026): H1 "Scale Postgres n times"; "3M+ queries/s in production"; 17 customer logos including Coinbase, Ramp, Modal, Huntress, Pennylane, PrizePicks and TRM Labs; five short customer quotes, one comparing PgDog favorably with RDS Proxy; DDL runs on every shard so Alembic and ActiveRecord migrations work; no pricing; calls to action "Get PgDog" (docs), "For enterprise" and "Talk to us" (a Calendly booking). The live demo is linked only from the Enterprise page.Source

03

How Programmable can help

Where an idea in this playbook is something Programmable builds or runs, it's listed here with what we'd do. Everything else is yours to run.

ProgrammableTalk

Fill the events in this plan

These ideas are events. Talk gets registrants for them and tells you who's coming and what their company does before the day.

Plan an event (opens programmable.talk in a new tab)
More example playbooks and reviews

More growth playbooks

Other companies we have researched, each read from what they are hiring for.

  • ettitude growth strategyA sustainable bedding and home brand selling sheets, duvet covers, pillowcases, towels, robes and blankets made from its patented…22 growth ideas
  • Code Four growth strategyAI software for law enforcement: Report drafts police reports from body-cam video and audio with every fact linked to its clip, Insights…22 growth ideas
  • CityZeen growth strategyAI-native infrastructure for institutional commercial real estate and sustainable infrastructure: evidence passports, geospatial and ESG…22 growth ideas
  • SupplyHouse.com growth strategyAn online distributor of plumbing, heating, HVAC and electrical supplies, with over 180,000 products, four US fulfillment centers, an app…23 growth ideas
  • Everlane growth strategyA US apparel brand selling premium essentials (denim, cashmere, tees, outerwear, shoes) under the "clean luxury" banner, made at partner…22 growth ideas
  • Global Healing growth strategyA family-owned maker of vegan and organic vitamins, supplements and cleanse programs, led by its Oxy-Powder colon cleanser, sold through…21 growth ideas
  • Bath & Body Works growth strategyA U.S. specialty retailer of body care, home fragrance (candles and Wallflowers), soaps and sanitizers under Bath & Body Works, White Barn…20 growth ideas
  • OS3 growth strategyBuilds HALE 1.0, a US-built bimanual mobile robot with in-house actuators and a video-pretrained model. Its first job is the hotel laundry…23 growth ideas

See every playbook and website review

Independent research. Programmable wrote this playbook from public sources, as they stood on November 10, 2026, and cites them throughout. PgDog did not commission, review or endorse it, and Programmable is not affiliated with PgDog. Company and product names are trademarks of their owners, used only to identify them. The ideas are suggestions and opinion, not professional, legal or financial advice, and not statements about how PgDog runs its business.

Something wrong, or do you represent PgDog? Email [email protected] and we will correct it or take it down.

30/60/90 roadmap

What to focus on in each month, and the ideas that carry it.

  1. Days 1 to 307 ideas

    Fix the crawl (sitemap, 404s, titles), publish Enterprise pricing anchors and an AGPL FAQ, put the live demo and support offers where readers already are, start a release-notes list and the first three case studies.

  2. Days 31 to 6010 ideas

    Docs that sell: RDS Proxy migration, cloud deployment guides, HA and resharding runbooks, a comparison hub and reproducible benchmarks; ship the config converter and CI action; add optional control-plane registration; meet the ORM communities.

  3. Days 61 to 905 ideas

    Commit to the big bets (consultancy partners, AWS Marketplace, a one-command install in the customer's AWS account) and the two wildcards: the PgCat lineage story and an annual report on sharded Postgres.

The research behind the plan

3 research areas, each summarised in a few lines. Open any of them for the full detail.

Customers

What customers say

Customers value stable in production at very high query rates. The most cited problem: running out of Postgres connections.

  • Easy migration from PgBouncer
  • RDS Proxy pinning connections
  • In their words: “connection pinning”

Market

Competitive landscape

6 competitors compared: PgBouncer, AWS RDS Proxy, Supavisor, Citus and 2 more.

  • Gap to exploit: Sharding for teams that want to stay on RDS or their own Postgres
  • PgBouncer: No load balancing or sharding; single-threaded
  • AWS RDS Proxy: Connection pinning on session features

Hiring signals

PgDog is a three-person YC company hiring one Founding Software Engineer (Rust and Postgres, mostly new features and bug fixes), and its roadmap names an OLAP query engine for sharded Postgres and push-button resharding.

  • Founding Software Engineer: Rust and Postgres; roadmap of an OLAP engine and in-place data redistribution. Ideas 10, 11, 14, 20.

From the team that wrote this playbook

All products
  • ProgrammableAgencyWorking AI systems in days, not quarters (opens programmable.agency in a new tab)
  • ProgrammableInfoAn agent that finds, researches and asks first (opens programmable.info in a new tab)
  • ProgrammableDigitalScreenshots in, an animated product demo out (opens programmable.digital in a new tab)
  • ProgrammableWatchKnow the day a supplier falls out of compliance (opens programmable.watch in a new tab)
  • ProgrammableTalkGet registrants for your events, and know who’s coming (opens programmable.talk in a new tab)
  • ProgrammablePageText what you need, your customer gets a page that works (opens programmable.page in a new tab)
  • ProgrammableCommunityForums with labelled AI members, never empty (opens programmable.community in a new tab)
ProgrammableMarketing
ExamplesLeaderboardsProductsTermsPrivacyCookiesDPALegalContact

© 2026 AI-Powered Growth Intelligence