Atlas E74243keac

Emergent Help

This guide walks you through connecting your custom domain to your Emergent deployment. The process involves adding DNS records to verify domain ownership and direct traffic to your application.

Access to your domain's DNS management panel

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

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

 34.57.15.54 (IP address provided by Emergent)

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

After adding the DNS record, return to Emergent

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

You can visit your application using your custom domain

The domain will automatically point to your live deployment

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

 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

Ensure TTL is set to 300 seconds or lower

Use DNS lookup tools to verify the record exists

SSL certificates are automatically provisioned

Allow 5–10 minutes after verification for SSL setup

Verify the A record is correctly configured

Ensure the domain is verified in Emergent

Try accessing via incognito/private browsing mode

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

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

Type: A
Host: staging
Value: 34.57.15.54

Type: A
Host: prod
Value: 34.57.15.54

 Regularly check domain verification status

Verify all DNS records are correctly configured

Wait for DNS propagation (up to 24 hours)

 Custom domain setup typically takes 5–15 minutes after DNS propagation.

 Always ensure only one IP address points to your domain to avoid routing conflicts.

For any questions or assistance, feel free to email us at 

Deployments and Custom Domains

By the end of this guide, you'll understand the difference between your Preview Link and Deployed Link, when to use each one, and how to move from testing to launching your app successfully.

Your Preview Link is designed to save resources when not in use. After 

Your Preview Link will stop working after 30 minutes of inactivity

All your work and code remain perfectly safe

This is normal behavior for testing environments

 Deploy your application! Your Deployed Link never sleeps and stays accessible to users anytime.

🔧 Preview Link - Your Safe Testing Ground

Your Preview Link is like having a private workshop where you can build, break, and perfect your application without any consequences.

A temporary link to your app running in our secure sandbox

Updates automatically as you make changes

Only accessible to people you share the link with

Goes to sleep after 30 minutes of inactivity

 (wakes up automatically when you visit it)

Sharing with friends or teammates for feedback

🚀 Deployed Link - Your Live Application

Your Deployed Link is your app's permanent home on the internet where real users will interact with it.

A stable, public version of your application

Doesn't change unless you deploy new updates

 - never goes to sleep like Preview Links

When you're ready to launch to real users

For sharing your finished product publicly

Create your application using Emergent's agent

Share with trusted friends, teammates, or beta users

Collect feedback and make final adjustments

This link won't change and can handle real users

Share this link publicly or add to your marketing

Purchase your own domain (like myawesomeapp123.com)

Now users can visit your custom domain instead

If you have forked your chat or started a new chat in another way, and want to replace your original deployment with code from the new chat - 

Select Replace from the bottom of the modal that opens

Replace your existing deployment with the new chat. 

There is no extra charge for replacing an existing deployment!

Always test thoroughly with your Preview Link first

Deploy only when you're confident everything works

Don't make frequent deploys that might confuse users

Don't ignore testing just because you can "fix it later"

"Why does my Preview Link stop working after a while?"

Your Preview Link goes to sleep after 30 minutes of inactivity to save resources. If you need your app to be always available, deploy it to get a Deployed Link that never sleeps!

Deploy when you've tested everything with your Preview Link and you're confident it works well for users. There's no rush - take time to perfect it first.

Yes! You can make changes and deploy updates anytime. Your Deployed Link stays the same, but the app behind it gets updated.

"What if something breaks after I deploy?"

You can quickly fix the issue and redeploy. Meanwhile, you can share your Preview Link as a temporary solution if needed.

"How many people can use my Preview Link?"

Preview Links are designed for testing, not heavy traffic. For real users, always use your Deployed Link.

[ ] Design looks good on different screen sizes

Remember: Your Preview Link is for perfecting, your Deployed Link is for sharing. Take your time in the preview stage - your users will thank you for launching a polished product!

Understanding Preview v/s Deployed Links

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.

Check interactive elements like buttons and forms.

Ensure responsive design works across different screen sizes.

When encountering errors in your Emergent project preview:

 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.

 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.

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. 

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.

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.

The Deployment Manual

Deployments and Custom Domains

Understanding Preview v/s Deployed Links

Preview v/s Deployment