Opportunities › Database scaling infrastructure for Postgres applications › Proposed app
Weirline
Postgres proxy that pools, routes and shards with no app changes
- Score
- 45
- confidence 61
- Evidence
- 10
- items on the page
- Rivals
- 5
- named in sources
- First version
- 90 d
- estimate
- Type
- Desktop app
- PWA: runs in the browser, installs on Mac and Windows
- Market since
- 2007
- Mature market · AI estimate
ScreensConcept
Desktop app: Backend engineers monitor dashboards, analyze load patterns, plan resharding, and query logs during extended work sessions at desks. Sample screens on a computer, in the proposed brand. Their numbers are sample data.
Overview
All routes healthy1,840 → 96
About this appAI proposal
Weirline is a network proxy that sits between your app and Postgres. It pools connections, sends reads to replicas, and spreads data across shards, so traffic spikes stop landing on one database. Your app keeps its current connection string and queries.
A web console, installable as a PWA, shows connection load, routing decisions and shard health. Platform engineers can plan a resharding, watch it run and roll it back from a phone when something pages them at night.
It is meant for backend and platform teams on self-hosted Postgres or managed services such as RDS, Azure and GCP. Unlike a plain pooler, it also balances load and coordinates queries across shards. Unlike an extension, it aims to avoid app refactoring.
- Tagline
- Let Postgres grow without rewriting your app.
- Voice
- CalmPrecisePractical
- Why this name
- A weir controls how water flows through a channel. Weirline does the same for queries: it shapes traffic so the database downstream stays steady.
In the first version
Members say which features they would use. It tells PWAS what people want; it changes no score.
Built-in connection pooling
Many app connections share a small set of database connections, so connection storms stop saturating database CPU. No separate pooler to run.
No member yet
Read and write routing
Reads go to healthy replicas, writes to the primary. Routing lives in the proxy, not in your application code.
No member yet
Transparent sharding
Spread tables across shards by a key you choose. The proxy sends each query to the right shard, so the app sees one database.
No member yet
Cross-shard queries
Counts, sums and sorts that span shards are combined by the proxy and returned as one result set.
No member yet
Brand identityAI proposal
Check the name against trademark registers before using it.
Palette
#0F5C6EDeep Channel · primary#F4F1EAPaper · surface#1B2A2FInk · text#E07A2FSpillway · accent#3E8E5BReed · data, healthy status
Typography
Aa
Weirline
ABCDEFGHIJKLMNOPQRSTUVWXYZ 0123456789
Let Postgres grow without rewriting your app.
PricingAI proposal
Citus's pricing page lists one paid plan, priced by usage at $0.27, plus a free plan; the material does not give the unit. Our tiers are a starting point to test, with a free tier like theirs.
Free
Free
- One proxy, no sharding
- Pooling and read routing
- Basic console
Team
$149 a month
- Up to 4 shards
- Cross-shard queries
- Resharding plans with rollback
- Alerts and query insights
Scale
$690 a month
- Up to 16 shards
- Multiple proxies per cluster
- SSO and audit log
- Priority support
Would you pay Team · $149 a month?
Your answer tells PWAS which prices people accept. It changes no score.
No answers yet.
What it could be worthEstimate
What a software business making this much sells for today, from real deals. Pick a monthly revenue.
If it makes
Worth about
$194,000
Sale range $132,000 to $263,000
$120,000 a year in revenue
From 87 software businesses listed and sold on Empire Flippers in the last year, revenue vetted by the broker: they sell for about 19× their monthly revenue, most between 13× and 26×.
Measured on profit, the middle deal is 32× monthly net profit: about 2.7 years of profit.
An estimate, not an offer or financial advice. A real price depends on profit, growth, churn, how much of the work is the owner's, and the buyer.
How it would growAI proposal
How the product would reach new customers through its own use, and how the first ones would be found. A plan to test, not a result.
- Built-in loop
- No loop in the product. Weirline runs inside a customer's infrastructure and is not seen by their users. It reaches new customers through content, open guides, talks and direct outreach to platform teams.
- Do they become customers?
- Only direct sales and content bring customers. Test whether teams with a live scaling problem will start on the free tier and pay for sharding and resharding tools.
- First customers
- Platform engineers at startups of 20 to 200 staff running self-hosted or RDS Postgres, whose primary database is near its connection or write limits.
- Where to reach them
- Hacker News and Postgres forums: Publish a worked scaling write-up with the numbers, and answer pooling and sharding threads with the free tier.
- Postgres community events: Give talks and run a booth on moving from a single database to shards without app changes.
- Direct outreach: Message engineers who post about connection storms or slow resharding and offer a hands-on pilot.
- First milestone
- Five teams run Weirline in front of production Postgres, and two pay for the Team plan within 90 days.
Why people already pay for this
- VerifiedHacker News post received 326 points and 63 comments
- Public claimDatabase becomes the bottleneck as application traffic grows
- Public claimPgDog is in production use with sharding at scale
- Public claimResharding at Instacart previously took over two weeks for 10TB; PgDog reduces this to hours
- AI inference
Tech stack
Every proposal builds on the same PWA base, installable from the browser on any phone or computer. Dashed boxes are what this app adds.
- AppNext.js and TypeScript
- PWAManifest and service worker
- UITailwind CSS
- Data and authSupabase Postgres
- PaymentsStripe
- EmailResend
- HostingVercel
- This app · Proxy data planeStandalone Postgres wire-protocol proxy, in Rust or GoQuery routing must run as a low-latency network service. A Next.js app cannot do this.
- This app · Proxy hostingCustomer-run containers and Helm chartThe proxy must sit in the customer's network, close to their database. Vercel cannot host it.
RisksAI inference
- TechnicalCorrect cross-shard queries and atomic cross-shard writes are hard. Unsupported SQL could return wrong results, so the first version needs a clear list of supported queries.
- CommercialAn open-source proxy already claims no-code-change sharding, and Citus has a free plan. Buyers may self-host or stay on a free option, so paid value must come from the console and resharding.
- TechnicalA proxy adds a network hop and becomes a critical failure point. Teams will want proven latency numbers and failover behaviour before routing production traffic.
- DataResharding moves large data sets, and a mistake can lose or duplicate rows. Early customers will ask for verification checks and rollback before trusting it.
- PlatformManaged services such as RDS, Azure and GCP limit replication settings and permissions. Some features may not work on every provider and version.
Everything marked AI proposal or AI inference was written by a model from the evidence on the opportunity page. The proposed name must be checked against trademark registers before it is used.