[MORSALIN]
Service 7.3Updated September 2026

Production Server Setup for Your Web App (VPS or Cloud VM)

I set up a secure production server for your app on the provider you choose: firewall, SSH keys, TLS, reverse proxy, database, workers, backups and basic monitoring, with a runbook. From $390 ($300 founding) for one server, about a week. Single server or app/database split. Email your app and provider to start.

See a sample report, proposal and weekly update
Price
from $390
Founding
from $300
Timeline
~1 week
Format
Fixed scope, fixed price
Hours
US Eastern Time, async
01Fit

Who this is for.

A good fit if

  • Apps ready to leave a shared host, a PaaS or a developer’s laptop
  • Founders who want a server they own, on their own cloud account
  • Agencies who need a clean production box for a client build

Common triggers

  • Launch is coming and there’s no production server yet
  • The current server was set up by hand years ago and nobody knows how
  • PaaS or cloud bills are growing faster than users

Not a fit if

  • You need high availability, clusters or Kubernetes
  • You need 24/7 on-call server support
  • You need email (mailbox) hosting on the same server
02Scope

What I do, and what you get.

What I do

  • Create the server on your account (DigitalOcean, Hetzner, Vultr, Linode, Google Cloud, AWS Lightsail and similar)
  • Harden it: SSH keys only, firewall, automatic security updates
  • Set up the reverse proxy and TLS certificates with auto-renewal
  • Deploy your app (Docker or native), queues, cron and the database
  • Set up encrypted offsite backups and one test restore (Standard)
  • Basic uptime and disk alerts to your email (Standard)
  • Split app and database onto two servers over a private network (Plus)

What you get

  • A running, hardened production server on your account
  • A runbook: deploy, restart, logs, backups, restore, renew, rotate
  • An inventory of what runs where, with versions
  • Handover call or recorded walkthrough, plus notes

Your part

  • A cloud account in your name with billing set up
  • DNS access or someone who can change records
  • Your app in a deployable state (Docker helps)

Included

  • One server (or app + database servers on Plus)
  • Hardening, TLS, proxy, app, workers, database
  • Backups, test restore, basic alerts (Standard and Plus)
  • Runbook

Not included

  • Hosting bills and paid add-ons
  • Mailbox hosting
  • 24/7 support or SLAs
  • Ongoing patching (Care Plan)
03Plans & price

Fixed prices, agreed before work starts.

Starter
$390
Founding price $300
~1 week

One server, proxy, TLS, firewall, app deployed

Standard
$650
Founding price $500
~1–2 weeks

Adds queues, cron, database, backups with test restore, basic alerts

Plus
$1,040
Founding price $800
~2–3 weeks

App and database on separate servers, private network

Build your scope

1 · Plan
2 · After handover (optional)
Your scope
$390
Timeline
~1 week
Payment
Paid in full before work starts
Earliest start
Oct 5
Not a commitment. I confirm the exact price in a written proposal.

Founding price: 3 of 7 spots left, until Mar 31, 2027 — one-off work, in return for a testimonial. How it works

Prices are in USD, paid by bank transfer against an invoice. Work under $1,000 is paid upfront; larger work is 50% to start and 50% before handover, or monthly milestones. How working together works

Variations

Docker app
Compose behind nginx or Caddy.
Native Laravel
nginx, PHP-FPM and systemd queue workers.
Go / Python
A systemd service or container behind the proxy.
Split (Plus)
The database on its own server, reachable only from the app server.
04Process

How it runs.

  1. 01

    Send app and provider

    Email your app stack, provider and domain, and I reply within one US business day.

  2. 02

    Plan and prepay

    You get a short plan with a server size suggestion and a prepaid invoice.

  3. 03

    Build and harden

    I build and harden the server and deploy to a temporary hostname for your check.

  4. 04

    Switch DNS

    We switch DNS in an agreed window and test a restore.

  5. 05

    Runbook handover

    You get the runbook, with an optional Care Plan for patching and checks.

05Proof

Where I have done this before.

06FAQ

Questions buyers ask.

Which provider should I pick?

I suggest one based on your region and budget; you own the account.

Will you keep access afterward?

Only if you want a Care Plan. Otherwise I hand back and you remove my key.

Can it handle my traffic?

I size it from your numbers and leave room to grow; I don’t promise capacity without a load check.

What about email?

I set DNS records for your existing email provider; I don’t host mailboxes.

07Start

Ask about Production Server Setup.

Tell me what you have and where it hurts. I reply within one US business day with either a fixed quote or the entry step that makes a fixed quote possible.

Helpful to include

  • Stack
  • Docker yes/no
  • Expected users
  • Provider preference
  • Domain and DNS host
  • Deadline
Reply within one US business day. No calls needed.

Prefer your own email app? Write to [email protected]. Your details stay with me, never on a list. An AI model drafts a private summary of your message for me.

More in Deployment & DevOps