Skip to content
Web Hosting

Startup Website Hosting Setup: Domain, VPS, Website and Email

In this article9 sections

A startup website does not need a complicated infrastructure diagram on day one. It does need a domain the business controls, a VPS that fits the website and app, secure access, working backups, and email on the same domain. This guide gives you a practical launch path for WordPress or a Node.js frontend, then tells you which Siteharbour VPS plan is the sensible first purchase.

Short answer: choose VPS-1 for a single, light website or a small Node.js app. Choose VPS-2 if WordPress and Node.js share one server, your Node app also runs a database or workers, or the site is a production service. Start with VPS-1 or choose VPS-2 for a production app. Add a domain name; Zoho Mail is a separate email service. Zoho’s free custom-domain option is limited to select data centers and offers up to five users, one domain, and 5 GB per user with web access. Confirm eligibility and terms in Zoho’s current setup guide.

Choose the website stack before the server

Use WordPress when the team wants an established content editor, plugins, and a site that marketing can update without deploying application code for every page. A company site, resource library, and many small business websites fit this model. You can use a managed WordPress service or run WordPress on a VPS when you need more control over the server.

A Node.js frontend is a better fit when the site is built around a JavaScript framework, custom application behavior, or a separate API. Before choosing it, confirm how the app is built, how environment variables are managed, what Node version it requires, and whether it serves pages as a long-running process or generates static files. A Node app on a VPS needs a process manager, a reverse proxy, HTTPS, deployment steps, and monitoring.

Keep the first release focused. Avoid selecting a complex stack solely because it is fashionable. The team should be able to update the site, recover it, and understand who owns production incidents. If a simple WordPress content site meets the requirement, a VPS still gives you room for custom PHP settings, staging, and services beside WordPress—but it also means your team owns server maintenance after handover. If you already have a Node app, Siteharbour’s Node.js VPS hosting includes Node, PM2, NGINX and HTTPS at setup.

Register and protect the domain

Choose a short domain that is easy to say, spell, and type. Check that the name does not create a trademark or brand conflict, and register it in the company’s name using an account the business controls. Keep the registrar login, recovery email, and payment method current. Turn on multi-factor authentication and domain auto-renewal, and record who can access DNS.

Registering the domain and hosting the website are separate decisions. You can keep the domain at one registrar and point it to hosting with DNS records. Siteharbour offers domain registration; after registration, DNS can direct the website to the VPS while mail records route messages to Zoho. Avoid changing name servers casually, since that can affect both web and email delivery.

Choose the right VPS plan for your startup

Size the server for the services you will run together, not the startup’s employee count. CPU handles concurrent requests and app processes; RAM must cover the operating system, web server, PHP or Node, database, Redis, and monitoring. A build can also use a temporary memory spike. The plan below is a concrete starting point based on Siteharbour’s current VPS lineup.

Your launch setup Plan to start with Why Order
One company site or lean WordPress site VPS-1 · 2 vCores · 4 GB RAM · 40 GB NVMe Fits a single, light website when traffic is modest and no heavy jobs or second database compete for memory. Choose VPS-1
Small Node.js frontend, bot, webhook receiver, or API VPS-1 · 2 vCores · 4 GB RAM · 40 GB NVMe A few app processes and NGINX fit; keep the database external or lightweight while usage is low. Choose VPS-1
Production Node.js app with a database, or WordPress plus Node.js VPS-2 · 4 vCores · 8 GB RAM · 75 GB NVMe More room for the frontend, database, workers, builds, and normal traffic to share a server. Choose VPS-2
Several production apps, real-time traffic, or heavy background jobs VPS-3 · 6 vCores · 12 GB RAM · 100 GB NVMe Use when measurements show VPS-2 is constrained, or when WebSockets, workers and the database need more headroom together. Choose VPS-3

Default pick: VPS-1 is the lean launch choice for one light site. If you plan to run WordPress and a server-rendered Node app together, choose VPS-2 so a build or worker does not compete with the live website for the same small memory pool. The plans can be upgraded in place as traffic and workload grow. Check current pricing, data-centre traffic allowance, and taxes on the Siteharbour VPS plans page or in checkout.

One important ownership point: the VPS page includes a free one-time stack installation and hardening, followed by handover with root access. It is unmanaged after that. Your team or developer remains responsible for deploying app code, applying routine application updates, monitoring, and responding to incidents. If no one can own those tasks, ask Siteharbour about support before ordering or choose managed WordPress for a WordPress-only site.

Launch WordPress on the VPS

Install a supported operating system and maintained web stack, configure a database and PHP runtime, and point the web server only at WordPress’s public document root. Create a separate database user with the permissions the site needs. Enable HTTPS before collecting logins or customer information. Set strong administrator credentials, add multi-factor authentication, remove unused themes and plugins, and apply security updates.

Set up backups that include both the database and uploaded media. Keep a copy outside the VPS and test a restore. Decide how updates will be checked and applied, especially for plugins that affect forms, payments, or membership. Configure caching carefully: public pages can often be cached, but logged-in and personalized pages need appropriate exclusions. Monitor disk space, PHP errors, and the availability of the website.

Deploy a Node.js frontend on a VPS

For a Node application, install the version required by the project, build from a version-controlled release, and store secrets as server environment values rather than in the repository. Run the application under a restricted service account and use a process manager such as systemd to start it on boot and restart it if it exits. Put a maintained web server such as NGINX in front of the app to terminate HTTPS and proxy requests to the local application port.

Keep the Node port private to the server where possible. Open only the network ports the public needs, commonly HTTP and HTTPS, and protect SSH access. Document how to deploy a new release, roll back, and rebuild assets. If the frontend is static, consider whether it needs a continuously running Node process at all. Keep application and operating system updates on a schedule, and watch service health, logs, memory, and disk usage.

Connect the domain and enable HTTPS

After the website is ready on the server, create the required DNS records at the authoritative DNS provider. An A record commonly points the root domain to the VPS IPv4 address; an AAAA record should be added only if IPv6 is configured and working. A CNAME can point www to the root domain or to the target recommended by the hosting setup. DNS changes take time to appear across networks, so verify the result from more than one resolver and keep a rollback note.

Issue and renew a TLS certificate, then redirect HTTP to HTTPS. Check both the root and www hostname, canonical redirects, and mixed-content warnings. For setup help, see the guide on pointing a domain to hosting with DNS. Add uptime monitoring and test the site from a mobile connection before announcing the launch.

Set up custom-domain email with Zoho Mail

A branded address such as [email protected] looks more consistent in customer conversations than a personal mailbox. Zoho’s custom-domain setup starts by adding and verifying your domain, creating users, then publishing the mail records Zoho provides. Its current page describes a free plan for small teams of up to five users, one custom domain, and 5 GB per user; availability is limited to select data centers. Confirm eligibility in your Zoho account because plan terms and regional availability can change.

  1. Add and verify the domain. Zoho gives you a verification value to publish in DNS. Keep existing mail routing in place until verification and migration are complete.
  2. Create mailboxes and groups. Set up the addresses the team actually needs, such as named users and a shared role address. A group address may be preferable to sharing one person’s password.
  3. Update MX records. Replace existing inbound mail records with the exact MX values shown in the Zoho admin console. Do this only when ready to receive mail there.
  4. Authenticate outbound messages. Add Zoho’s SPF and DKIM records and publish a DMARC policy appropriate for the domain. Follow Zoho’s current DNS values rather than copying old examples from a blog.
  5. Test delivery. Send to and from external providers, check spam placement, verify replies and aliases, and monitor DMARC reports as you tighten policy.

Zoho’s free plan is web-only according to its plan information, so confirm whether IMAP or desktop/mobile mail-client access is required before relying on it. The one-domain and five-user limits may be fine for a very small team but can become restrictive as hiring begins. Budget for a paid mail tier if the team needs additional users, protocol access, more storage, or other paid features. Website hosting and Zoho email are separate services, so a change to website hosting should not remove the mail records.

Protect the startup’s first production setup

Use separate logins for the domain registrar, VPS, website admin, and email administrator. Give each teammate only the access they need. Store recovery codes securely and keep a short handover document with the domain renewal date, DNS provider, server access owner, backup location, and deploy steps. This simple inventory prevents a founder’s departure or lost laptop from locking the company out of its own website.

Before launch, test the signup or contact form, email delivery, mobile layout, HTTPS, 404 page, backup restore, and one deployment rollback. Add basic analytics and Search Console after launch, verify the sitemap and canonical domain, and make sure important pages are indexable. Keep the homepage clear about what the startup offers and give each service a direct next step.

A practical launch checklist

  • Business-controlled domain with auto-renewal and multi-factor authentication.
  • WordPress or Node.js stack selected for the team’s skills and website needs.
  • VPS capacity and ongoing maintenance responsibility understood.
  • HTTPS, restricted access, application updates, and tested off-server backups in place.
  • DNS records checked for both website and Zoho Mail; SPF, DKIM, and DMARC configured.
  • Forms, email, redirects, mobile pages, monitoring, and rollback tested before promotion.

Ready to launch? For one light website or a small Node app, order VPS-1. For a production Node app, a local database, or WordPress and Node together, order VPS-2. Then register your domain and follow the Node.js VPS setup details or WordPress hosting options. Confirm the current price and regional terms before checkout; keep the domain, server, and email administrator accounts under company ownership.

Share this guide