{"source":"CiteHawk AI Index","record":"Postgres hosting providers — 2026-11","url":"https://www.citehawk.com/leaderboards/editions/2026-11/postgres-hosting","immutable":true,"snapshotId":"33f9a717-8e6e-4082-98e3-a5a553498e2a","capturedAt":"2026-11-01T05:10:30.071+00:00","contentHash":"f67ad86047124319b040976d23e1b2301edb307f5adc159b5be5585682522711","contentHashSpec":"sha256-v1: hex SHA-256 of the UTF-8 bytes of the compact JSON array (no whitespace, non-ASCII characters unescaped, as JavaScript JSON.stringify emits) of [provider, run, model, text] tuples, one per captured answer, sorted by provider then run","registryRulesHash":"c45953a641fc763b2597a6a3f8837471f65b7550827fe50008bb0e5221fca519","registryRulesHashSpec":"sha256-v1: hex SHA-256 of the UTF-8 bytes of the compact JSON object {version, aliases, notInCategory, categoryAllow, serviceSlugRe} where aliases is the array of [foldedKey, canonicalName, pinnedDomain, categoryScope] tuples sorted by key, carrying a fifth regionScope element only on the entries that have one, notInCategory and categoryAllow are arrays of [categorySlug, domains] tuples sorted by slug, and every domain/scope list is itself sorted, carrying a trailing notInCategoryByRegion element, an array of [categorySlug, region, domains] triples sorted by slug then region, only when at least one region-scoped deny entry exists, and after it a trailing notInCategoryByName element, an array of [categorySlug, regionScope, names] triples sorted by slug then scope (regionScope \"*\" for every board region, names as published), only when at least one name-scoped deny entry exists","region":"global","prompt":"What are the best Postgres hosting providers? Recommend the top brands or products that people actually use.","providers":["openai","claude","gemini","perplexity","deepseek","grok","bing_copilot","google_aio","google_ai_mode"],"models":{"grok":"grok-4.3","claude":"claude-sonnet-5-5","gemini":"gemini-3.6-flash","openai":"gpt-6-sol","deepseek":"deepseek-flash","google_aio":"google_aio","perplexity":"sonar","bing_copilot":"bing_copilot","google_ai_mode":"google_ai_mode"},"runsPerProvider":1,"totalCalls":18,"ranking":[{"rank":1,"brand":"Amazon RDS for PostgreSQL","domain":"amazon.com","entityId":"3666af11-2b31-4cd9-ae70-44c69cfdf69a","score":51.6,"mentions":8,"recommendedBy":["openai","claude","perplexity","deepseek","grok","bing_copilot","google_aio","google_ai_mode"],"averagePositionByProvider":{"grok":1,"claude":1,"openai":1,"deepseek":1,"google_aio":8,"perplexity":1,"bing_copilot":1,"google_ai_mode":1}},{"rank":2,"brand":"Supabase","domain":"supabase.com","entityId":"a7fddae5-279c-4bf8-b9b3-99a52845d923","score":49.5,"mentions":9,"recommendedBy":["openai","claude","gemini","perplexity","deepseek","grok","bing_copilot","google_aio","google_ai_mode"],"averagePositionByProvider":{"grok":5,"claude":4,"gemini":2,"openai":4,"deepseek":4,"google_aio":2,"perplexity":2,"bing_copilot":2,"google_ai_mode":7}},{"rank":3,"brand":"Neon","domain":"neon.com","entityId":"dd6ad096-7a83-458f-beb5-da55a8902f4b","score":49.1,"mentions":9,"recommendedBy":["openai","claude","gemini","perplexity","deepseek","grok","bing_copilot","google_aio","google_ai_mode"],"averagePositionByProvider":{"grok":4,"claude":5,"gemini":1,"openai":5,"deepseek":5,"google_aio":1,"perplexity":3,"bing_copilot":3,"google_ai_mode":8}},{"rank":4,"brand":"DigitalOcean Managed PostgreSQL","domain":"digitalocean.com","entityId":"4e717d54-aa72-43f8-954c-f18880e291bd","score":45.9,"mentions":8,"recommendedBy":["openai","claude","perplexity","deepseek","grok","bing_copilot","google_aio","google_ai_mode"],"averagePositionByProvider":{"grok":6,"claude":9,"openai":6,"deepseek":11,"google_aio":7,"perplexity":4,"bing_copilot":4,"google_ai_mode":4}},{"rank":5,"brand":"Crunchy Bridge","domain":"crunchybridge.com","entityId":"831239b3-56ad-4541-ade2-6dea99fbbd02","score":45.8,"mentions":8,"recommendedBy":["openai","deepseek","grok","google_aio","claude","gemini","perplexity","google_ai_mode"],"averagePositionByProvider":{"grok":7,"claude":10,"gemini":7,"openai":7,"deepseek":8,"google_aio":4,"perplexity":7,"google_ai_mode":5}},{"rank":6,"brand":"Aiven for PostgreSQL","domain":"aiven.io","entityId":"7c37bfb8-996b-493f-b3d2-e913b05351bb","score":45.5,"mentions":8,"recommendedBy":["openai","claude","gemini","perplexity","deepseek","grok","google_aio","google_ai_mode"],"averagePositionByProvider":{"grok":9,"claude":11,"gemini":8,"openai":8,"deepseek":9,"google_aio":5,"perplexity":8,"google_ai_mode":6}},{"rank":7,"brand":"Google Cloud SQL for PostgreSQL","domain":"cloud.google.com","entityId":"6231f6d8-8a49-4d2d-8627-83abdcd2d7e3","score":44.5,"mentions":7,"recommendedBy":["openai","claude","gemini","deepseek","grok","google_aio","google_ai_mode"],"averagePositionByProvider":{"grok":2,"claude":2,"gemini":10,"openai":2,"deepseek":2,"google_aio":10,"google_ai_mode":2}},{"rank":8,"brand":"Render","domain":"render.com","entityId":"baf60f85-fc0c-4554-9f7a-5e1af042c5dd","score":43.5,"mentions":7,"recommendedBy":["claude","gemini","perplexity","deepseek","grok","bing_copilot","google_aio"],"averagePositionByProvider":{"grok":8,"claude":7,"gemini":4,"deepseek":6,"google_aio":6,"perplexity":5,"bing_copilot":6}},{"rank":9,"brand":"Azure Database for PostgreSQL","domain":"azure.microsoft.com","entityId":"372451d6-7b80-4120-8d00-c52be4deb63d","score":38.6,"mentions":6,"recommendedBy":["openai","claude","google_ai_mode","gemini","deepseek","grok"],"averagePositionByProvider":{"grok":3,"claude":3,"gemini":11,"openai":3,"deepseek":3,"google_ai_mode":3}},{"rank":10,"brand":"Aurora PostgreSQL","domain":null,"entityId":"c484e566-8d70-43dc-804f-706d28386481","score":26.7,"mentions":2,"recommendedBy":["perplexity","claude"],"averagePositionByProvider":{"claude":1,"perplexity":1}},{"rank":11,"brand":"Railway","domain":"railway.app","entityId":"dab7299d-4314-43a7-9745-b1ea3482fff1","score":25.8,"mentions":4,"recommendedBy":["claude","gemini","perplexity","deepseek"],"averagePositionByProvider":{"claude":8,"gemini":5,"deepseek":7,"perplexity":6}},{"rank":12,"brand":"Timescale Cloud","domain":"timescale.com","entityId":"039d7f99-79bd-48c6-b80a-94907943b800","score":13.4,"mentions":2,"recommendedBy":["gemini","deepseek"],"averagePositionByProvider":{"gemini":3,"deepseek":15}},{"rank":13,"brand":"Heroku Postgres","domain":"heroku.com","entityId":"a9c44f75-e80d-41f1-bdc7-53aadd74644c","score":13,"mentions":2,"recommendedBy":["perplexity","deepseek"],"averagePositionByProvider":{"deepseek":14,"perplexity":9}},{"rank":14,"brand":"PlanetScale","domain":"planetscale.com","entityId":"7ea3093e-ea42-47aa-9fcc-95d5e755ebab","score":8.4,"mentions":1,"recommendedBy":["claude"],"averagePositionByProvider":{"claude":6}}],"answers":[{"provider":"bing_copilot","run":1,"model":"bing_copilot","capturedAt":"2026-11-01T05:10:30.097Z","text":"The top PostgreSQL hosts people actually use are AWS RDS, Supabase, Neon, DigitalOcean, Northflank, and Render, each excelling for different workloads.\n\n✅ The Top Providers People Use Most\n\nThese options appear consistently across developer comparisons and industry roundups :\n\nAWS RDS for PostgreSQL — the enterprise default with mature HA, backups, and deep AWS integration.\nSupabase — PostgreSQL plus authentication, storage, APIs, and realtime features for full-stack apps.\nNeon — serverless PostgreSQL with scale‑to‑zero and database branching for modern development workflows.\nDigitalOcean Managed Databases — simple, predictable pricing and easy setup for small/medium apps.\nNorthflank — managed PostgreSQL with HA, backups, pooling, and full-stack preview environments.\nRender — managed PostgreSQL tightly integrated with application hosting on the same platform.\n\nThese six providers dominate developer adoption because they balance reliability, modern features, and ecosystem integration.\n\n📊 Quick Comparison Table\n\nProvider | Best For | Key Strengths | Notable Trade-offs\nAWS RDS | Enterprise workloads, AWS apps | Multi‑AZ HA, mature backups, many instance sizes 1 | Expensive, complex pricing, limited extensions 1\nSupabase | Full-stack apps, rapid prototyping | Auth, storage, APIs, pgvector/PostGIS support 1 | No Multi‑AZ, PITR is a paid add‑on 2\nNeon | Serverless apps, CI/CD, branching | Scale‑to‑zero, instant branching, usage-based pricing 2 | Cold starts, narrower extension support 1\nDigitalOcean | SMBs, simple production workloads | Predictable pricing, easy HA, built-in pooling 2 | Limited instance sizes, fewer regions 1\nNorthflank | Teams needing HA + app previews | HA via Patroni, pooling, snapshots, BYOC option 1 | Storage/replica counts cannot shrink in place 1\nRender | Apps already hosted on Render | Private networking, PITR, HA on eligible plans 1 | HA requires specific compute tiers 1\n2 Sources2\n\n🥇 Best Overall Picks by Use Case\n\nFor enterprise or mission-critical workloads:\n\nAWS RDS — most widely deployed, strong HA, predictable operational model.\n\nFor modern serverless apps or variable workloads:\n\nNeon — scale-to-zero and branching are unmatched.\n\nFor full-stack development with built-in backend services:\n\nSupabase — instant APIs, auth, storage, realtime features.\n\nFor simple, affordable production hosting:\n\nDigitalOcean Managed Databases — predictable pricing and easy setup.\n\nFor teams wanting database + app deployment in one platform:\n\nNorthflank — HA, backups, pooling, and preview environments.\nRender — integrated app + DB hosting with PITR and HA options.\n\n🧭 How to Choose the Right Provider\n\nBased on the criteria highlighted in the results, prioritize:\n\nAvailability & HA — Multi‑AZ, standby nodes, failover behavior.\nRecovery — backup frequency, retention, PITR support.\nPerformance & scaling — CPU/RAM, storage IOPS, read replicas, pooling.\nExtension support — pgvector, PostGIS, pg_cron, TimescaleDB.\nWorkflow fit — branching, previews, private networking, CI/CD integration.\nFull cost — compute, storage, replicas, backups, transfer fees.\n\n🔍 If you want a simple recommendation\n\nTell me your use case (e.g., SaaS app, analytics, hobby project, enterprise workload), and I can narrow this list to the best 1–2 providers for your needs.","extractedBrands":[{"name":"AWS RDS","domain":"aws.amazon.com","position":1},{"name":"Supabase","domain":"supabase.com","position":2},{"name":"Neon","domain":null,"position":3},{"name":"DigitalOcean","domain":"digitalocean.com","position":4},{"name":"Northflank","domain":"northflank.com","position":5},{"name":"Render","domain":"render.com","position":6}]},{"provider":"claude","run":1,"model":"claude-sonnet-5-5","capturedAt":"2026-11-01T05:10:30.097Z","text":"There's no single best Postgres host. The right one depends on your workload. These are the providers that come up most often, grouped by what they suit.\n\n## Big cloud providers\n- **Amazon RDS and Aurora PostgreSQL** are the usual choice for AWS shops. RDS for PostgreSQL provides managed instances, automated backups, point-in-time recovery, read replicas and Multi-AZ configurations. Aurora is aimed at mission-critical workloads. One ranking cites six-way replicated storage and sub-35s failover. The downside is that costs and tuning complexity can grow at scale.\n- **Google Cloud SQL and AlloyDB** suit apps on Google Cloud. Some 2026 benchmarks put Cloud SQL often 10 to 16 percent below equivalent AWS RDS instances at the 8 vCPU tier.\n- **Azure Database for PostgreSQL** is the pick for Microsoft-centred organisations.\n\n## Developer-focused platforms\n- **Supabase** is Postgres plus auth, storage, realtime and an API. It's the usual choice if you want a whole backend. It has a free tier, then starts at $25/mo. It also raised funding recently, $500 million in June 2026 at a $10.5 billion valuation, so it's well established.\n- **Neon** is serverless Postgres. It's best for instant branching and scale-to-zero, and suits spiky or dev workloads. It's now part of Databricks.\n- **PlanetScale** now offers Postgres too. It's pitched at fast-growing apps and has local NVMe storage on its Metal clusters.\n- **Render** and **Railway** let you run your app and its Postgres database on one platform. With Railway you'll own more of the database operations.\n\n## Simple, predictable pricing\n- **DigitalOcean Managed Databases** is popular with small teams. It has daily backups included, from $15/mo. The entry node is small, and high availability doubles the price.\n\n## Postgres specialists and multi-cloud\n- **Crunchy Bridge** is run by Postgres specialists. It offers superuser access, built-in PgBouncer and Postgres-core-team-level support across AWS, GCP and Azure.\n- **Aiven** is multi-cloud, and good if you also want other open source data services such as Kafka or OpenSearch.\n\n## Quick picks\n- **Starting a new app or MVP:** Supabase or Neon, both of which have free tiers.\n- **Already on AWS, GCP or Azure:** use that cloud's managed Postgres.\n- **Preview environments and branching:** Neon.\n- **Steady production app on a budget:** DigitalOcean.\n- **Postgres expertise and support:** Crunchy Bridge.\n- **Mission-critical, high availability:** Aurora, Cloud SQL Enterprise Plus or PlanetScale HA.\n\nMany of the comparison articles I found are published by vendors that sell their own hosting, so they may favor their own products. Check pricing and current features on each provider's site before committing.\n\nIf you tell me your stack, budget and scale, I can narrow this to one or two options.","extractedBrands":[{"name":"Amazon RDS","domain":"amazon.com","position":1},{"name":"Aurora PostgreSQL","domain":null,"position":1},{"name":"Google Cloud SQL","domain":"google.com","position":2},{"name":"AlloyDB","domain":"google.com","position":2},{"name":"Azure Database for PostgreSQL","domain":"microsoft.com","position":3},{"name":"Supabase","domain":"supabase.com","position":4},{"name":"Neon","domain":null,"position":5},{"name":"PlanetScale","domain":"planetscale.com","position":6},{"name":"Render","domain":"render.com","position":7},{"name":"Railway","domain":"railway.app","position":8},{"name":"DigitalOcean Managed Databases","domain":"digitalocean.com","position":9},{"name":"Crunchy Bridge","domain":"crunchybridge.com","position":10},{"name":"Aiven","domain":"aiven.io","position":11}]},{"provider":"deepseek","run":1,"model":"deepseek-flash","capturedAt":"2026-11-01T05:10:30.097Z","text":"“Best” depends on whether you want a boring managed Postgres, a serverless/dev-friendly Postgres, or a specialized provider. The brands people actually use, roughly by category:\n\n## Top recommendations by use case\n\n| Use case | Providers people actually use | Notes |\n|---|---|---|\n| **Default / most teams** | **Amazon RDS for PostgreSQL**, **Google Cloud SQL for PostgreSQL**, **Azure Database for PostgreSQL Flexible Server** | The safe, ubiquitous choices. Good HA, backups, PITR, compliance, VPC integration. More ops/config complexity than dev-first providers. |\n| **Developer experience / app backend** | **Supabase**, **Neon**, **Render Postgres**, **Railway Postgres** | Supabase is popular for full backend/auth/storage around Postgres. Neon is popular for serverless, branching, and scale-to-zero-style workflows. Render/Railway are simple and pleasant for small-to-mid apps. |\n| **Dedicated managed Postgres specialists** | **Crunchy Bridge**, **Aiven for PostgreSQL**, **EDB BigAnimal** | Good when you want Postgres expertise, extensions, support, and less cloud-vendor lock-in. Crunchy/Aiven/EDB are well-regarded by teams that need more than basic DBaaS. |\n| **Simple/cheap managed DB** | **DigitalOcean Managed PostgreSQL**, **Linode/Akamai Managed Databases**, **Vultr Managed Databases** | Fine for smaller apps and predictable workloads. Less feature-rich than AWS/GCP/Azure or specialists. |\n| **Heroku-style / legacy PaaS** | **Heroku Postgres** | Still used, especially by existing Heroku apps. Less compelling for new projects unless you’re already on Heroku. |\n| **Time-series / analytics on Postgres** | **Timescale Cloud** | Best known for time-series and Postgres extensions. Not a general default unless you need TimescaleDB. |\n| **High-performance / cloud-native Postgres-compatible** | **Google AlloyDB**, **Amazon Aurora PostgreSQL** | Great for high performance and scale, but they’re Postgres-compatible managed systems, not plain vanilla Postgres. Watch lock-in and cost. |\n| **Self-managed on cloud** | **AWS EC2**, **GCP Compute Engine**, **DigitalOcean Droplets** + **Patroni/pgBouncer** | Cheapest at scale if you have DB ops skills. Not “hosting” in the managed sense. |\n\n## What I’d pick in practice\n\n- **Most startups / SaaS apps:** **Supabase** if you want batteries included; **Neon** if you want serverless/branching; **RDS/Cloud SQL** if you want maximum maturity and cloud integration.\n- **Enterprise / compliance-heavy:** **Amazon RDS**, **Google Cloud SQL**, **Azure Flexible Server**, or **Crunchy Bridge/Aiven/EDB** for specialist support.\n- **Small projects / side projects:** **Neon**, **Supabase**, **Render**, **Railway**, or **DigitalOcean**.\n- **High-scale production with dedicated DB team:** **RDS/Aurora**, **Cloud SQL/AlloyDB**, **Crunchy Bridge**, **Aiven**, or self-managed with Patroni.\n- **Time-series workloads:** **Timescale Cloud**.\n\n## Quick buying checklist\n\nLook for: automated backups + point-in-time recovery, HA/failover, connection pooling, read replicas, Postgres version/extension support, VPC/private networking, encryption, compliance, observability, support SLA, and egress/backup pricing. The biggest hidden costs are usually **egress, storage/backups, and high-availability replicas**.\n\n**Shortlist for most people:** **Amazon RDS for PostgreSQL**, **Google Cloud SQL**, **Supabase**, **Neon**, **Crunchy Bridge**, **Aiven**, and **DigitalOcean Managed PostgreSQL**. Those are the names you’ll see most often in real production stacks.","extractedBrands":[{"name":"Amazon RDS for PostgreSQL","domain":"amazon.com","position":1},{"name":"Google Cloud SQL for PostgreSQL","domain":"google.com","position":2},{"name":"Azure Database for PostgreSQL Flexible Server","domain":"azure.com","position":3},{"name":"Supabase","domain":"supabase.com","position":4},{"name":"Neon","domain":null,"position":5},{"name":"Render Postgres","domain":"render.com","position":6},{"name":"Railway Postgres","domain":"railway.app","position":7},{"name":"Crunchy Bridge","domain":"crunchydata.com","position":8},{"name":"Aiven for PostgreSQL","domain":"aiven.io","position":9},{"name":"EDB BigAnimal","domain":"edb.com","position":10},{"name":"DigitalOcean Managed PostgreSQL","domain":"digitalocean.com","position":11},{"name":"Linode/Akamai Managed Databases","domain":null,"position":12},{"name":"Vultr Managed Databases","domain":"vultr.com","position":13},{"name":"Heroku Postgres","domain":"heroku.com","position":14},{"name":"Timescale Cloud","domain":"timescale.com","position":15},{"name":"Google AlloyDB","domain":"google.com","position":16},{"name":"Amazon Aurora PostgreSQL","domain":"amazon.com","position":17},{"name":"AWS EC2","domain":"aws.amazon.com","position":18},{"name":"GCP Compute Engine","domain":"google.com","position":19},{"name":"DigitalOcean Droplets","domain":"digitalocean.com","position":20},{"name":"Patroni","domain":null,"position":21},{"name":"pgBouncer","domain":null,"position":22}]},{"provider":"gemini","run":1,"model":"gemini-3.6-flash","capturedAt":"2026-11-01T05:10:30.097Z","text":"The Postgres hosting ecosystem ranges from developer-friendly serverless platforms to heavy-duty enterprise cloud infrastructure. \n\nThe top PostgreSQL hosting providers actually used in production and development fall into four distinct categories:\n\n---\n\n### 1. Developer-First & Serverless Postgres\n*Best for fast development, modern web apps (Next.js, Remix, Node, Python), and AI/Vector workloads.*\n\n* **Neon**\n  * **Why people use it:** Neon is a modern, serverless Postgres platform that separates compute and storage. Its defining feature is **instant database branching** (allowing you to branch your database schema and data like Git) and **scale-to-zero** (you only pay for active compute).\n  * **Best for:** Serverless applications, staging/preview environments, and developers who want low idle costs.\n* **Supabase**\n  * **Why people use it:** Often called the open-source alternative to Firebase, Supabase is built entirely on top of PostgreSQL. It provides a full backend suite: auto-generated REST/GraphQL APIs, Auth, Edge Functions, Realtime subscriptions, and built-in vector support (`pgvector`).\n  * **Best for:** Full-stack developers, mobile/web app builders, and startups wanting an out-of-the-box backend centered around Postgres.\n* **Timescale Cloud**\n  * **Why people use it:** Built by the creators of TimescaleDB (a Postgres extension), it optimizes standard Postgres for time-series data, event tracking, real-time analytics, and vector search.\n  * **Best for:** IoT, financial data, metrics, analytics-heavy platforms, and high-ingest workloads.\n\n---\n\n### 2. Integrated PaaS (App + Database Hosting)\n*Best for solo developers, small teams, and projects where you want app code and database hosted under one roof.*\n\n* **Render**\n  * **Why people use it:** Render offers a zero-friction developer experience. It provides managed Postgres databases (with automated backups, connection pooling, and disk auto-scaling) alongside its web service hosting.\n  * **Best for:** Web apps, side projects, and small-to-medium startups wanting simplicity over complex cloud setup.\n* **Railway**\n  * **Why people use it:** Railway is praised for its UI, quick setup time, and usage-based pricing model. You can provision a production-ready Postgres instance in seconds with built-in metrics and simple connection management.\n  * **Best for:** Prototyping, microservices, and fast-moving dev teams.\n* **Fly.io**\n  * **Why people use it:** Fly.io runs application containers close to users globally. Its PostgreSQL service allows you to deploy distributed read-replicas in multiple global regions easily.\n  * **Best for:** Global, low-latency applications requiring database replicas near end-users.\n\n---\n\n### 3. Dedicated & Cloud-Agnostic DBaaS Specialists\n*Best for teams that need deep Postgres expertise, high availability, and performance without being locked into a single cloud hyperscaler.*\n\n* **Crunchy Bridge (by Crunchy Data)**\n  * **Why people use it:** Built by core PostgreSQL contributors, Crunchy Bridge is a pure-play managed database service. It runs on AWS, GCP, or Azure infrastructure while offering superior Postgres performance tuning, security, and top-tier expert support.\n  * **Best for:** Teams looking for deep Postgres expertise, enterprise-grade reliability, and multi-cloud flexibility.\n* **Aiven for PostgreSQL**\n  * **Why people use it:** Aiven manages open-source data infrastructure across major cloud providers (AWS, GCP, Azure, DigitalOcean). It offers automated backups, point-in-time recovery, zero-downtime upgrades, and multi-cloud disaster recovery.\n  * **Best for:** Mid-market to enterprise companies managing multi-cloud or multi-service infrastructure (e.g., Postgres + Kafka + Redis).\n\n---\n\n### 4. Hyperscale Cloud Managed Postgres\n*Best for established businesses, high-traffic production workloads, and strict enterprise compliance.*\n\n* **AWS (Amazon RDS & Aurora PostgreSQL)**\n  * **Why people use it:** The industry benchmark for enterprise deployments. **RDS** offers standard managed Postgres, while **AWS Aurora PostgreSQL** provides a high-performance, fault-tolerant engine (with up to 5x throughput of standard Postgres on RDS) and **Aurora Serverless v2** for auto-scaling compute.\n  * **Best for:** Scale-ups, enterprise workloads, high-availability deployments, and deep integration into the AWS ecosystem.\n* **Google Cloud (Cloud SQL & AlloyDB)**\n  * **Why people use it:** Google’s **Cloud SQL** offers reliable managed Postgres. For intensive enterprise workloads, **AlloyDB** is Google's fully managed, Postgres-compatible engine designed for high-throughput OLTP and fast analytical queries.\n  * **Best for:** Google Cloud native workloads, data analytics, and high-transaction applications.\n* **Azure Database for PostgreSQL (Flexible Server)**\n  * **Why people use it:** Microsoft’s managed Postgres offering with predictable cost management, custom maintenance windows, and built-in integration with Azure services.\n  * **Best for:** Enterprise teams heavily invested in Microsoft Azure.\n\n---\n\n### Quick Selection Guide\n\n| If your primary need is... | Choose... |\n| :--- | :--- |\n| **Instant setup, scale-to-zero, Git-like database branching** | **Neon** |\n| **Complete app backend (Auth, APIs, Realtime) on Postgres** | **Supabase** |\n| **Fastest deploy for full-stack apps (App + DB unified)** | **Render** or **Railway** |\n| **Deep Postgres expertise, high availability, no hyperscaler lock-in** | **Crunchy Bridge** |\n| **Enterprise scale, maximum uptime, complex multi-region HA** | **AWS Aurora** or **GCP AlloyDB** |\n| **Time-series data, high-volume metrics, or heavy AI vector workloads** | **Timescale Cloud** |\n\n*(Note: Legacy free database providers like ElephantSQL officially reached End-of-Life in early 2025. Modern projects primarily use Neon, Supabase, or Render as alternatives for free/cheap dev tiers).*","extractedBrands":[{"name":"Neon","domain":null,"position":1},{"name":"Supabase","domain":null,"position":2},{"name":"Timescale Cloud","domain":null,"position":3},{"name":"Render","domain":null,"position":4},{"name":"Railway","domain":null,"position":5},{"name":"Fly.io","domain":null,"position":6},{"name":"Crunchy Bridge","domain":null,"position":7},{"name":"Aiven for PostgreSQL","domain":null,"position":8},{"name":"AWS","domain":null,"position":9},{"name":"Google Cloud","domain":"cloud.google.com","position":10},{"name":"Azure Database for PostgreSQL","domain":"azure.com","position":11}]},{"provider":"google_ai_mode","run":1,"model":"google_ai_mode","capturedAt":"2026-11-01T05:10:30.097Z","text":"When looking at Postgres hosting providers that people actually use and rely on in production, the landscape generally splits into traditional cloud giants (hyperscalers), straightforward developer-friendly platforms, pure-play Postgres specialists, and modern serverless/branching databases.\n\nThe top-used brands and products are organized below by category so you can match them to your actual workflow:\n\n1. The Heavyweight Hyperscalers (Enterprise & Scale)\n\nAmazon RDS for PostgreSQL : The default choice for companies already living in AWS. It handles backups, patching, Multi-AZ high availability, and read replicas smoothly. Amazon RDS for PostgreSQL Pros: Deep AWS ecosystem integration, massive scale, and highly trusted. Cons: Pricing can be complex and unpredictable because you pay separately for instances, storage, and IOPS. Tuning it properly requires genuine DBA knowledge. Google Cloud SQL for PostgreSQL : Google's managed offering. Highly praised for performance, smooth scaling, and great automated maintenance features. Azure Database for PostgreSQL : Microsoft’s enterprise offering, heavily used by organizations entrenched in the Microsoft ecosystem, featuring strong enterprise security and native integration with Azure AI/extensions.\n\n2. Simple & Predictable (Startups & SMBs)\n\nDigitalOcean Managed PostgreSQL : Frequently recommended on developer forums (like Reddit's r/PostgreSQL ) when you want a straightforward, flat-rate monthly price without hidden IO fees. DigitalOcean Managed PostgreSQL Pros: Incredibly simple UI, predictable pricing, automated daily backups, and easy horizontal/vertical scaling. Cons: Lacks the granular enterprise configuration options of AWS RDS.\n\n3. Dedicated Postgres Specialists (Pure-Play & Power Users)\n\nCrunchy Bridge : Built by veteran Postgres contributors and experts who do only Postgres. It gives you true superuser access and runs across multiple clouds. Crunchy Bridge Pros: Exceptional performance tuning, deep Postgres expertise behind the platform, and great security. Cons: Premium pricing compared to basic droplet setups. Aiven for PostgreSQL : A fully managed data platform running across AWS, GCP, and Azure. Pros: Cloud-portable, incredible operational reliability, and built-in connection pooling. Cons: You pay a markup for multi-cloud flexibility.\n\n4. Modern Serverless & Developer Ecosystems (Newer Stacks)\n\nSupabase : Effectively an open-source Firebase alternative built entirely on top of a managed Postgres database, bundling in auto-generated APIs, authentication, and file storage. Supabase Pros: Incredible DX (developer experience), real-time subscriptions, and instant client libraries. Cons: Tight coupling to their platform philosophy; might be overkill if you just want a naked database. Neon : A serverless Postgres platform built with a decoupled storage/compute architecture. Neon Pros: Instant database branching (like Git for your database), scale-to-zero capability, and great for preview environments or serverless functions (Next.js, Vercel stacks). Cons: Scale-to-zero can introduce cold starts if not configured properly for heavy production traffic.\n\nTo help narrow down the best fit, tell me:\n\nWhat is your expected scale (traffic/storage size)? Do you need serverless/scale-to-zero features, or an always-on dedicated instance? Are you already hosted on a specific cloud like AWS or Vercel ?","extractedBrands":[{"name":"Amazon RDS for PostgreSQL","domain":"amazon.com","position":1},{"name":"Google Cloud SQL for PostgreSQL","domain":"google.com","position":2},{"name":"Azure Database for PostgreSQL","domain":"microsoft.com","position":3},{"name":"DigitalOcean Managed PostgreSQL","domain":"digitalocean.com","position":4},{"name":"Crunchy Bridge","domain":null,"position":5},{"name":"Aiven for PostgreSQL","domain":null,"position":6},{"name":"Supabase","domain":null,"position":7},{"name":"Neon","domain":null,"position":8}]},{"provider":"google_aio","run":1,"model":"google_aio","capturedAt":"2026-11-01T05:10:30.097Z","text":"The market for PostgreSQL hosting is highly competitive, shifting from generic cloud database offerings to specialized platforms tailored to specific workflows. The \"best\" provider depends entirely on your architectural choice: modern Serverless/BaaS architectures, dedicated Postgres specialists, or standard Hyperscaler clouds.\n\nThe top brands and products that developers and enterprises actually use are categorized below by their operational models:\n\n1. Serverless & Backend-as-a-Service (BaaS)\n\nThese providers are highly popular for startups, modern web applications, and Jamstack/edge developers because they abstract away traditional server management.\n\nNeon : A favorite among developers for its innovative architectural separation of storage and compute. It supports instant database branching (similar to Git branches, allowing you to isolate environments for staging/testing) and scales down to zero when not in use to save costs. Supabase : An open-source alternative to Firebase that is entirely built on top of standard PostgreSQL. Instead of just providing a raw database connection, Supabase bundles your Postgres instance with authentication, auto-generated REST APIs, storage, and real-time listeners. Prisma Postgres : A specialized, operation-based serverless Postgres built on unikernel microVMs. It is designed with zero cold starts and a pricing model built around the total number of operations rather than provisioned RAM or CPU, allowing it to scale fluidly with applications.\n\n2. Independent Postgres Specialists & PaaS\n\nIf your workload is resource-intensive or you prefer predictable, provisioned hardware over a serverless model, these platforms offer deep database configuration without vendor lock-in.\n\nCrunchy Bridge : Built by Crunchy Data (longtime Postgres core contributors), this service provides managed Postgres across AWS, GCP, and Azure. It gives you raw, high-performance database access with professional-grade extensions (like PostGIS and pg_vector ) without the typical hyperscaler operational guardrails. Aiven for PostgreSQL : A multi-cloud data platform that lets you deploy standard, un-forked PostgreSQL on your choice of cloud provider (AWS, GCP, Azure, etc.). It is widely used by companies that want to collocate their database alongside other managed open-source systems like Kafka or OpenSearch in a unified control plane. Render / DigitalOcean Managed Databases : Perfect choices for small-to-medium business apps where simplicity and flat, predictable billing are the priorities. They bundle automatic daily backups, point-in-time recovery (PITR), and connection pooling into a straightforward, fixed monthly infrastructure cost.\n\n3. Cloud Hyperscalers (The Enterprise Defaults)\n\nWhen your application backend is completely deployed inside a major cloud environment, hosting your database natively minimizes network egress fees and latency.\n\nAmazon RDS for PostgreSQL : The industry baseline for enterprise production apps. It handles automated scaling, high availability, and backups perfectly, though configuring IOPS, storage tiers, and instances can lead to variable monthly bills. Amazon Aurora PostgreSQL : A distributed, cloud-native storage engine layered on top of Postgres. It is the elite choice for high-throughput, massive enterprise systems requiring automatic storage scaling, multi-region replication, and rapid read-scaling. Google Cloud SQL for PostgreSQL : Google's native relational database solution. It is a straightforward, highly reliable offering that features independent scaling of compute and memory, automated maintenance, and integrated AI-assisted operations.\n\nDirectly Comparing the Top Options\n\nProvider Operating Model Key Advantage Best For\nNeon Serverless Database branching & scale-to-zero Fast-moving development teams & preview environments\nSupabase BaaS Full application stack built around Postgres Startups looking to avoid building Auth/APIs from scratch\nCrunchy Bridge Dedicated Specialist Pure Postgres performance & expert support Mission-critical apps needing raw database access\nDigitalOcean Standard Managed Flat, highly predictable pricing Simple web applications and side-projects\nAmazon RDS Hyperscaler Native Seamless integration with AWS infrastructure Traditional enterprise deployments situated on AWS\n\nTo help narrow down the ideal platform, could you share where your main application code is hosted (e.g., Vercel, AWS, Render), the estimated size of your database, and whether you need specialized extensions like PostGIS or pg_vector ?","extractedBrands":[{"name":"Neon","domain":null,"position":1},{"name":"Supabase","domain":"supabase.com","position":2},{"name":"Prisma Postgres","domain":null,"position":3},{"name":"Crunchy Bridge","domain":"crunchydata.com","position":4},{"name":"Aiven for PostgreSQL","domain":"aiven.io","position":5},{"name":"Render","domain":"render.com","position":6},{"name":"DigitalOcean Managed Databases","domain":"digitalocean.com","position":7},{"name":"Amazon RDS for PostgreSQL","domain":"amazon.com","position":8},{"name":"Amazon Aurora PostgreSQL","domain":"amazon.com","position":9},{"name":"Google Cloud SQL for PostgreSQL","domain":"cloud.google.com","position":10}]},{"provider":"grok","run":1,"model":"grok-4.3","capturedAt":"2026-11-01T05:10:30.097Z","text":"**The best Postgres hosting providers depend on your workload, existing cloud ecosystem, need for features like branching or auth, and priorities around cost predictability vs. flexibility.** There is no universal top choice, but several stand out consistently across 2025–2026 comparisons as the ones developers and teams actually use in production.[[1]](https://swyftstack.com/blog/best-postgresql-hosting-providers)[[2]](https://encore.dev/articles/best-postgresql-hosting)[[3]](https://www.lilachbullock.com/best-postgres-hosting/)\n\nHere are the most frequently recommended and widely adopted options, grouped by category:\n\n### Hyperscaler / Enterprise Defaults (Most Widely Deployed)\n- **AWS RDS for PostgreSQL (and Aurora PostgreSQL)**: The default for many production workloads, especially AWS-native teams. It offers strong high availability (Multi-AZ), read replicas, automated backups/PITR, broad extension support (including pgvector), and deep IAM/VPC integration. Aurora adds faster failover, serverless v2 options, and better scalability for variable loads. Widely used due to ecosystem lock-in and enterprise features.[[4]](https://www.bytebase.com/blog/postgres-hosting-options-pricing-comparison/)[[5]](https://www.itechguides.com/best/postgresql-hosting/)[[6]](https://queryplane.com/docs/blog/top-managed-postgresql-cloud-providers)\n- **Google Cloud SQL for PostgreSQL (and AlloyDB)**: Strong choice for GCP users, with good integration, HA, and analytics-friendly features in AlloyDB.[[2]](https://encore.dev/articles/best-postgresql-hosting)\n- **Azure Database for PostgreSQL (Flexible Server)**: Solid for Microsoft-centric environments, with features like stop/start and hybrid options.[[3]](https://www.lilachbullock.com/best-postgres-hosting/)\n\nThese are battle-tested at scale and often the \"safe\" pick for larger or compliance-heavy setups.\n\n### Developer-Friendly / Modern Serverless Options (Popular for Startups & Apps)\n- **Neon**: Frequently praised for serverless Postgres with true scale-to-zero (after idle), instant copy-on-write database branching (ideal for previews, tests, or per-PR environments), and usage-based pricing. Strong free tier and great for spiky/dev/AI-agent workloads. It's a top pick when you want Postgres without always-on costs.[[1]](https://swyftstack.com/blog/best-postgresql-hosting-providers)[[7]](https://neon.com/guides/best-postgres-hosting-saas-and-ai-agents-2026)[[8]](https://nearbase.dev/blog/best-postgres-hosting/)\n- **Supabase**: Postgres at the core, bundled with auth, realtime subscriptions, storage, REST/GraphQL APIs, and edge functions—positioned as a Firebase alternative. Very popular for full-stack apps and rapid development; sees heavy use (including AI-assisted projects). Free tier available, with paid plans starting around $25/mo.[[1]](https://swyftstack.com/blog/best-postgresql-hosting-providers)[[3]](https://www.lilachbullock.com/best-postgres-hosting/)[[9]](https://dreamlit.ai/blog/top-10-managed-postgres-providers)\n\n### Other Strong Contenders (Niche but Actively Used)\n- **DigitalOcean Managed PostgreSQL**: Simple, predictable flat pricing, good for smaller/steady workloads. Popular among teams already on DigitalOcean.[[1]](https://swyftstack.com/blog/best-postgresql-hosting-providers)[[4]](https://www.bytebase.com/blog/postgres-hosting-options-pricing-comparison/)\n- **Crunchy Bridge**: Run by Postgres experts (Crunchy Data); offers near-full Postgres access (superuser-like, broad extensions), multi-cloud (AWS/GCP/Azure), and strong support. Favored by those wanting fewer restrictions than hyperscalers.[[2]](https://encore.dev/articles/best-postgresql-hosting)[[10]](https://chat2db.ai/resources/blog/best-postgres-hosting-providers-2026)\n- **Render**: Convenient when hosting your full app + DB on one platform; straightforward for smaller teams.[[8]](https://nearbase.dev/blog/best-postgres-hosting/)\n- **Aiven**: Multi-cloud managed Postgres with a free tier and integration with other open-source data tools.[[3]](https://www.lilachbullock.com/best-postgres-hosting/)\n\n### Quick Decision Guide\n- **Already on AWS/GCP/Azure** → Start with RDS/Aurora, Cloud SQL, or Azure Flexible Server.\n- **Spiky traffic, dev branches/previews, or cost-sensitive idle time** → Neon.\n- **Need auth, realtime, storage, or a full backend platform** → Supabase.\n- **Predictable flat bills for small/steady apps** → DigitalOcean or Render.\n- **Want Postgres purist experience with expert support** → Crunchy Bridge.\n- **Prototyping or low-traffic** → Neon or Supabase free tiers.\n\nOther mentions include PlanetScale (newer Postgres focus with branching/HA), Railway (app + DB together), Heroku Postgres (legacy/simple), and self-hosting on VPS (cheapest but highest ops burden).[[4]](https://www.bytebase.com/blog/postgres-hosting-options-pricing-comparison/)\n\n**Pricing varies widely** (usage-based vs. fixed instances; free tiers on Neon/Supabase/Aiven; entry points often $5–25/mo or lower with credits). Check current details, as models evolve (e.g., Neon emphasizes CU-hours + storage; hyperscalers have multiple meters).[[4]](https://www.bytebase.com/blog/postgres-hosting-options-pricing-comparison/)\n\nFor the latest benchmarks or user experiences, look at sites like DBArena or community discussions on Reddit/HN. Test with free tiers where possible, as fit is highly use-case specific.","extractedBrands":[{"name":"AWS RDS for PostgreSQL","domain":"aws.amazon.com","position":1},{"name":"Google Cloud SQL for PostgreSQL","domain":"cloud.google.com","position":2},{"name":"Azure Database for PostgreSQL","domain":"azure.microsoft.com","position":3},{"name":"Neon","domain":"neon.com","position":4},{"name":"Supabase","domain":"supabase.com","position":5},{"name":"DigitalOcean Managed PostgreSQL","domain":"digitalocean.com","position":6},{"name":"Crunchy Bridge","domain":"crunchydata.com","position":7},{"name":"Render","domain":"render.com","position":8},{"name":"Aiven","domain":"aiven.io","position":9},{"name":"PlanetScale","domain":null,"position":10},{"name":"Railway","domain":null,"position":11},{"name":"Heroku Postgres","domain":"heroku.com","position":12}]},{"provider":"openai","run":1,"model":"gpt-6-sol","capturedAt":"2026-11-01T05:10:30.097Z","text":"If you want a **shortlist of established Postgres hosts people actually use**, start with **Amazon RDS, Google Cloud SQL, Supabase, Neon, and DigitalOcean**. The best choice depends less on a universal ranking than on where your app runs and how much database management you want to do.\n\n| Provider | Best fit | Main trade-off |\n|---|---|---|\n| **Amazon RDS for PostgreSQL** | A conventional, always-on production database when your app is on AWS. Multi-AZ failover is available. | More AWS configuration and cost decisions. **Aurora PostgreSQL** is a separate, PostgreSQL-compatible option worth evaluating for larger AWS workloads. ([aws.amazon.com](https://aws.amazon.com/rds/features/multi-az/?utm_source=openai)) |\n| **Google Cloud SQL for PostgreSQL** | The natural managed choice for apps on Google Cloud; offers backups, replicas, and optional high availability. ([docs.cloud.google.com](https://docs.cloud.google.com/solutions/setting-up-cloud-sql-for-postgresql-for-production?utm_source=openai)) | Less compelling if the rest of your stack lives elsewhere. |\n| **Azure Database for PostgreSQL – Flexible Server** | The equivalent default for Azure-based teams, with optional zone-redundant high availability. ([learn.microsoft.com](https://learn.microsoft.com/azure/postgresql/high-availability/concepts-high-availability?utm_source=openai)) | Primarily makes sense within Azure. |\n| **Supabase** | Building an app that also needs authentication, storage, and APIs—not just a database. ([supabase.com](https://supabase.com/solutions/hosted-postgres?utm_source=openai)) | Check your plan’s backup provisions: daily backups are provided on paid plans, not the free plan. ([supabase.com](https://supabase.com/docs/guides/platform/backups?utm_source=openai)) |\n| **Neon** | Serverless-style projects, variable traffic, and development workflows that benefit from database branching and scale-to-zero. ([neon.com](https://neon.com/platforms?a=01b7acb3-01f9-4bc8-81b3-206f0a80e812&utm_source=openai)) | Compare costs and behavior against an always-on instance for steady workloads. |\n| **DigitalOcean Managed PostgreSQL** | A straightforward standalone managed database for a smaller team. ([docs.digitalocean.com](https://docs.digitalocean.com/products/databases/postgresql/details/pricing/?utm_source=openai)) | Its single-node plan is not highly available; production HA requires a standby node. ([docs.digitalocean.com](https://docs.digitalocean.com/products/databases/postgresql/how-to/create/?utm_source=openai)) |\n| **Crunchy Bridge** or **Aiven** | PostgreSQL-focused managed hosting across major clouds, especially when specialist support or multi-cloud choice matters. ([crunchydata.com](https://www.crunchydata.com/?utm_source=openai)) | Compare regions, extensions, support, and full production pricing for your workload. |\n\n**My default picks:** choose **RDS, Cloud SQL, or Azure Flexible Server** if you’re already committed to that cloud; **Supabase** if you want a ready-made app backend; **Neon** for branching or intermittently used databases; and **DigitalOcean** if you want a simpler standalone host. Before committing, price the *production setup*—including backups, point-in-time recovery, and high availability—not just the smallest advertised instance. ([supabase.com](https://supabase.com/docs/guides/platform/backups?utm_source=openai))","extractedBrands":[{"name":"Amazon RDS","domain":"aws.amazon.com","position":1},{"name":"Google Cloud SQL","domain":"cloud.google.com","position":2},{"name":"Azure Database for PostgreSQL","domain":"learn.microsoft.com","position":3},{"name":"Supabase","domain":"supabase.com","position":4},{"name":"Neon","domain":"neon.com","position":5},{"name":"DigitalOcean","domain":"digitalocean.com","position":6},{"name":"Crunchy Bridge","domain":"crunchydata.com","position":7},{"name":"Aiven","domain":null,"position":8}]},{"provider":"perplexity","run":1,"model":"sonar","capturedAt":"2026-11-01T05:10:30.097Z","text":"The best widely used Postgres hosts are **AWS RDS/Aurora, Supabase, Neon, DigitalOcean Managed PostgreSQL, Render, Railway, Crunchy Bridge, Aiven, and Heroku Postgres**. The right choice depends mainly on whether you prioritize cloud-native operations, developer speed, serverless economics, or PostgreSQL expertise.\n\n| Provider | Best for | Why people choose it |\n|---|---|---|\n| **AWS RDS for PostgreSQL** | Production systems already on AWS | Mature backups, networking, IAM, replicas, monitoring, and broad regional availability. It is the safest general-purpose enterprise default. **Aurora PostgreSQL** is better when you need AWS-native high availability or larger-scale workloads.[1][2] |\n| **Supabase** | Full-stack startups and web/mobile apps | Managed Postgres bundled with authentication, APIs, storage, realtime features, and row-level security. It is more than a database, which makes it fast to build with.[1][7] |\n| **Neon** | Serverless apps, previews, and spiky workloads | PostgreSQL branching, autoscaling, and scale-to-zero are particularly useful for development environments and variable traffic.[2][6] |\n| **DigitalOcean Managed PostgreSQL** | Small teams wanting simplicity | Straightforward managed databases, predictable plans, and less operational complexity than the major clouds.[3][6] |\n| **Render Postgres** | Teams hosting the application on Render | Convenient when the app and database should live in one platform with unified deployment and billing.[2][7] |\n| **Railway** | Individual developers and small teams | Very fast app-and-database deployment, private networking, and a simple workflow for shipping prototypes or smaller production services.[2][6] |\n| **Crunchy Bridge** | Teams wanting deep PostgreSQL expertise | PostgreSQL-focused operations, strong portability, and features such as built-in connection pooling; a good alternative to hyperscaler-managed Postgres.[2][9] |\n| **Aiven for PostgreSQL** | Multi-cloud and portability requirements | Managed PostgreSQL across multiple cloud providers and regions, with a consistent operational model.[1][6] |\n| **Heroku Postgres** | Existing Heroku applications | Still a practical, familiar choice when the application already runs on Heroku and operational simplicity matters.[1][3] |\n\n## Practical recommendations\n\n- **Choose AWS RDS** for a serious production application if the team already uses AWS.\n- **Choose Supabase** if authentication, file storage, APIs, and realtime functionality are useful alongside Postgres.\n- **Choose Neon** for serverless applications, preview environments, database branching, or highly variable workloads.\n- **Choose DigitalOcean** for a conventional small-to-medium application where simple pricing and setup matter.\n- **Choose Render or Railway** when the application and database should be deployed together with minimal infrastructure work.\n- **Choose Crunchy Bridge** when PostgreSQL itself is mission-critical and expert database operations matter more than adjacent platform features.\n- **Choose Aiven** when multi-cloud availability or avoiding deep dependence on one cloud is important.\n\nFor most new startups, the shortlist is **Supabase vs. Neon vs. managed Postgres on AWS**. For a conventional production service, **AWS RDS** is the conservative choice; for the fastest developer experience, **Supabase** or **Neon** is usually better. These providers recur across current comparisons and are among the commonly used practical options rather than niche hosts.[1][2][3]","extractedBrands":[{"name":"AWS RDS","domain":"aws.amazon.com","position":1},{"name":"Aurora","domain":null,"position":1},{"name":"Supabase","domain":"supabase.com","position":2},{"name":"Neon","domain":null,"position":3},{"name":"DigitalOcean Managed PostgreSQL","domain":"digitalocean.com","position":4},{"name":"Render","domain":null,"position":5},{"name":"Railway","domain":null,"position":6},{"name":"Crunchy Bridge","domain":null,"position":7},{"name":"Aiven for PostgreSQL","domain":"aiven.io","position":8},{"name":"Heroku Postgres","domain":"heroku.com","position":9}]}]}