Questions, answered

The Starter trial runs for 14 days from the moment you connect Stripe. You get every Starter feature for the full window — no credit card required up front, no automatic downgrade at minute 14.

No. Trial sign-up only asks for your email and your Stripe connection. We do not collect a payment method until you choose to start a paid plan at the end of the trial.

Connect Stripe, see live revenue and subscription snapshots, fire a synthetic alert to verify your channels work, and explore the dashboard. The monitoring agent begins running as soon as your Stripe account is linked, so you can watch a real cycle end-to-end before committing.

If you upgrade to a paid plan, monitoring continues uninterrupted. If you do not, the connector pauses — your Stripe data stays in place but no new monitoring cycles run until you come back. Nothing is deleted.

From the dashboard billing page, click "Cancel plan." Cancellation is immediate and self-serve — no email-back-and-forth, no phone call. Your account drops to read-only at the end of the current paid period.

Yes. Once you cancel, you keep the full feature set until your current billing period ends. After that, the account moves to the trial-equivalent paused state — your data and channel list stay intact.

Monthly plans are non-refundable because the monitoring cycle, alerting, and storage all run on the days you pay for. If something breaks on our side, reach out and we'll credit the affected days.

Downgrading from Pro to Starter takes effect immediately on renewals. If you downgrade mid-cycle, you keep Pro features until the period ends, then settle into Starter on the next bill. No prorating on downgrade — same logic the other way around for upgrades.

Every charge emails a Stripe receipt to the address on file during checkout. The same receipt is also available in your Stripe dashboard under "Payments."

Monthly recurring revenue, daily revenue, new subscriptions, churned subscriptions, trial-signup volume, and ad spend. Each metric runs against a baseline — a sudden deviation fires an alert, not a constant stream of noise.

Yes. The heartbeat check fires a critical alert if no monitoring cycle has completed in the last 48 hours. That way a silent monitoring pipeline is the loudest thing that happens, not the quietest.

Every six hours on a scheduler in production. You can also trigger a manual cycle from the dashboard to see a fresh snapshot now.

Yes — spike and drop percentages, cooldown windows, and per-metric thresholds are configurable per company. Defaults are sensible for most SaaS, but if your business has a spiky revenue curve, tightening or loosening thresholds takes about a minute.

Slack channels via incoming webhooks, and email via the Polsia authenticated email proxy. Both channels can be configured, tested, and removed at any time from the dashboard.

Yes. A single alert can fan out to every configured channel — for example, Slack for the engineering channel and email for the founder. Add as many of either type as you need.

The dashboard exposes a "Send test alert" button per channel. It fires a synthetic alert through the same dispatch path real alerts use, so you see exactly what your team will see and confirm the channel is wired correctly.

No. Each alert type has a configurable cooldown (by default 60 minutes), so a sustained anomaly produces one alert per cooldown window rather than one every six hours.

Create an incoming webhook in your Slack workspace (Settings → Apps → Incoming Webhooks), paste the URL into the channels page, and save. The next monitoring cycle — or a test alert — will deliver there.

Enter the email address on the channels page. We verify each address with a confirmation link before it goes live, so a typo can't accidentally send revenue alerts to the wrong inbox.

Yes — channels can be deleted from the dashboard at any time, with no effect on historical alert data.

From the pricing page, choose the Pro tier and complete checkout. The change is immediate — no migration step needed because both tiers share the same data model.

More companies (if you monitor more than one Stripe account), longer alert cooldowns are configurable, more channels per alert rule, and higher API rate limits for power users.

No. Upgrades take effect immediately and the next bill is the full Pro price. Pro features stay on through the paid period, so you only pay once for the cycle you upgraded on.

Yes — see the "downgrades" question in the billing section above. You'll keep Pro features until the current period ends, then drop to Starter on the next bill.

Stripe is the only first-party source today. Pingpilot reads your Stripe account in read-only mode through the Polsia Stripe integration — never write, never modify charges or customers.

The monitoring cycle runs every six hours, so each cycle sees the previous six hours of Stripe events. Manual triggers from the dashboard give you an immediate on-demand snapshot.

Yes — additional first-party sources beyond Stripe are on the roadmap. The data-layer and alert engine are source-agnostic, so new sources slot in without changing alert behavior.

No. The Stripe connection is strictly read-only — we can't touch charges, customers, products, or subscriptions. The scope is enforced by Stripe at the API level, not just by our code.

In a managed PostgreSQL database hosted on Neon. Each company's rows are scoped by company_id, so one customer's monitoring data is never visible to another.

Only the channels you configure. Alerts fan out to Slack webhooks and email addresses you explicitly add, and each channel can be removed at any time. Nobody at Pingpilot reads alert contents.

Email support@pingpilot.app — that's the inbox a real person on the team reads. If your question is urgent, mention "urgent" in the subject line and we'll prioritize.

One business day for most questions, often faster. Critical pipeline issues (alerts not firing, wrong data) jump the queue.