Project Import
Bring your existing project into BlueForge. We auto-detect your tech stack, scan for database configurations, and let you deploy with zero re-setup.
No lock-in. Import does not modify your existing code. A single project.json file is added to your folder. Your git history is fully preserved.
Quick Start
Download BlueForge
Available for macOS (Apple Silicon & Intel) and Windows.
Click "Import Project"
On the Home screen, click the Import Project card next to New Project.
Select Your Project Folder
Use the OS file picker to select any project directory on your machine.
Review Scan Results
BlueForge auto-detects your framework, language, package manager, and database.
Choose Database Option
Keep your existing database (Supabase, Firebase, etc.) or optionally switch to ForgeDB.
Start Building
BlueForge generates a Blueprint from your code. Use Build Studio for AI-assisted development.
Supported Tech Stacks
| Category | Detected | Status |
|---|---|---|
| Next.js | next in dependencies | Full |
| Vite | vite in devDependencies | Full |
| Create React App | react-scripts | Full |
| Vue / Nuxt | vue or nuxt | Full |
| SvelteKit | @sveltejs/kit | Full |
| Remix | @remix-run/react | Full |
| Express / Fastify | In dependencies | Full |
| TypeScript | tsconfig.json present | Full |
| npm / yarn / pnpm / bun | Lock file detection | Full |
Database Detection
BlueForge scans your package.json dependencies and .env files to identify your database setup.
| Provider | Detection | Auto-Convert to ForgeDB |
|---|---|---|
| Supabase | @supabase/supabase-js + env keys | Supported |
| Firebase | firebase package + env keys | Detect only (manual guide) |
| Prisma | @prisma/client + schema.prisma | Detect only |
| Drizzle | drizzle-orm + config file | Detect only |
ForgeDB Conversion (Optional)
If you choose to switch from Supabase to ForgeDB, BlueForge auto-converts your configuration. This is completely optional — you can always keep your existing database.
What changes in your code
SUPABASE_URL=https://xxx.supabase.co SUPABASE_ANON_KEY=eyJ... FORGEDB_URL=https://xxx.forgedb.cloud FORGEDB_ANON_KEY=eyJ...
What stays the same
@supabase/supabase-jslibrary is kept — ForgeDB is API-compatible- All
supabase.from(),supabase.auth,supabase.storagecalls work unchanged - RLS policies and database schema transfer as-is
Backup & Rollback
All original files are backed up to .blueforge-backup/ in your project directory. If anything goes wrong, you can restore from backup instantly.
Frequently Asked Questions
Will my git history be preserved?
Yes. BlueForge never touches your .git directory. Your entire commit history remains intact.
Can I switch back to Supabase after converting?
Yes. Original files are saved in .blueforge-backup/. Simply copy them back to restore your original configuration.
What if my project uses Firebase?
BlueForge detects Firebase and shows it in the scan results. Auto-conversion to ForgeDB is not yet available for Firebase, but your project will import and work normally.
Is ForgeDB conversion required?
No. ForgeDB conversion is completely optional. The default option is to keep your existing database. You can always switch later.
Does Import modify my project files?
Only a single project.json file is added (and optionally added to .gitignore). No existing files are modified unless you choose ForgeDB conversion.
What project types can I import?
Any Node.js/JavaScript/TypeScript project. As long as there's a package.json, BlueForge can import and work with it.