Calendula App
Next.js + managed DB, p95 latency 80ms across two continents.
Calendula is a calendaring app with 180,000 daily-active users split roughly 60/40 between North America and Europe. The team wanted a hosting partner that could host the Next.js front-end close to their users, a managed Postgres they could trust, and a billing line they could explain to their seed investors. Vintony was the third provider they evaluated and the only one that finished onboarding inside an afternoon.
p95 EU latency
80ms
Down from 220ms
p95 US latency
62ms
Held at parity
Trial → paid
+11%
Conversion lift in EU
Provisioning
afternoon
Start to live
The problem
The previous setup was a single-region Next.js deployment on a PaaS-style host that charged generously for bandwidth and stingily for compute. The team had spent two engineering weeks trying to add a European replica and given up; the PaaS made it possible but expensive. Latency for European users sat at 220ms p95, which was costing the team in trial-to-paid conversion — a metric they could literally see flip when measured per geo.
The migration
Onboarding was a single afternoon. They created two Vintony VPS pools — Ashburn and Frankfurt — fronted by Vintony's anycast load balancer with health-check routing. Postgres landed in Frankfurt as the primary with a hot-standby replica in Ashburn for failover. The Next.js builds went into Vintony's container registry and rolled out blue/green via the orchestration plane. Total migration time, including DNS warmup: six hours. The dashboard's per-region latency widget made the impact visible inside the first day.
“The dashboard is actually pleasant. Provisioning a server is one click, billing is transparent, and the docs are written by people who run servers.”
What's next
Calendula is adding a Singapore pool to serve their growing APAC user base, plus piloting Vintony's object storage to host avatars and ICS attachments that currently sit in a separate vendor.