Monitor your Replit app.

How a Replit app runs in production

Publishing a Replit app — what Replit used to call deploying it — runs it as an Autoscale, Reserved VM, Static or Scheduled deployment, on a replit.app address or your own domain.

Replit gives an app its own PostgreSQL database, with separate development and production copies, Replit Auth for sign-in, and a Stripe integration. The Git pane pushes to and pulls from a GitHub repository.

What breaks after launch

• It works in preview and breaks in productionReplit’s own troubleshooting guide says secrets set in the workspace do not automatically carry over to the published app — the usual reason sign-in or payments work in the editor and fail live.How to tell, and the fix
• Sign-in breaks on your new domainA callback or redirect URL that still names the development address fails once the app answers on its published domain.How to tell, and the fix
• Payments stop after a deployA Stripe webhook pointing at the development address, or a signing secret missing in production, means payments succeed at Stripe and never reach the app.How to tell, and the fix
• The site is downA published app that does not answer its health check in time never comes up; Replit’s guide gives the home page five seconds.How to tell, and the fix

What Keelnest watches

• The site, every five minutes

  The address, its certificate and its security headers, requested the way a browser asks; an incident opens after two failures in a row, never on one blip.

• Every publish

  Replit announces no publish to anyone else, so every check fingerprints the live page; a new version is checked within five minutes and walked by your journeys.

• Sign-in and checkout, in a real browser

  Walked after every publish and on your plan’s schedule, sign-up emails and magic links included; a payment journey stops before the pay step.

• Payments

  A read-only Stripe key compares payments with what that hour of the week usually brings, and reads webhook endpoints and failed deliveries.

  Stripe

• AI spend

  OpenAI or Anthropic usage, read hourly, so a spike is caught within a few hours; paid plans add a daily budget that warns at 80% and alerts at 100%.

  OpenAIAnthropic

• Errors

  One script tag reports uncaught errors and failed requests — never form values or request bodies — so an incident says what broke. Sentry works too.

  Error captureSentry

Fixes: a prompt, or a pull request

Every incident carries a prompt you can give Replit Agent, never asking for a secret. With the project connected to GitHub and a paid plan, Keelnest can prepare the fix as a pull request instead; once a named person approves it and it merges, pull it into the project from the Git pane.

Setting it up

1. Add the published address — replit.app or your own domain. The first check runs straight away.
2. Connect Stripe with a restricted key if the app takes payments, and OpenAI or Anthropic with an admin key if it calls a model.
3. Write one journey — sign in, or reach the checkout — in plain words. It is walked after every publish.
4. For fixes as pull requests, connect the project to GitHub from the Git pane and install the Keelnest GitHub App on that repository.

Or start without an account: the free health check reads any live address in a few seconds.

Questions

Sources

What Replit does, as its own documentation described it on 23 September 2026. Builders change quickly; if something here is out of date, tell us.

• Replit · Deployment types
• Replit · Troubleshooting deployments
• Replit · Production databases
• Replit · Git

Other builders

• Lovable
• Bolt
• v0
• Cursor