Emergent migration services by X & Company

Migrate off Emergent.Stop paying credits to stay online.

Emergent’s agents build a real React, FastAPI and MongoDB app. Keeping it live costs 50 credits a month per deployed app, and every AI feature runs through Emergent’s key. X & Company moves your code, data and AI calls to infrastructure you own.

Get a free migration assessment Read the migration guide
  • MongoDB data moved intact
  • Your own AI keys
  • Hosting you control
  • Fixed-scope quote
your-emergent-app50 credits / mo to stay live
  1. FrontendReactPushes to GitHub
  2. BackendPython · FastAPIPushes to GitHub
  3. DatabaseMongoDBOn Emergent hosting
  4. AI callsUniversal LLM keyBilled in credits

After migration: your repo, your MongoDB or Postgres, your OpenAI / Anthropic / Gemini keys, your server.

Emergent by the numbers

Half your Standard plan goes to keeping one app online.

The numbers come from Emergent’s pricing page and help center. Building on Emergent spends credits. So does keeping the result live, month after month.

100 creditsStandard plan, $20 / month
  • Hosting one deployed app: 50
  • Left for building: 50

Deploy a second app and the Standard plan’s credits are fully spent on hosting alone, before a single prompt.

$20

Standard plan, 100 credits a month

Roughly $0.20 per credit. Pro is $200 for 750 credits. Free gets 10.

src [1]

50

credits per month, per deployed app

Hosting isn’t a one-off. Every live app draws down your credits every month.

src [2]

3

layers in every web app

React on the front, Python FastAPI on the back, MongoDB underneath. All standard, all portable.

src [2]

1

shared key for GPT, Claude and Gemini

The universal LLM key bills AI usage through Emergent credits instead of your own provider accounts.

src [2]

7M+

apps built on Emergent

By more than six million builders in 190+ countries. A lot of them will outgrow the platform.

src [3]

Paid

plans needed for GitHub

GitHub integration is listed from the Standard plan up. It’s your main route for getting code out.

src [1]
  1. [1] Emergent pricing
  2. [2] Emergent Help Center FAQ
  3. [3] Business Wire: Emergent reaches $100M ARR in 8 months (Feb 2026)
  4. Checked September 2026. Confirm current plans on emergent.sh.

Why teams leave Emergent

Built by agents in an hour. Paid for every month after.

Emergent’s agents are genuinely good at getting a full-stack app running. Once customers depend on it, the credit meter, the shared AI key and the hosted database become business risks.

Rent that never ends

Every deployed app costs 50 credits a month to stay live. More apps, or more environments, means more credits, whether or not you change a line.

AI you don’t hold the key to

The universal LLM key is convenient, but AI usage is billed through Emergent credits. You can’t use your own provider discounts, limits or data agreements.

Your data sits on their cloud

Emergent hosts the MongoDB database behind your deployed app. Backups, retention, region and direct access are the platform’s decisions, not yours.

Every fix costs credits

Every agent action spends credits, and complex tasks spend more. Debugging a production issue by prompt can burn through a month’s plan in an afternoon.

Security reviews get harder

Enterprise buyers ask about SOC 2, data residency and VPCs. Self-hosted databases and VPC deployment sit in Emergent’s Enterprise tier.

Agent-written, human-maintained

The code is yours, but nobody on your team wrote it. A migration is the moment to get it reviewed, tested and documented properly.

What an Emergent migration involves

Your code is portable. Your runtime isn’t.

Good news first: Emergent writes a standard React, FastAPI and MongoDB app, and it can push the code to your GitHub. The migration work is the live data, the AI key, the secrets and the hosting.

In your GitHub

  • React frontend source, via Save to GitHub (Standard plan and up)
  • Python FastAPI backend source, in the same repository
  • requirements.txt and package.json, so dependencies rebuild cleanly
  • Mobile apps built with Expo (React Native), if you have one

Left on Emergent

  • Your live MongoDB data on Emergent’s cloud. It needs its own dump and restore
  • AI calls made through the universal LLM key and the credits behind them
  • Environment values like MONGO_URL and the Emergent LLM key
  • Hosting, SSL and the deployed URL. Custom domains need re-pointing
  • Agent history and context. Document what the agent knew before you leave
backend/server.py — the two lines every Emergent migration touches
- from emergentintegrations.llm.chat import LlmChat, UserMessage
+ from anthropic import Anthropic          # or openai, google-genai

- chat = LlmChat(api_key=os.environ["EMERGENT_LLM_KEY"], ...)
+ client = Anthropic(api_key=os.environ["ANTHROPIC_API_KEY"])   # your account, your limits

- client = AsyncIOMotorClient(os.environ["MONGO_URL"])   # Emergent-hosted
+ client = AsyncIOMotorClient(os.environ["MONGO_URL"])   # your Atlas cluster or server

The FastAPI app itself barely changes. What changes is who pays for the AI calls, where the database lives, and who holds every key.

The X & Company process

Four steps from Emergent to your own servers.

A calm, repeatable method, whether it’s a side project or a product with paying customers. You know the scope, the timeline and the cost before we start.

  1. Audit & review

    We pull your repo from GitHub, read what the agents wrote, and inventory every collection, endpoint, integration, env var and LLM call. Weak spots get flagged before anything moves.

    • Code review & risk list
    • Dependency inventory
    • Fixed-scope quote

  2. Harden & re-key

    We replace the universal LLM key with your own OpenAI, Anthropic or Gemini accounts, re-issue every secret, and add the tests and config a production app needs.

    • Your own AI keys
    • Secrets in your manager
    • Test suite & CI

  3. Move MongoDB

    We dump every collection, restore it to your MongoDB Atlas cluster or server, and verify document counts and indexes. If you’d rather be on Postgres, we plan that too.

    • Collection-by-collection counts
    • Indexes & backups
    • Files moved to your storage

  4. Deploy & cut over

    We deploy FastAPI and React to your server behind Nginx and SSL, run a final sync, switch your domain with a rollback plan, and hand over the repo, runbooks and every key.

    • Production deploy
    • Monitoring & alerts
    • Docs & handoff
Start with a free audit

Emergent vs. your stack

What changes when you get off Emergent

A fair comparison. Emergent is a strong place to start. Your own stack is where you go when control, cost predictability and security reviews start to matter more than build speed.

Staying on EmergentAfter migration
CodeSave to GitHub on paid plansYour repo, reviewed, tested and documented
Hosting cost50 credits per deployed app, every monthA server bill you can see and size
DatabaseMongoDB on Emergent’s cloudYour Atlas cluster or server, with your backups
AI callsUniversal key, billed in Emergent creditsYour OpenAI, Anthropic or Gemini accounts
ChangesAgent actions paid in creditsAny developer or AI tool, no meter
Enterprise needsVPC & self-hosted DB on Enterprise tierRegion, VPC and controls you choose
EnvironmentsPreview and deployed appLocal, staging and production with CI/CD
MonitoringPlatform-levelLogs, metrics and alerts you own

What you get

A finished migration, not a zip file.

X & Company delivers a working production system on infrastructure you own, and a team that understands how it works.

Talk to X & Company

Your full source code

A reviewed, tested repository in your GitHub organization, with no Emergent-only libraries left.

A production database

Your MongoDB collections on infrastructure you control, with indexes, backups and every document counted.

Your own AI keys

LLM calls moved to your own provider accounts, with usage limits and alerts you set.

Hardened hosting

Your server behind Nginx with Certbot SSL, firewalling and monitoring. AWS, a VPS or on-prem.

A deploy pipeline

Push to main and ship. Staging and production environments you can reason about.

Runbooks & handoff

Docs for deploys, backups, restores and on-call, plus a walkthrough with your team.

Readiness check

Is it time to get off Emergent?

Tick every statement that’s true for your app. It takes 20 seconds.

0/8signals

Check the statements that apply to you.

Your score updates as you go. Nothing is sent anywhere; it all runs in your browser.

Get an expert opinion

Credits calculator

What does staying on Emergent really cost?

Hosting uses 50 credits per deployed app each month. Add the credits you spend building, and see what’s left of your plan, and what you pay on top.

Standard works out to $0.20 a credit. Enter what you pay for top-ups.
Together they use 100 hosting credits a month (50 each).
New features, fixes and agent runs. Check your usage page for a real number.
A server for FastAPI and React plus a small MongoDB Atlas cluster. Add your own LLM spend on both sides.
Enter your quote from X & Company.
Credits needed each month250 / 100
Extra credits bought: 150 · Emergent per month: $50
Stay on Emergent
$1,200
Migrate + self-host
$960
$240saved over 24 months
immediatelyto break even
Get your real migration quote

Free Emergent migration guides

Prefer to do it yourself? Start here.

Everything we’ve learned about getting off Emergent, written up in plain language. If you decide you’d rather have it done for you, we’re one click away.

How to Migrate Off Emergent (Step-by-Step)

From Save to GitHub to switching DNS. Seven steps covering code, MongoDB, AI keys, secrets and hosting.

Read guide

Moving Your Emergent App's MongoDB Data

Collections, indexes, files and users. How to move your Emergent app's MongoDB data and prove every document arrived.

Read guide

Emergent Credits and Hosting Costs, Explained

What each plan includes, why every live app costs 50 credits a month, and how to tell when self-hosting wins.

Read guide

Done for you

Skip the guides. We’ll migrate it.

X & Company takes your Emergent app from audit to live on your own server, for a fixed-scope quote.

Get a free assessment →

Questions

Emergent migration FAQ

Can I export my code from Emergent?

Yes. On paid plans, Emergent’s GitHub integration saves your project to a repository you own. Web apps are a React frontend with a Python FastAPI backend and MongoDB; mobile apps use Expo (React Native). The code is standard, which makes Emergent one of the more portable AI builders.

Then what does a migration actually involve?

Everything that isn’t in the repo. Your live MongoDB data sits on Emergent’s cloud, AI features call models through Emergent’s universal LLM key, environment values and secrets stay behind, and the deployed app runs on Emergent hosting. A migration moves the data, swaps in your own AI provider keys, re-issues secrets, and redeploys on infrastructure you control.

How much does it cost to keep an app live on Emergent?

Emergent’s help center lists deployment at 50 credits per month for each deployed app. On the Standard plan ($20 for 100 credits) that is half the month’s credits for one app, before any building. On your own stack, a small server and database is a fixed monthly bill that doesn’t grow with each app you keep online.

What happens to AI features that use the Emergent LLM key?

We replace them with direct calls to your own OpenAI, Anthropic or Google Gemini accounts. It’s usually a small code change, and it gives you your own rate limits, usage alerts, provider discounts and data agreements, instead of paying for AI usage in Emergent credits.

How do you move the MongoDB data?

We export every collection, restore it to your MongoDB Atlas cluster or your own server, then check document counts and rebuild indexes. The final sync happens during a short write freeze just before cutover, so no documents are lost. If you’d rather move to PostgreSQL, we scope that as part of the audit.

Is agent-written code safe to run in production?

It can be, once someone has reviewed it. Our audit reads the code the agents produced, adds tests for the critical paths, and fixes things like hard-coded settings, missing validation and over-broad CORS before the app moves.

How long does an Emergent migration take?

Because the code is already standard, most of the work is data, keys and hosting. Scope depends on the number of collections, integrations, AI features and apps. You get a fixed timeline and quote after the audit.

Will there be downtime?

Very little. The new deployment runs alongside your Emergent app while we test it. At cutover there’s a brief write freeze for the final data sync, then your domain moves over with a rollback plan ready.

Is this site affiliated with Emergent?

No. This is an independent resource run by X & Company, a software studio that provides Emergent migration services. Emergent is a trademark of its owner.

Ready to migrate off Emergent?

Tell X & Company about your app. You’ll get a straight answer on scope, timeline and cost, and a plan to own your whole stack.

Get your free assessmentor email contactus@xandcompany.com