Skip to content
InnoStak Pulse

Find out before your customers do

Website and app health monitoring for businesses and agencies.

Don't wait for an angry email to learn your site is down. Pulse checks your apps around the clock, alerts you within minutes, and tells you what broke, who it affects and where to look. Be proactive, not the last to know.

Now onboarding pilot customers. Business email required.

Checks every 5 minutes

On the pilot plan · Vercel · Supabase · HTTPS

Proactive beats panic

Uptime monitoring that explains what broke.

Most teams find out something broke from a customer, a support ticket or a 2 a.m. “is the site down?” text. Pulse flips that. It checks the URLs your customers depend on, reads what Vercel and Supabase expose, and tells you what failed, who's affected and where to look next — so you get ahead of it instead of hearing about it.

  • You hear it first

    Incident alerts by email (and opt-in SMS) within minutes of repeated failed checks.

  • Evidence, not vibes

    Metrics are calculated first, and every actionable claim links back to the checks behind it.

  • Plain language or full detail

    Owners get the what and the why. Developers get the timestamps and status codes. Same facts.

  • Agency-ready

    Monitor every client from one workspace. Clients only ever see their own.

No more surprises

Website monitoring, incident alerts and AI health reports in one place

Pulse sticks to what it can measure reliably today. No SDKs, no agents, no code changes — and no invented numbers when a provider doesn't share the data.

  1. 01

    Safe HTTPS availability checks

    Scheduled checks on public URLs you verify — every five minutes on the pilot plan.

  2. 02

    Incidents without the noise

    One blip won't page you. An incident opens after consecutive failures (three by default) — then acknowledge, assign, resolve.

  3. 03

    Vercel and Supabase integrations

    Deployment status and project health, read the way your providers allow.

  4. 04

    Weekly evidence-linked AI report

    What happened this week, with confirmed facts kept separate from suspicions. No guessing at root causes.

  5. 05

    Email alerts and opt-in SMS

    One message when it breaks, one when it recovers. No notification storms.

  6. 06

    Honest data states

    Stale, disconnected or unsupported data is never dressed up as healthy. No false all-clears.

  7. 07

    Agency portfolio

    Summary health across all your client organizations, with a clear scope breadcrumb.

  8. 08

    Client-scoped access

    Invite client users to their own organization. They never see your other clients.

  9. 09

    Read-only where possible

    We request the narrowest scopes each provider offers, and tell you when a provider only offers broader access.

  10. 10

    Encrypted credentials

    Designed to encrypt provider tokens in the application before storage, with the key held outside the database.

  11. 11

    Tenant isolation

    Built so every workspace, organization and project is isolated at the database level.

  12. 12

    Audit logs

    Designed to record incident changes, access changes and staff support sessions.

Three steps to calm

How Pulse website monitoring works

Paste a URL, invite your team, and Pulse does the watching. Nothing to install and no code to change — get on with your day.

  1. Step 1: Connect Vercel, Supabase and your URLs

    Authorize Vercel and Supabase with read access wherever the provider allows it, then add the public HTTPS URLs your customers actually use.

  2. Step 2: Pulse checks every five minutes

    Safe, scheduled HTTPS availability checks run around the clock, alongside the deployment and health data your providers make available.

  3. Step 3: You get the heads-up — and the evidence

    Failures become incidents you can acknowledge and assign. A weekly AI health report sums up what happened, with links to the proof.

Rolling out

More than a red dot

AI health reports with answers from your engineer and your DBA.

Pulse's AI reads the evidence and tells you what it sees, what to do, how long it takes and what it costs you — from the owner, engineering and database point of view. AI reports ship alongside monitoring during the pilot.

  • Every recommendation comes with effort, impact, pros and cons, risk and who should do it.
  • Confirmed facts are kept apart from suspected causes, with the evidence linked.
  • It tells you when a fix is beyond your team — and when to call in help.
Weekly AI health report · finding 1 of 3Illustrative preview
MajorConfirmedHigh confidence

Checkout slowed down Tuesday 2:10–2:50 PM

Affected: Customers paying at checkout

What happened

ConfirmedFor about 40 minutes on Tuesday afternoon, customers trying to pay waited 4 seconds or more for the checkout page. It recovered on its own at 2:50 PM.

Why it matters

Slow checkouts cost sales: some customers likely gave up. Nothing was lost or charged twice, but it will happen again under the same load unless it's fixed.

Evidence

  • Incident #7
  • Checkout checks · Tue
  • DB connections · 1h
  • Deploy · 13:58

Database fix

Close idle transactions automatically

under 1 hourLow riskReversible

Effort basis: One configuration change, applied without downtime.

  1. 1.Set idle_in_transaction_session_timeout to 60 seconds on the app's database role.
  2. 2.Watch connection counts during the next import run.

Impact: Frees stuck connections so checkout stays responsive while jobs run.

Pros

  • Immediate relief
  • No code changes
  • Easy to undo

Cons

  • Long legitimate transactions over 60 s would be cut off

Who: Your database admin

Engineering fix

Batch the job's database writes

1–2 daysMedium riskReversible

Effort basis: One job to refactor and test against a production-sized import.

  1. 1.Reuse one pooled connection for the whole import run.
  2. 2.Write items in batches of ~500 inside short transactions.
  3. 3.Run the job outside peak checkout hours until it's changed.

Impact: Removes the root pressure on the database, so imports and checkout can run together.

Pros

  • Fixes the cause, not the symptom
  • Imports get faster too

Cons

  • Needs developer time and testing
  • Batch failures need retry handling

Who: Your developer

Stuck? Hand this finding to InnoStak engineers(opens innostak.com in a new tab)
Illustrative preview of a Pulse AI health report finding with sample data, showing owner, engineering and database views and two recommendations.
Rolling out

No more “is it down?” emails

Put your status where your customers already are.

One line of script on your site shows live health from your Pulse checks, so customers can see for themselves instead of emailing you to ask.

  • Shows the same checks Pulse runs every five minutes — nothing made up for the widget.
  • Install is a copy-paste snippet. No build step, no SDK.
  • You choose which components are public. Everything else stays private.

Acme Status

Powered by Pulse

Minor slowdown: API · checked 3 min ago · checks every 5 minutes

  • WebsiteWorking normally142 ms
  • Sign-inWorking normally100% today
  • APIA little slow1.9 s
  • DatabaseWorking normally100% today
  • Checkout pageWorking normally188 ms

Last 30 days

99.94% uptime

  • Good
  • Fair
  • Slow
  • Problem
  • Today ›
Illustrative previewSample data
Illustrative preview of the Pulse status widget with sample data: all systems operational, API a little slow, 99.94% uptime over the last 30 days.

Same facts, different depth

Health reports for owners and developers

No more translating a stack trace for your boss or your client. Everyone looks at the same evidence — Pulse just changes the level of detail.

Owner view

A plain-language picture of your business's software, without the jargon.

  • What failed, which customer workflow it affects, and for how long
  • How confident we are, and who is responsible for the next step
  • Open issues, weekly reports, team and billing in one place
  • Clear “unknown” and “stale” states — never a false all-clear

Developer view

The detail you need to investigate, with units, time ranges and freshness on every chart.

  • Environment status, response-time trends and check run history
  • Deployment correlation from Vercel alongside incident evidence
  • Connection diagnostics and available Supabase health data
  • Zero errors is shown differently from zero samples received
Pilot pricing

Simple website monitoring pricing. No overage surprises.

Monthly billing through Stripe, cancel anytime, and no surprise overage charges — usage simply stops at your plan's limit.

Straight answers

Website monitoring FAQ

What does Pulse actually monitor?
Scheduled HTTPS availability checks on URLs you choose, plus data your providers expose through their APIs — for example Vercel deployment status and Supabase project and service health. When a provider doesn't give us a measurement on your plan, we show it as unavailable instead of guessing.
How quickly will I hear about an outage?
Within minutes. Checks run on a schedule (every five minutes on the pilot plan), and an incident opens after several consecutive failures — three by default — so a single blip doesn't wake anyone up. We notify once when it opens and once when it recovers.
Do I need to install an SDK or change my code?
No. Pulse starts with external checks and provider integrations. Deeper signals such as request tracing or browser errors are not part of the launch product.
Will Pulse fix problems for me?
No. Pulse explains what failed, who is affected, and suggests where to investigate. It never changes your code, your deployments or your database.
Can agencies use it for multiple clients?
Yes. An agency workspace holds a portfolio of client organizations. Client users only see their own organization. Agencies bill their own clients; Pulse bills the agency workspace.
Who can sign up?
Anyone with a business email address. We're currently onboarding pilot customers.

Stop learning about outages from angry emails.

Start your pilot: connect Vercel and Supabase, add the URLs your customers depend on, and get your first weekly health report. Business email required.

Backup when you need it

Your developer's stuck? Ours aren't.

Pulse is built by InnoStak, a software engineering and automation partner. When a fix is beyond your team, hand it over with the evidence attached. Optional, and quoted separately from your Pulse plan.

Talk to InnoStak (opens innostak.com in a new tab)