Everything you need to know about using HotSwap to manage, monitor, and swap your integrations.
Link your GitHub, GitLab, or Bitbucket repository. HotSwap scans your codebase to detect every third-party integration — databases, auth providers, payment processors, email services, and more.
Once scanned, you get a visual map of every external dependency in your project. Each node represents a service, showing which files reference it, what environment variables it uses, and how deeply it's integrated.
From the map, you can monitor health, swap integrations, or generate documentation — all without leaving HotSwap.
Select any integration on your map, click "Swap Integration," and choose a replacement provider. HotSwap's AI agents analyze every file that references the old service and rewrite them for the new one.
Source code (API calls, client initialization, queries), database schemas and migrations, environment variable references, configuration files, and tests. Every file is updated in a single, reviewable pull request.
Common swaps include Neon → Supabase, Stripe → Paddle, Clerk → Auth0, Resend → SendGrid, Vercel → Netlify, and many more. If both services have a public API, HotSwap can generate the migration.
Swaps are never auto-merged. HotSwap opens a pull request with a detailed diff, so your team can review every change before it hits production. Each file change includes inline comments explaining the reasoning.
Every integration receives a health grade (A through F) based on four signals: package freshness (last publish date), weekly download trends, known security vulnerabilities (CVEs), and API deprecation notices.
When a dependency drops below a configurable health threshold, HotSwap flags it in your dashboard with severity (critical, warning, info). You'll see exactly what's wrong — "3 CVEs found," "last updated 2 years ago," or "deprecated API in use."
For many issues, HotSwap can fix them automatically: updating to the latest stable version, patching vulnerable transitive dependencies, or migrating from deprecated API methods to their replacements. Fixes are opened as pull requests for review.
Health checks run on a schedule (daily by default). When new CVEs are published or a package you depend on becomes unmaintained, you'll know about it within 24 hours.
HotSwap detects integrations across all major categories: Databases (Neon, Supabase, PlanetScale, MongoDB, Turso), Authentication (Clerk, Auth0, NextAuth, Supabase Auth), Payments (Stripe, Paddle, LemonSqueezy), Email (Resend, SendGrid, Postmark), Analytics (PostHog, Mixpanel, Amplitude), Hosting (Vercel, Netlify, Railway), Storage (Cloudflare R2, AWS S3, Uploadthing), and AI (OpenAI, Anthropic, Replicate).
Integrations are detected by scanning package.json dependencies, import statements, environment variable patterns, and configuration files. No manual tagging required.
If you use an internal or niche service that HotSwap doesn't recognize, you can define it manually with a simple JSON config specifying the package name, file patterns, and environment variables.
HotSwap uses specialized AI agents for different tasks. The Scanner agent maps your codebase. The Swap agent rewrites code for a new provider. The Health agent evaluates dependency risk. The Docs agent generates integration documentation.
When performing a swap, agents don't just find-and-replace. They understand API semantics — translating Neon's serverless SQL to Supabase's client library, adapting authentication flows between providers, and restructuring data models when schemas differ.
All agent-generated changes are sandboxed. Nothing is committed directly to your branch. Every change goes through a PR with full diffs, and agents include test suggestions to verify the migration works correctly.
Install with npm install -g hotswap-cli. Run hotswap scan to detect integrations, hotswap health to check dependency health, and hotswap swap <from> <to> to initiate a migration from the command line.
Add HotSwap to your CI pipeline to block merges when dependency health drops below a threshold. The GitHub Action runs health checks on every PR and comments with a summary of any issues found.
All settings live in a hotswap.config.json file at your project root. Configure health thresholds, ignored dependencies, custom integration definitions, and notification preferences.
HotSwap Documentation