Skip to content

Add more PaaS (PostgreSQL as a Service) providers#460

Open
belo4ya wants to merge 1 commit into
dhamaniasad:masterfrom
belo4ya:complete-paas-list
Open

Add more PaaS (PostgreSQL as a Service) providers#460
belo4ya wants to merge 1 commit into
dhamaniasad:masterfrom
belo4ya:complete-paas-list

Conversation

@belo4ya
Copy link
Copy Markdown
Contributor

@belo4ya belo4ya commented Jan 11, 2026

This PR significantly expands the PaaS (PostgreSQL as a Service) section by adding a broad set of currently active platforms that provide managed PostgreSQL offerings. The list is based on a personal long-term collection of managed PostgreSQL services and cloud platforms. I actively use accounts in many of these services, including their free-tier plans where available. I also use this list to track ongoing innovation in the PostgreSQL ecosystem and to observe how commercial providers differentiate their offerings (e.g. serverless architectures, branching, multi-tenant models, regional clouds, etc.).

The list items were sorted in alphabetical order.

One pull request for one item.

I have reviewed the repository’s Contribution Guidelines репозитория, but I do not consider it practical to split this PR into 30+ separate ones. However, if this is strongly preferred, I am willing to do so.

I did not spend much effort on crafting the descriptions for each item - most descriptions were taken directly from providers’ landing pages, which makes some of them sound marketing-oriented. Where such descriptions were not available, I tried to write concise and neutral summaries (with the help of an LLM; for example, "Managed PostgreSQL on Akamai/Linode with automated provisioning, backups, and maintenance").

Links for Selectel Cloud for PostgreSQL, Cloud.ru Evolution Managed PostgreSQL, VK Cloud PostgreSQL as a Service, MWS Managed PostgreSQL, Timeweb Cloud Managed Service for PostgreSQL point to landing pages in local languages rather than English, as equivalent English pages do not exist. Please let me know if this is an issue.

Disclaimer: I am affiliated with Cloud.ru as an engineer working on Managed PostgreSQL.

@belo4ya belo4ya force-pushed the complete-paas-list branch from 7407768 to e3bbc7f Compare January 11, 2026 01:18
@NikolayS
Copy link
Copy Markdown
Contributor

NikolayS commented Jan 11, 2026

I think it makes sense to point explicitly in which jurisdiction each service works

@belo4ya
Copy link
Copy Markdown
Contributor Author

belo4ya commented Feb 8, 2026

Do you have a preference for how to present this?

One idea is to add short availability/market tags at the end of each entry, e.g. (global, us, eu, apac, cn, ru, cis, multicloud). For example:

Alibaba Cloud ApsaraDB RDS for PostgreSQL - An on-demand database hosting service for PostgreSQL with automated monitoring, backup and disaster recovery capabilities. (cn, global)
Yandex Cloud Managed Service for PostgreSQL - Managed PostgreSQL clusters in Yandex Cloud infrastructure. (ru, cis)

each service

To keep it readable and accurate, I could apply tags only where the service is clearly region-limited or market-specific (e.g., CN/CIS/EU-only). For broadly available services I’d omit tags unless there’s a clear regions reference.

@kmoppel
Copy link
Copy Markdown
Collaborator

kmoppel commented Feb 14, 2026

@belo4ya Wow, crazy amount of services, had no idea that there were so many, thanks!....But, yes making marking strictly country-based offerings would be very useful for users / readers indeed, so do please add all the limitations info you have in parentheses,

@belo4ya belo4ya force-pushed the complete-paas-list branch 2 times, most recently from 9fb5730 to 7ab7694 Compare April 12, 2026 11:59
@belo4ya belo4ya force-pushed the complete-paas-list branch from 7ab7694 to 5c127f2 Compare April 12, 2026 13:00
@belo4ya
Copy link
Copy Markdown
Contributor Author

belo4ya commented Apr 12, 2026

added tags: (ru), (ru, cis), (cn, apac), (eu-focused)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants