Hobby
$29per month, billed yearly
For one person.
- 1 seat, 1 project
- Live chat and inbox
- In-app bug reporting
- Kai Support and Kai Copilot
You built it with Replit. Gleap runs the support and fixes the bugs.
Kai Support answers your users, Replit Agent fixes the bugs after one click from you, and the user hears back.
7 days free. No credit card needed.
Sofia Lindqvist
Mia Kellerman
Jonas Weber
Tom Alvarez Tomorrow
Ade Okafor
Priya Raman
Florian Berger
Kai Support handed the conversation to the team
Trusted by 4,500+ teams
Kai Support replies in the chat widget inside your Replit app, and by email.
After one click from you. Agent builds the change in the background.
Gleap follows up with the user only once Replit reports the app live.
Kai may publish is off until you switch it on for an app.
On autopilot
Gleap for Replit is an integration that adds AI customer support and bug fixing to the app you built with Replit. Kai Code works only through Replit Agent: it asks how the app works, requests the fix and, if you allow it, publishes. It never reads or writes your files. Connecting Replit needs Growth, at $99 a month billed annually.
I’ll find why the picker closes, then ask Replit to make the change.
The picker closes on blur, and Safari blurs the input before the day click lands.
The picker now stays open until a day is picked. Publishing it now.
The change is live: https://lumen-demo.replit.app.
Kai Code asks Replit Agent how that part of the app works.
In words, to Replit Agent.
And checks the status until Replit reports live or failed.
Kai Code never reads or writes them.
What runs without you
When a user describes something broken, Kai Support files the bug with the session attached. Replit Agent then explains how that part of the app works.
Meet Kai SupportIn the chat widget inside your Replit app and by email, from your help center and docs.
Kai Code · Merged · 2:30 PM
Once Replit reports the app live, Gleap replies on the user's original ticket.
In Kai Code settings, open Vibe coding, connect Replit with its own sign-in and add the apps Kai Code may work on. Kai may publish is off until you switch it on for an app.
Meet Kai CodeKai Code adds Gleap to Replit.
Kai Code asks Replit Agent to add the gleap npm package and one Gleap.initialize call in the client entry point, or the snippet in the head of a plain HTML site. The widget brings the AI chat, bug reports and your help center into the app.
I’ll ask Replit to add the Gleap widget once, in src/main.tsx, and change nothing else.
The app renders from src/main.tsx. Gleap goes there, before the first render.
Replit added the Gleap widget in src/main.tsx. Publishing it now.
The change is live: https://lumen-demo.replit.app.
Pricing
$29per month, billed yearly
For one person.
$99per month, billed yearly
For a support team on every channel.
$299per month, billed yearly
Everything in Growth, plus control.
7-day free trial. No credit card needed.Compare all features
Questions
Gleap for Replit is AI customer support and bug fixing for the app you built with Replit. Kai Support answers your users around the clock from your docs, bug reports arrive with a screenshot, replay and logs, and Kai Code asks Replit Agent for the fix. Once it's live, Gleap replies to the user who reported it.
Every plan starts with a 7-day free trial, and no credit card is needed. See pricing.
Start a Kai Code task and it asks Replit Agent to install Gleap: the npm package gleap with Gleap.initialize("API_KEY") once in the client entry point (src/main.tsx in Replit's React apps), or the loader snippet in the head of a plain HTML site.
Yes. Kai Support answers in the chat widget inside your Replit app, and by email, from your help center, docs and the sources you connect.
It hands a conversation to you when it can't help or the user asks for a human, and it recognizes bug reports and files them with the session attached.
When the fix is live, Gleap writes the reply on the user's original ticket. Turn on automatic follow-up and it sends by itself, right away or after a delay you set. Otherwise a teammate confirms first with one click.
Yes. Kai Code connects to Replit's official MCP server, and you approve access with your Replit sign-in (OAuth).
It asks Replit Agent questions, requests changes and, if you allow it, publishes and reads the publish status. It can't create apps or reach apps you didn't link.
Only if you switch on Kai may publish for that app. Kai Code then publishes and waits until Replit reports it live. Otherwise your team publishes in Replit and marks the change as published in Gleap.
Kai Code describes the change to Replit Agent in words, and Agent builds it in the background. Before that, Kai Code asks Agent how the relevant part of the app works, because it can't read the files itself.
No. On Replit, Kai Code works only through Replit Agent: it asks questions and requests changes. It never reads or writes the app's files.
Publishing on Replit runs in the background. After Kai Code starts the publish, it checks the publish status until Replit reports the app live or failed, and Gleap follows up with the user only once it is live.
Lovable, Replit, v0 and Base44, and code in GitHub, GitLab, Bitbucket and Azure DevOps. See Gleap for vibe-coded apps.