Skip to content
Irfan Habib, co-founder of Plutonapps

Irfan Habib

Co-Founder, Plutonapps

Co-founder of Plutonapps, in the IT industry since 2017, and a coder by passion who became a T-shaped product developer, Irfan works on distributed systems and leads Plutonapps' engineering, where the team builds AI products with its clients and turns AI-built apps into dependable production software. He studied at the Indian Institute of Science Education and Research (IISER) Pune.

Articles

Stripe Connect in a Lovable app: pay sellers

Adding Stripe Connect to a Lovable marketplace: what Lovable covers, connected accounts, charge types, seller onboarding, payouts and webhooks.

Lovable post-launch checklist for founders

What to check in the first days and weeks after your Lovable app goes live: errors, backups, access rules, email, payments, domain, costs and who is on call.

How to read an AI-built backend for security

A plain-English walk-through for non-technical founders: how to sanity-check the backend an AI builder generated, and when to call an engineer.

Lovable app slow with real users? Find out why

Why a Lovable app that was fast in testing gets slow with real users, how to find the cause in DevTools and Supabase, and what to ask Lovable to fix.

Lovable emails going to spam: causes and fixes

Why sign-up, password-reset and receipt emails from a Lovable app land in spam or never arrive, how to find the cause yourself, and how to fix it.

Lovable users can see each other's data

Why one user of a Lovable app can see another's records, how to confirm it safely with two test accounts, what to do first if data leaked, and the fix.

Lovable API key exposed: what to do now

Which keys are safe in a Lovable app's browser code, what to do in the first hour after a leak, and how to move the key into a server-side secret for good.

Lovable security scan: what it misses

What Lovable's quick and deep security scans check, what they miss, what common warnings mean and what to do, and where a human review finds problems.

Lovable app: Stripe paid but user not upgraded

Why a Lovable app still treats paying Stripe customers as free, how to find the cause in Stripe and your logs, and how to fix affected customers for good.

Lovable Google login not working: the fixes

Fix Google sign-in in a Lovable app: redirect_uri_mismatch, login that only works in preview, the supabase.co consent screen and Google's Testing mode.

Why every Lovable fix breaks something else

Learn why a Lovable fix breaks other features and burns credits, how to stop the loop with version history and Plan mode, and when to call engineers.

Lovable blank page after publish: fixes

Find out why a Lovable app works in preview but shows a blank page, a 404 or endless loading once published, and how to trace and fix each cause.

Lovable Stripe integration: set it up safely

How the Lovable Stripe integration works, built-in payments vs your own Stripe account, and the webhooks, keys and tests a paying app needs before launch.

Vibe coding security risks, and how to fix them

The security risks of vibe coding: exposed data, leaked keys, trusting the browser, fake packages and unsafe AI features, with a test and a fix for each.

Lovable authentication and secure user roles

How to add sign-in and user roles to a Lovable app safely: where roles must live, how to protect admin areas, Google sign-in, MFA, and how to test it all.

Backups and disaster recovery for Supabase apps

What Supabase backs up on Free, Pro and PITR, what it leaves out, how Lovable Cloud backups work, and how to rehearse a restore before you need one.

Supabase RLS policy examples and mistakes

Supabase RLS policy examples for owner, team, public, admin and storage access, with a test for each and common mistakes that break or open your tables.

Scaling a Lovable app: what breaks first

Scaling a Lovable app: why the database breaks first, how to fix indexes, connections and slow functions, and how to load-test before a traffic spike.

How to test an AI-built app before launch

How to test a Lovable or AI-built app before launch: which journeys to test first, two-account access checks, payment failures, and tests on every change.

Lovable app to the App Store and Google Play

How to get a Lovable app into the App Store and Google Play: PWA, Capacitor, wrapper or rebuild, Apple's review rules, Google's testing step and costs.

Lovable OpenAI integration: keep your key safe

Add OpenAI to a Lovable app safely as of 2026: Lovable AI vs your own key, Secrets and edge functions, per-user limits, spend caps and prompt injection.

Lovable email with Resend: reach the inbox

Send email from a Lovable app with Resend that reaches the inbox: domain records, Supabase auth emails, the email verification error, retries and bounces.

Production readiness checklist for AI apps

Twenty-four checks to run before real users arrive — data, access, testing, recovery and support, in the order they matter.

Case studies

Comparisons and guides

Glossary

Audit log

An audit log is a permanent, append-only record of who did what in a system. What belongs in one, how it differs from app logs, and why buyers want it.

Authentication vs authorization

Authentication proves who a user is; authorization decides what they may do. The difference, with examples; why AI-built apps often get only the first right.

Background job

A background job is work an app does outside the user's request, like sending email, through a queue that can retry. What it is, and why live apps need them.

CI/CD

CI/CD builds and tests every change automatically, then releases it through a pipeline. What CI and CD each mean, and how to set it up for a Lovable app.

Code audit

A code audit is a structured review of a codebase for security holes, reliability risks and maintainability. What it covers, and when an AI-built app needs one.

Database index

A database index lets the database find rows without scanning the whole table. What an index does, and why apps without the right ones slow down as they grow.

End-to-end testing

End-to-end testing drives a real browser through a user's whole journey, such as sign-up to checkout. What E2E testing is, versus unit and integration tests.

Feature flag

A feature flag turns a feature on or off for some or all users without a new release. The four kinds, how they fail, and how to add one to a Lovable app.

Idempotency

Idempotency means running an operation twice has the same effect as once, so retries never charge or send twice. What it is, and how idempotency keys work.

Load testing

Load testing puts an app under realistic traffic to measure how it performs before users do. What it is, how it differs from stress testing, what to watch.

Lovable Cloud

Lovable Cloud is the backend built into Lovable: database, sign-in, storage and server functions on Supabase. What it covers, and what production still needs.

Model Context Protocol (MCP)

MCP, the Model Context Protocol, is an open standard connecting AI assistants to apps through tools. What it is, how it works, and why products are adding it.

Multi-factor authentication (MFA)

Multi-factor authentication asks for two or more kinds of proof at sign-in, such as a password and a one-time code. What MFA is, and how it differs from 2FA.

Multi-tenancy

Multi-tenancy means one app and database serve many customers, each walled off from the others. What it is, how isolation is enforced, and where it fails.

OAuth

OAuth 2.0 lets an app act on a user's account elsewhere, such as reading Gmail, without their password. What OAuth is, and how it relates to Google sign-in.

Observability

Observability is knowing what a live app is doing, and why, from its logs, metrics and traces. How it differs from monitoring, and how to add it to your app.

Penetration test

A penetration test is an authorized, simulated attack on your app by testers to find weaknesses that can be exploited. What it covers; when to get one.

Point-in-time recovery (PITR)

Point-in-time recovery restores a database to its exact state at a chosen moment, not just last night's backup. What PITR is, and how it relates to RPO and RTO.

Rate limiting

Rate limiting caps how many requests a user, key or IP address can make in a period. What it protects against, and why AI features need spending limits as well.

Refactoring

Refactoring restructures existing code without changing what it does, so the next change is cheaper. When to refactor an AI-built app rather than rebuild it.

Regression testing

Regression testing re-runs existing tests after every change to prove that what worked before still works. What it is, and why AI-built apps need it most.

Role-based access control (RBAC)

Role-based access control grants permissions to roles, like admin or viewer, and roles to people. What RBAC is, how it relates to least privilege, and pitfalls.

Row-level security (RLS)

Row-level security is a database rule that decides which rows each user may read or change, enforced by the database. Why AI-built apps need it on every table.

Schema migration

A schema migration is a versioned script that changes a database's structure, applied in order everywhere. What it is, and why AI-built apps need them.

Secrets management

Secrets management is how an app stores, limits, rotates and audits its API keys, passwords and tokens. What it covers, and the leaks it stops in AI-built apps.

Single sign-on (SSO)

Single sign-on lets people log in once with their company account. How SAML SSO works, what adding it involves, and whether a Lovable app can offer it.

Staging environment

A staging environment is a private copy of production where each release is checked before real users see it. What staging is, and how it differs from previews.

Supabase

Supabase is an open-source backend platform built on PostgreSQL, with sign-in, storage and APIs. What it gives an AI-built app, and what it leaves to you.

Supabase anon key vs service role key

The Supabase anon (publishable) key is safe in the browser; the service role (secret) key bypasses row-level security. Which is which, and where each belongs.

Vibe code cleanup

Vibe code cleanup is engineering work that makes AI-generated code safe and maintainable for real users. What it covers, and how it differs from a rewrite.

Webhook

A webhook is an HTTP request one service sends your app when an event happens, such as a payment succeeding. How webhooks work, and how they fail in production.