[MORSALIN]
Service 7.4Updated September 2026New service

Production Environment as Code: Rebuild Your Server From Scripts

I turn your production setup into files in your repo: server creation, configuration, Docker Compose and a runbook, so you can rebuild it from scratch by following timed, tested steps. Terraform or OpenTofu on request. From $910 ($700 founding) for a single server, 2–3 weeks. Email your current setup to start.

See a sample report, proposal and weekly update
Price
from $910
Founding
from $700
Timeline
2–3 weeks
Format
Fixed scope, fixed price
Hours
US Eastern Time, async
01Fit

Who this is for.

A good fit if

  • Apps running on a server that was set up by hand and never written down
  • Founders who want to switch providers without starting over
  • Small teams who want staging to match production

Common triggers

  • A server died or nearly died and nobody could rebuild it
  • A provider change or price rise
  • An investor or customer asks for a disaster recovery plan

Not a fit if

  • You need Kubernetes, multi-region or auto-scaling groups
  • You want a large multi-account cloud setup
  • Nobody on your side will keep the files up to date
02Scope

What I do, and what you get.

What I do

  • Write down what runs today: packages, configs, services, ports, cron, volumes
  • Script server creation (Terraform or OpenTofu where the provider supports it, or cloud-init)
  • Script configuration (hardening, proxy, TLS, app, workers)
  • Keep app services in Docker Compose with pinned versions
  • Keep secrets out of the repo, with a documented way to supply them
  • Rebuild the whole thing on a fresh server as the acceptance test

What you get

  • An infra/ folder: server definition, bootstrap scripts, Compose files
  • A rebuild runbook with times from the real test rebuild
  • A diagram of what runs where
  • Handover notes

Your part

  • Cloud account access and an API token with limited scope
  • Budget for a temporary test server during the rebuild
  • A person who will own the files afterward

Included

  • Server definition, bootstrap, Compose, runbook
  • One full test rebuild
  • Single node or app/database split
  • Secrets handling approach

Not included

  • Kubernetes, auto-scaling, multi-region
  • Migrating live traffic (Hosting Migration)
  • Ongoing changes (Care Plan or Hours Block)
  • Hosting and test-server costs
03Plans & price

Fixed prices, agreed before work starts.

Single node
$910
Founding price $700
2–3 weeks

One server as code, one test rebuild

Split
$1,560
Founding price $1,200
4–6 weeks, phased

App + database servers, private network, test rebuild; two monthly milestones of $780 ($600 founding)

Build your scope

1 · Plan
2 · After handover (optional)
Your scope
$910
Timeline
2–3 weeks
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

Script-only
cloud-init, shell and Compose with no Terraform state to manage, which is simplest for one server.
Terraform / OpenTofu
For providers with good support (Hetzner, DigitalOcean, Google Cloud), with state stored in your account.
Split
Two servers, with the private network and firewall rules in code.
04Process

How it runs.

  1. 01

    Describe your server

    Email your provider and a description of the server, and I reply within one US business day.

  2. 02

    Inventory and plan

    I inventory the current server read-only and send a written plan with a prepaid invoice (50/50 for $1,000+).

  3. 03

    Write the code

    I write the code and scripts in a branch.

  4. 04

    Test rebuild

    I rebuild on a fresh server and compare it with production.

  5. 05

    Runbook handover

    You get the runbook and the test server is deleted.

05Proof

A new service, done openly.

I have not delivered this exact service for a client before, so there is no case study to point to yet. The approach above is built from parts I have shipped in production — see the case studies — and the fixed price and written scope protect you while it is new.

06FAQ

Questions buyers ask.

Have you done this as a client service before?

This is a new service, with no past case study yet. It’s built from parts I’ve shipped: Docker images and Compose stacks, and software that installs and configures servers on five clouds.

Do I need Terraform?

Not for one server. Scripts plus Compose are often simpler, and I’ll recommend one in the plan.

Can this move me to another provider?

It makes a move much easier; the move itself is a Hosting Migration.

Where are secrets kept?

Never in the repo. In your provider’s secret store, a password manager, or an .env file placed at deploy.

What if production differs from the code later?

The runbook includes a quick drift check, and a Care Plan can run it monthly.

07Start

Ask about Environment as Code.

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

  • Provider
  • Number of servers
  • Stack
  • How it was set up
  • Docker yes/no
  • Who will own the files
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