Deploy anything in minutes

How to register a domain

1. 1.Go to Dashboard → DNS → Register Domain.
2. 2.Search for your desired domain name — available TLDs and prices are shown instantly.
3. 3.Click "Register" and complete the checkout via Stripe.
4. 4.Your domain is provisioned automatically with DeploysApp nameservers.
5. 5.Connect it to any service from the Domains tab, or manage DNS records manually.

Domain pricing

Prices are per year and include auto-renewal. TLDs not listed above are available at $25/yr. Domain transfers from other registrars are also supported.

Using your own domain (registered elsewhere)

• You don't need to register your domain with us. Any domain from any registrar works.
• Point your domain's nameservers to DeploysApp for full DNS management, or add a CNAME record pointing to your service URL.
• SSL/TLS certificates are provisioned automatically via Let's Encrypt for all connected domains.
• Both apex domains (yourdomain.com) and subdomains (app.yourdomain.com) are supported.

Supported record types

Setting up DNS for a DeploysApp-registered domain

1. 1.Domains registered through DeploysApp automatically use our nameservers — no manual setup needed.
2. 2.Go to Dashboard → DNS and select your domain.
3. 3.Add, edit, or delete records. Changes propagate within seconds.
4. 4.To connect a domain to a service, add it in the service’s Domains tab — the required DNS records are created automatically.

Using DeploysApp nameservers with external domains

• If you registered your domain elsewhere, you can point its nameservers to DeploysApp for full DNS management.
• Set your domain's nameservers to ns1.deploysapp.com and ns2.deploysapp.com at your registrar.
• Once nameservers propagate (usually 1-24 hours), you can manage all DNS records from the DeploysApp dashboard.
• Alternatively, keep your current nameservers and just add a CNAME record pointing to your DeploysApp service URL.

Getting started with email

1. 1.Choose an email plan from Dashboard → Billing → Email Plan.
2. 2.Go to Dashboard → Email and add your domain (must be verified or registered through DeploysApp).
3. 3.Create mailboxes — e.g. [email protected], [email protected].
4. 4.DNS records (MX, SPF, DKIM) are configured automatically for DeploysApp-managed domains.
5. 5.Access your inbox via the built-in Webmail, or configure any IMAP/SMTP email client.

Email client settings

Use these settings to connect your mailbox in Outlook, Thunderbird, Apple Mail, Gmail, or any IMAP/SMTP client:

Storage add-ons

Need more storage? Add extra capacity to your email plan at any time:

Email features

• Spam filtering with SpamAssassin — automatically scores and filters incoming mail.
• DKIM signing — outgoing emails are cryptographically signed for better deliverability.
• DMARC support — configure a DMARC policy to protect against email spoofing.
• Webmail access — read and send email from your browser, no client setup needed.
• Quota management — set per-mailbox storage limits from the dashboard.

Deploy Hook

Each service can have a unique deploy hook URL. Send a POST request to trigger a new build and deployment.

{
  "branch": "main",
  "commit": "abc1234...",
  "noCache": false
}

GitHub Actions example

# .github/workflows/deploy.yml
name: Deploy to DeploysApp
on:
  push:
    branches: [main]
jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - name: Trigger deploy
        run: |
          curl -X POST \
            https://api.deploysapp.com/webhooks/deploy/${{ secrets.DEPLOY_HOOK_TOKEN }}

Where to find your deploy hook

• Go to your service page
• Click the "Settings" tab
• Find "Deploy Hook" in the configuration section
• Click "Generate" to create a new hook token
• Copy the URL and use it in your CI/CD pipeline

Priority order

When the same key exists at multiple levels, the most specific value wins:

Import from .env file

You can bulk-import environment variables from a .env file:

• Go to your project's "Secrets" tab
• Click "Import .env" and paste your file contents
• Each KEY=value line becomes a secret
• Link secrets to services by adding a "Secret ref"

From Render

1. 1.Create a project in DeploysApp and add a Web Service
2. 2.Connect the same GitHub repo and branch
3. 3.Copy your build command, start command, and internal port from Render
4. 4.Copy environment variables from Render → DeploysApp env vars
5. 5.If you use a Render PostgreSQL, create a PostgreSQL service in the same project
6. 6.Update your DATABASE_URL to use the new service name as hostname
7. 7.Deploy and verify — then update your DNS to point to DeploysApp

From Heroku

1. 1.If using a Procfile, your "web" process maps to a Web Service start command
2. 2.Heroku buildpacks translate to build commands (e.g. npm install && npm run build)
3. 3.Export Heroku config vars: heroku config -s > .env
4. 4.Import the .env file into DeploysApp secrets
5. 5.Heroku add-ons need to be replaced with DeploysApp services (PostgreSQL, Redis) or external providers
6. 6.Deploy and test before cutting over DNS

From Vercel

1. 1.For Next.js apps, create a Web Service with build command: npm install && npm run build
2. 2.Set the start command to: npm start (or next start)
3. 3.Copy environment variables from Vercel project settings
4. 4.If using Vercel serverless functions, refactor to a standard Node.js server
5. 5.Static sites: use a Static Site service type with your build output directory
6. 6.Deploy and verify before updating your domain DNS

From Railway

1. 1.Railway services map directly to DeploysApp Web Services
2. 2.Copy your start command and environment variables
3. 3.Railway volumes → DeploysApp persistent volumes (configure mount path)
4. 4.Railway PostgreSQL/Redis → create equivalent database services in your project
5. 5.Internal service communication uses service names as hostnames (same concept as Railway)