So you've made your first app on Emergent. The next step is to make it shareable with the world and show your stuff off! Emergent lets you deploy full-stack FastAPI + React + MongoDB apps without configuring servers.

You get:

• Automatic scaling

• Managed MongoDB

• Secure environment variables

• Preview & Production environments

• Custom domains

• One-click deployments

Pre-Deployment Checklist

Before you hit that deploy button, you need to ensure that it's ready to go. Here's the best practices to follow to ensure a smooth deployment:

1. Live Preview

For viewing your app as you build it and check the responsiveness, design, and interactivity.

To preview your application in real-time:

• Click the Preview button in the Emergent interface.

• A preview window will open showing your application's current state.

• Interact with your application to test functionality.

• The preview automatically updates when you make changes to your code.

Best Uses:

• Test user interfaces before deployment.

• Verify that components render correctly.

• Check interactive elements like buttons and forms.

• Ensure responsive design works across different screen sizes.

• Debug visual issues in real-time.

Getting an error in the preview

When encountering errors in your Emergent project preview:

1. Use the agent's debugging capabilities: Copy the complete error message text, Paste it in the chat with a request like: "Please solve this error" The agent will analyze the error and provide solutions.
   Alternatively, you should take a screenshot of the issue and upload that directly to the agent along with a description of the problem.

2. Why this works: The agent has deep knowledge of common development errors. By sharing the specific error, you enable precise troubleshooting This approach is faster than trying to describe the problem in general terms.

3. For persistent issues: If the agent cannot resolve the error, try providing additional context. Include information about when the error occurs and any relevant code sections.

Most preview errors can be resolved directly with the agent's assistance, as it has comprehensive understanding of web development issues. 

2. Pre-Deployment Health Check

This is a handy feature where Emergent's Agent checks the readiness of your app for deployment, flagging any concerns before you commit to the deployment.

Deployment

To deploy your application to the web:

• First, use the Preview button to test your application and ensure it works correctly.

• Once you're satisfied with the preview, click the Deploy button in the Emergent interface.

• Click "Deploy Now" to publish your application.

• Wait for the deployment process to complete (typically 15 minutes).

• Once finished, you'll receive a URL where your application is live.

• After deployment, you can configure environment variables and custom domain settings if needed.

• Share this URL to allow others to access your application.

Important Notes:

• Always preview your application before deploying.

• Deployment creates a publicly accessible URL for your application.

• The deployment process typically takes 15 minutes.

• You can redeploy at any time to update your live application.

• Environment variables and domain settings can be configured after deployment.

• Deployment costs 50 credits per month per deployed app.

• Creates a production-ready environment with managed infrastructure that stays live 24/7.

• You can securely manage secrets and environment variables.

• Custom domains can be added, you just need to configure the A record with your DNS server and add Emergent IP listed in the Custom Domain Flow.

• You can relace your existing deployments with a new deployments without any additional charges, this will help you iterate on complex applications spanning across jobs.

• View all deployed apps from the Home tab.

• Apps can be rolled back to a stable version at no additional cost.

• You can shut down any deployed app anytime to stop recurring charges.

Adding a Custom Domain

Once deployed, you might want your creation to have a unique face for the internet. The process involves adding DNS records to verify domain ownership and direct traffic to your application.

Note: Custom domain works for web apps - mobile apps do not have a domain attached to them.

Prerequisites

• An active Emergent deployment

• Access to your domain's DNS management panel

• Your domain registrar login credentials (GoDaddy, Namecheap, Cloudflare, etc.)

Step-by-Step Process

Step 1: Initiate Custom Domain Setup

1. Navigate to your Deployments section in Emergent

2. Find the Custom Domain section

3. Click "Link Domain" button

4. Enter your domain name (e.g., emergent1.feelingcoding.xyz)

5. Click "Next"

Step 2: Configure DNS Records

After entering your domain, Emergent will provide you with DNS configuration details:

Required DNS Record:

• Type: A Record

• Host/Name: emergent1 (or your chosen subdomain)

• Value/Points to: 34.57.15.54 (IP address provided by Emergent)

• TTL: 300 seconds (or leave as default)

Step 3: Add DNS Records to Your Provider

For Popular DNS Providers:

Cloudflare:

1. Log into Cloudflare dashboard

2. Select your domain

3. Go to DNS → Records

4. Click "Add record"

5. Select "A" as type

6. Enter subdomain name (e.g., "emergent1")

7. Enter the IP address: 34.57.15.54

8. Set Proxy status to "DNS only" (gray cloud)

9. Click "Save"

GoDaddy:

1. Log into GoDaddy account

2. Go to My Products → DNS

3. Find your domain and click "Manage"

4. Click "Add" in the Records section

5. Select "A" record type

6. Enter Host (subdomain name)

7. Enter the IP address

8. Click "Save"

Namecheap:

1. Log into Namecheap account

2. Go to Domain List

3. Click "Manage" next to your domain

4. Go to Advanced DNS tab

5. Click "Add New Record"

6. Select "A Record"

7. Enter Host and IP address

8. Click the checkmark to save

Step 4: Verify Domain Ownership

1. After adding the DNS record, return to Emergent

2. Click "Check Status" button

3. Wait for verification (5–15 minutes)

4. Once verified, you'll see a green "Verified" status

Step 5: Complete Setup

• Your custom domain is now active

• You can visit your application using your custom domain

• The domain will automatically point to your live deployment

Important Notes

DNS Propagation

• DNS changes typically take 5–15 minutes to propagate

• In some cases, global propagation may take up to 24 hours

• Use online DNS checker tools to verify propagation status

Critical Requirements

⚠️ Important: Ensure only ONE A record points to your domain

• Do not add multiple IP addresses for the same subdomain

• Remove any conflicting DNS records before adding the Emergent record

• Multiple A records can cause routing issues

Troubleshooting

Domain Not Verifying:

• Double-check the DNS record values

• Ensure TTL is set to 300 seconds or lower

• Wait 15–30 minutes and try again

• Use DNS lookup tools to verify the record exists

SSL Certificate Issues:

• SSL certificates are automatically provisioned

• Allow 5–10 minutes after verification for SSL setup

• If issues persist, contact support

Domain Not Loading:

• Verify the A record is correctly configured

• Check that no other A records conflict

• Ensure the domain is verified in Emergent

• Try accessing via incognito/private browsing mode

DNS Configuration Examples

Example 1: Subdomain Setup

Type: A
Host: app
Value: 34.57.15.54
Result: app.yourdomain.com → Your Emergent App

Example 2: Root Domain Setup

Type: A
Host: @ (or leave empty)
Value: 34.57.15.54
Result: yourdomain.com → Your Emergent App

Example 3: Multiple Subdomains

Type: A
Host: staging
Value: 34.57.15.54

Type: A
Host: prod
Value: 34.57.15.54

Support

If you encounter issues during setup:

1. Verify all DNS records are correctly configured

2. Wait for DNS propagation (up to 24 hours)

3. Check our troubleshooting section above

4. Contact Emergent support (support@emergent.sh) with:

• Your domain name

• Screenshots of DNS configuration

• Error messages (if any)