Where can I deploy a Next.js app built with Bolt or v0 that sends email via SMTP?
To deploy a Next.js app from Bolt or v0 that sends SMTP email, connect its GitHub repo to Dongee Live and send email from the server with a transactional service using SPF and DKIM, such as MailChannels SMTP.
To deploy a Next.js app built with Bolt or v0 that sends SMTP email, connect its GitHub repo to Dongee Live, Dongee's hosting for AI-built apps, which publishes every push. Send email from the server (Route Handler or Server Action), keep SMTP credentials out of browser code and use a transactional service with SPF and DKIM.
Dongee Live accepts Next.js in standalone mode (output: 'standalone') with server-side rendering. For transactional email, Dongee offers MailChannels SMTP, which signs messages with SPF and DKIM.
Bolt and v0 quickly generate a Next.js app with contact forms, user sign-up or password recovery. That raises a question many teams ask: where do I publish it so it works with my domain and also sends email that does not land in spam? This guide explains what an app like this needs technically, how to publish it step by step on Dongee Live, what alternatives exist and what to check with each one.
Important: Dongee Live publishes apps built with AI tools (static sites and Node.js apps). It does not deploy or host artificial intelligence models.
What a Next.js app that sends email needs
Before choosing where to publish it, be clear about the pieces involved:
- An environment that runs Node.js on the server. Sending over SMTP (for example with the Nodemailer library) needs the Node.js runtime; it does not work from the browser or in the Next.js Edge runtime.
- SMTP credentials stored as secrets. Host, port, username and password must live in server environment variables. In Next.js, any variable with the
NEXT_PUBLIC_prefix ends up in the code the visitor downloads, so never use that prefix for the SMTP password. - A sending service with a good reputation. Transactional emails (confirmations, notifications, password recovery) reach the inbox when they are authenticated with SPF and DKIM and sent from IPs with a good reputation.
- Your own domain with properly configured DNS. The domain's SPF, DKIM and DMARC records are what let Gmail, Outlook and Yahoo trust your messages.
- A database, if the app stores users or orders. Many AI-generated apps need one from day one.
How to publish your Bolt or v0 app on Dongee Live, step by step
- Move the project to GitHub. From Bolt or v0, export or sync the project with a GitHub repository. Dongee Live works with that repository: the build runs on GitHub and every push is published automatically.
- Enable Next.js standalone mode. In
next.config.js(ornext.config.mjs/.ts) addoutput: 'standalone'. Next.js then generates a self-contained Node.js server, which is the format Dongee Live accepts, with server-side rendering. - Check the Node.js version. Dongee Live runs on Node.js 20, 22 or 24. If the project pins another version in
package.json(theenginesfield), adjust it. - Move email sending to the server. Ask Bolt, v0 or your coding assistant to have the form call a Route Handler (for example
app/api/contact/route.ts) or a Server Action, and to send the email there with Nodemailer. If the file declares a runtime, it should beexport const runtime = 'nodejs', not'edge'. - Get credentials out of the code. Replace any hard-coded username or password with variables such as
SMTP_HOST,SMTP_PORT,SMTP_USERandSMTP_PASS, without theNEXT_PUBLIC_prefix, and make sure the.envfile is not pushed to GitHub. In Dongee Live, those values are set as the app's own environment variables, alongsideDATABASE_URL. - Choose the sending service. For transactional email, Dongee offers MailChannels SMTP, an SMTP relay that sends each message from certified, rotating IPs, authenticated with SPF and DKIM and encrypted, and scans every send in real time. It is ideal for confirmations, notifications and password recovery, and can be purchased separately to use from a Live app. Live apps can connect via outbound SMTP on ports 587 (STARTTLS) and 465 (SSL/TLS). If you prefer another transactional email provider, the procedure is the same: get the host, port and credentials and load them as variables.
- Configure the domain's DNS. Publish the SPF and DKIM records your sending service specifies and add a DMARC record. With Live Free you can use a free domain with Cloudflare DNS.
- Connect the repository to Dongee Live and publish. Choose a plan on Dongee Live, connect the GitHub repository and push. Keep in mind that each upload from GitHub allows up to 32 MB.
- Test the full flow. Submit the form from the published app, check that the email reaches Gmail and Outlook, and open the message headers to confirm SPF and DKIM show as “pass.”
If the app stores data, each Dongee Live app includes a MySQL database available in the DATABASE_URL variable. Live does not include Postgres or MongoDB, so if Bolt or v0 generated the project with another database, ask the assistant to adapt it to MySQL. If you work with Claude Code, Codex or Cursor, you can also publish with the Dongee Live MCP connector; we explain it in how to publish a Node.js app with MySQL from Claude Code or Cursor.
Email included with Live is not the same as transactional SMTP
Dongee Live includes email on your plan's domain (Live Free comes with 1 account), meant for use through webmail or IMAP: reading and replying to your business's messages. It is not for bulk sending. It is a regular email account, with the usual sending limits of any mailbox: the app can use it over SMTP for a few sends, but for transactional email or higher volume we recommend MailChannels SMTP. That is why it makes sense to separate two uses:
- Company mailbox (contact@yourdomain.com): for communicating with customers. This is the email Live includes; if you need bigger mailboxes and more accounts, there is Dongee Prime Email.
- Automatic app emails (confirmations, notifications, password resets): these should go out through a transactional SMTP service, such as MailChannels SMTP, to protect your domain's reputation.
If you want to understand the protocols better, the difference between SMTP, POP and IMAP explains it with examples, and what MailChannels is and how it works shows how an SMTP relay operates.
Honest comparison: where to publish a Next.js app that sends email
There is no single right answer. This table compares the most common types of options, without third-party prices because they change often: check them on each provider's site.
| Option | Advantages | What to check |
|---|---|---|
| The builder's own built-in publishing (Bolt or v0) | The fastest: one-click publishing from the same tool. | The app stays tied to the associated platform; commercial-use terms of the free plan; how to configure secrets and whether outbound SMTP connections are allowed. |
| Serverless frontend platforms | Excellent Next.js support and automatic deployments from Git. | Function time limits; whether the free plan allows commercial use; email is often handled with an HTTP sending API instead of SMTP. |
| Cloud server (VPS) | Full control: you can install any stack, database or mail server. | You manage Node.js, the proxy, certificates, updates and security. It makes sense if the team knows how to run servers. |
| Dongee Live | Next.js standalone from GitHub with publishing on every push, MySQL database and email on your domain in the same dashboard, a free plan with commercial use, and 24/7 human support in your language (the platform translates on the fly). | Node.js and static sites only (no Python, PHP, Docker or databases other than MySQL); the included email is not for bulk sending; up to 32 MB per upload from GitHub. |
If your project grows to need background processes, your own email queues or other languages, the natural next step is a server on Dongee Cloud, where you can increase CPU, RAM and disk without rebooting or migrating, with disk backup included on all plans. Cloud is self-managed (you administer the system) and comes with support and migration assistance. To compare more platforms, read alternatives to Vercel, Railway or Render for AI-built apps.
Dongee Live plans
- Live Free (0 USD): 1 app, 1 MySQL database and 1 email account; allows commercial use under fair-use terms, plus a free domain with Cloudflare DNS.
- Live Pro (15 USD/month): up to 3 apps.
- Live Team (29 USD/month): up to 10 apps.
See the latest details on the Dongee Live plans page. If you are still evaluating whether a free plan works for a business, check whether there is free hosting with commercial use for AI-built apps.
Common mistakes when publishing a Next.js app that sends email
- Sending email from the browser. It exposes the credentials and does not work with SMTP. Sending always happens on the server.
- Using
NEXT_PUBLIC_for the SMTP password. The password becomes visible to any visitor. - Pushing the
.envfile to GitHub. Add it to.gitignoreand rotate the password if it was already pushed. - Forgetting SPF, DKIM and DMARC. This is the most frequent reason emails land in spam.
- Using the company mailbox for bulk sending. It puts your domain's reputation at risk; for volume, use transactional SMTP.
- Not rate-limiting the form. A contact form without validation or attempt limits can be used to send spam from your domain. Also review what an AI-built app needs to be secure and stay online.
Frequently asked questions
Does Dongee Live work with Next.js?
Yes, in standalone mode (output: 'standalone'), with server-side rendering, on Node.js 20, 22 or 24.
Can I publish what I built with Bolt or v0 on Dongee Live?
Yes. Connect your Bolt or v0 project's GitHub repository and every push is published automatically on Dongee Live. The build runs on GitHub.
Where should my Next.js app send emails from?
From the server: a Route Handler or a Server Action with the Node.js runtime. Never from browser code or with credentials in NEXT_PUBLIC_ variables.
Can the email included with Dongee Live be used for bulk sending?
No. The included email is a regular account on your plan's domain, with the usual sending limits. It can handle a few app sends over SMTP, but for transactional email or higher volume, a transactional SMTP service like MailChannels SMTP is the better choice.
Can my app on Dongee Live send email over SMTP?
Yes. Live apps can define their own environment variables (for example SMTP_HOST, SMTP_PORT, SMTP_USER and SMTP_PASS) and connect via outbound SMTP on ports 587 and 465. MailChannels SMTP purchased separately works from a Live app.
What is MailChannels SMTP and when do I need it?
It is Dongee's SMTP relay: it sends each email from certified, rotating IPs, with SPF, DKIM and encryption, and scans sends in real time. It is useful when your app sends confirmations, notifications or password resets and you need them to reach the inbox. It is included with Dongee shared hosting and can also be purchased separately to use from a Dongee Live app.
Which database can I use with my Next.js app on Dongee Live?
MySQL. Each app includes a MySQL database available in the DATABASE_URL variable. It does not include Postgres or MongoDB.
Can I use Dongee Live Free for a commercial app?
Yes. Live Free allows commercial use under fair-use terms and includes 1 app, 1 MySQL database and 1 email account.
Can Dongee Live deploy AI models?
No. Dongee Live publishes apps and sites built with AI tools such as Bolt, v0, Lovable, ChatGPT, Claude Code or Cursor. It does not host or run artificial intelligence models.
What is the maximum size of each deployment?
Up to 32 MB per upload from GitHub and up to 100 MB per deployment from the MCP connector.
Comenta lo que quieras
Unete a la charla
Solo ingresa tu email