Skip to main content
Nometria supports apps built on every major vibe coding platform. Here’s what gets exported, how to connect, and any platform-specific notes.

Base44

Base44 apps require the Chrome Extension for export — Base44 does not offer native GitHub or ZIP export.
What gets migrated:
  • Full React + Vite frontend source
  • Database schema (tables, relationships, RLS policies) from your Base44 Supabase project
  • All environment variables detected in your project
  • Static assets and public files
Connection method: Chrome Extension Notes:
  • Base44 uses a managed Supabase instance. Nometria migrates your schema to your own Supabase project during setup.
  • If you’ve customized SQL beyond the Base44 editor, use the Advanced schema review option before deploying.

Lovable

What gets migrated:
  • React + Vite or Next.js source code
  • Supabase schema and data
  • Environment variables
  • All Supabase Edge Functions (if present)
Connection method: GitHub (recommended) or Chrome Extension Notes:
  • Lovable offers native GitHub sync — connect your Lovable project to GitHub first, then point Nometria at that repo for the cleanest setup.
  • Two-way sync works particularly well with Lovable since it already tracks changes in Git.

Bolt

What gets migrated:
  • React, Next.js, or Vite project source
  • Environment variables
  • Static assets
Connection method: Chrome Extension or ZIP upload Notes:
  • Bolt supports ZIP export from the project menu. Use Download Project → upload the ZIP to Nometria.
  • If your Bolt project uses a backend (Express, Fastify), Nometria detects and deploys it alongside the frontend on the same EC2 instance.

Manus

What gets migrated:
  • Frontend source (React, Vue, or plain HTML depending on what Manus generated)
  • Backend API code (Python FastAPI or Node.js)
  • Environment variables
Connection method: Chrome Extension Notes:
  • Manus generates full-stack projects. Nometria deploys both the frontend and backend together, with nginx proxying API routes.
  • Python backends are supported — Nometria installs dependencies from requirements.txt automatically.

Emergent

What gets migrated:
  • React frontend source
  • Backend services
  • Database schema
  • Environment variables
Connection method: Chrome Extension Notes:
  • Emergent apps are often full-stack. Review the detected stack on the configuration screen before deploying.

Replit

What gets migrated:
  • Any language or framework (Node.js, Python, Go, etc.)
  • replit.nix or Dockerfile for environment definition
  • Environment secrets (Replit Secrets → Nometria env vars)
Connection method: GitHub (recommended) or ZIP upload Notes:
  • Replit supports GitHub export natively. Connect your Replit project to GitHub, then use the GitHub connection in Nometria.
  • If your app uses Replit DB, you’ll need to migrate to Supabase or Appwrite. See the Firebase to Supabase guide for a similar migration pattern.
  • Always-on Repls → Nometria EC2 instances give you true always-on with no sleep penalties.

Any GitHub Repository

You can deploy any public or private GitHub repository — it doesn’t have to come from a vibe coding platform. Requirements:
  • A package.json with a build script (for Node/React apps) or a Dockerfile (for any stack)
  • Environment variables documented in a .env.example file (optional but recommended)
Connection method: GitHub

Connect via GitHub

Step-by-step guide to connecting any GitHub repository.