Heedza
Start free

For apps made with AI tools

Know when your Replit app stops working

Replit makes it easy to go from an idea to a live app at a replit.app address or your own domain. But the live app runs with its own settings, keys and database, so it can behave differently from the preview. Heedza opens your live Replit app the way a visitor does, on a schedule, and checks that your home, sign-up, log-in and payment pages still open and show their forms. If one stops working, we send you a picture of the page and a fix to paste into Replit.

Start free with 1 siteOr run a free scan first

Common ways published Replit apps break

From Replit's own troubleshooting docs. Under each one, “Heedza sees this” means the problem stops a page from opening or removes its form, so you get an alert. Heedza only sees what a visitor sees before logging in, so it can’t see problems that happen after a form is sent.

  1. Secrets didn't come along. "Secrets you set in the Project Editor do not automatically carry over to your published app." Missing secrets can cause "login errors, or payment failures" (Replit: Troubleshoot publishing). Heedza sees this only if a page stops opening. It can’t see a log-in that fails after the button is pressed, because it never logs in.
  2. Static deployments have no secrets. "Secrets are available for all deployment types except Static Deployments" (Replit: Secrets). Heedza sees this only if a page stops opening.
  3. The server listens on the wrong address. Your app is set to answer only on your own computer, not on the internet. Replit says it "must listen on 0.0.0.0. Listening only on localhost or 127.0.0.1 does not work for published apps." With ports set in .replit, you need externalPort set to 80 (Replit: Troubleshoot publishing). Heedza sees this.
  4. A slow homepage fails the health check. "If your homepage takes more than five seconds to respond, the health check can time out and publishing can fail at the final step" (Replit: Troubleshoot publishing). Heedza can’t see the cause. You only notice that your change isn’t on the live site.
  5. Hard-coded localhost URLs and unrun migrations. Replit lists these, plus missing production secrets, as the main reasons a deployed app fails (Replit: Networking and app errors). Heedza sees this.
  6. A crash shows as an error page (code 502). "A 502 usually means your app process crashed" (Replit: Networking and app errors). Heedza sees this.
  7. The publish succeeded but the app returns 500. Replit says the issue is then in your app code; you can redeploy the last working version from Publishing → History (Replit: Deployment and publishing). Heedza sees this.

What Heedza checks

Heedza works from the outside, on your public web address. There's nothing to install.

  • Your key pages. We open your home page the way a visitor does, follow its links to your sign-up, log-in and payment pages, and check on a schedule that each one opens and shows its form or Pay button.
  • Security checks. The free scan looks for secret keys in your page code and .env or .git files anyone can open.
  • Alerts. When a check fails, you get an alert (by email, or on paid plans also Slack, Telegram or a webhook (we send the alert to a web address you choose; for developers)) with a picture of the page and a fix written for Replit, ready to paste into the Replit chat.

It never fills in forms, never logs in, never types a card number and never clicks Pay. So it can't tell you whether a log-in, email or payment works after the button is pressed.

It works the same for any vibe-coded app, whichever AI tool made it. Build Replit apps for clients? See Heedza for agencies: up to 30 client sites, with white label client reports and status pages on Business.

Fix it for me (Pro and Business)

Some alerts have a Fix it for me button. Nothing starts until you press it. Heedza then writes the fix and suggests it on GitHub (a pull request). Nothing changes in your app until you approve it, and you can undo it.

It works for a page Heedza checks that stopped working (such as sign-up, log-in or payment), a file that should not be public, and a security setting your site stopped sending. It needs your app’s code in a GitHub project (repository), with the Heedza GitHub app added to it. Other alerts come with a fix to paste into your AI tool. How Fix it for me works

Run a free scanSee prices

Questions

Is Heedza a Replit product?

No. Heedza is independent and not affiliated with Replit. It checks your public web address from outside and needs no access to your Repl.

Will Heedza's checks wake my Autoscale deployment?

Each check is a normal page visit, so it behaves like any visitor. Replit notes that with Autoscale, the first request after a quiet period can take a few seconds (a cold start) (Replit: Networking and app errors).

Does it check my API or database?

No. It checks the pages a customer uses to get in. It does not read your database.

Can it check a private deployment?

Not past its login. Heedza never logs in.

Is the fix written for Replit?

It's written for the tool you built with, and Replit is one of the tools Heedza writes fixes for. It describes the URL and what failed; review the changes before republishing.

Where this comes from

Heedza is an independent service. It isn't affiliated with, endorsed by or a partner of Replit. Replit is a trademark of its owner.