Tell us what you’re dealing with. We’ll tell you exactly what we’d look at first, what it would take to fix it, and whether PGFlare is the right fit. No commitment required.
Pick any 30-minute slot that suits you. You’ll get a calendar invite immediately with a Google Meet or Zoom link.
Before the call, Cal.com prompts you for a few quick details: PostgreSQL version, instance class, peak load, and what symptoms you’re seeing. This lets us prepare, not improvise.
We’ll walk you through what we’d investigate first and the most likely remediation path. You leave with a concrete recommendation whether or not you engage PGFlare.
Yes, completely. There’s no obligation to purchase anything. We run discovery calls because talking directly with engineering teams is the fastest way to understand whether PGFlare can genuinely help — and if we can’t, we’ll tell you that directly.
Ideally: your PostgreSQL version (e.g. 16.x), instance class (e.g. db.r6g.2xlarge),
and an idea of peak query volume. If you have specific slow queries already identified, bring
those. If not — no problem — we’ll talk through how to surface them using
pg_stat_statements.
Not for the discovery call. We talk through the problem first. If you decide to proceed, we’ll walk you through our read-only IAM role setup (see the IAM setup guide) — and that’s the only access we ever need.
No — for active production incidents, skip the call entirely and go straight to Emergency Response. Use the contact form and select “Emergency Response” — we respond within 2 hours, 24/7.
We use Cal.com — an open-source scheduling platform. It connects to Google Calendar and Outlook/Office 365, sends automatic reminders, and lets you reschedule without emailing us. Your booking data is not used for any purpose other than scheduling this call.
Use the contact form to describe your situation in writing. We’ll respond within 24 hours and suggest next steps.
Send an Enquiry →