PLAN THE PERIOD Save 28% on 6 months · 50% on 12 months · paid upfront.
PrivateHostLabLet’s talk projects
THE PROJECT NOTEBOOK

The work around the server.

Choose a project path, use a worksheet and leave the next operator a clearer record. Twenty guides connect budgets, recoveries, migrations, launches and handovers.

Choose the next decision

  1. New client project: define responsibilities, compare shared and separate servers, then prepare a complete budget.
  2. Existing site moving: inventory and rehearse the migration, agree acceptance, then preserve the operating handover.
  3. Time-limited campaign: prepare its traffic window, approve the launch and schedule exports and closure.
PROJECT WORK

Scope & budget

Decide who operates the project, where its boundaries sit and what the full commitment costs.

Budgets & payments02
5 min read · Planning guide

Build a hosting budget your client can approve.

Separate VPS resources, outside services and agency work, then compare the upfront period total with a clear renewal and review plan.

Client operations04
5 min read · Planning guide

One VPS or separate servers for client projects?

Compare cost, access, maintenance and incident impact before placing client projects together, with a practical decision matrix and review checklist.

Budgets & payments08
4 min read · Planning guide

Keep a clear payment record for a client project

Separate the approved USD budget, prepaid period, crypto quote, transfer evidence and provider confirmation in one usable project record.

PROJECT WORK

Migration & launch

Prepare the move, rehearse the work and give the client a clear acceptance decision.

Migration & launch01
5 min read · Planning guide

Plan a client migration around the last write.

Build an inventory, rehearse real client workflows and document the data, DNS and rollback decisions before moving a website.

Client delivery06
4 min read · Planning guide

Turn a launch into a client acceptance checklist

Agree on launch evidence for forms, redirects, access, scheduled jobs and data, then record a clear client acceptance or refusal.

Campaign launches05
5 min read · Planning guide

Prepare a campaign site for a traffic window

Plan a campaign launch around publication times, caching, dynamic work, external services and a bounded rehearsal with clear stop conditions.

PROJECT WORK

Ownership & handover

Assign duties and leave access, recovery and renewals usable by the next operator.

Ownership & access03
5 min read · Planning guide

Give every client hosting responsibility an owner.

Prepare a client–agency responsibility matrix with replacements, escalation triggers, recovery evidence and a practical handover acceptance check.

Client delivery07
5 min read · Planning guide

Offboard a contractor without losing the project

Transfer account ownership, test the handover with a replacement operator, revoke old access and retain recovery evidence without recording secrets.

Put the guides into a project

Check the offer alongside the plan

Use service facts for catalog-derived allocations, period totals and scope. The 28-question FAQ connects everyday project questions to the deeper worksheets. Prepare a local brief when your next decision needs a clearer context.

SHARED PROJECT LANGUAGE

A glossary for the handover

Sixteen terms used across these guides. These working definitions help the client and operator discuss the same decisions.

Account owner
The person or organization with authority over the service account and its recovery. This may differ from the application operator. Read in context.
Application operator
The named person responsible for the project’s application work, such as updates, deployment and recovery, within the agreed scope. Read in context.
Acceptance check
A comparison of an agreed expected result with an observed result, recorded for a named approver. Read in context.
Write boundary
The agreed point and process for controlling new data during a move, including forms, uploads, integrations and jobs. Read in context.
Rollback
A planned return to a previous working state. New data written after a switch can make a simple reversal unsafe. Read in context.
DNS TTL
A DNS record’s time-to-live value, which affects how long resolvers may cache it; it is not a promise that all traffic switches instantly. Read in context.
Scheduled job
Application work launched on a schedule, such as an export or notification. Its owner and timing belong in a migration inventory. Read in context.
Incident scope
The set of projects, data and operators that could be affected by a failure or compromised access. Read in context.
Recovery point objective
The amount of recent data loss the project is prepared to tolerate, expressed in time. It is a target to design and verify against. Read in context.
Recovery time objective
The target time to restore an agreed service after disruption. A target is not proof of an achieved recovery time. Read in context.
Restore rehearsal
A controlled attempt to recover a usable application from its backups, with evidence of what was restored and checked. Read in context.
Monthly reference
The configuration’s monthly USD resource and option cost before a service-period discount. Read in context.
Prepaid period
The selected service interval paid in one upfront amount. Its total and renewal decision are distinct from a monthly reference. Read in context.
Payment route
The exact asset and network combination selected at checkout; the same asset symbol on another network is not interchangeable. Read in context.
Local payment reference
The browser-generated identifier for a quote. It is not a receipt, server-issued order or proof of payment. Read in context.
Least privilege
Giving an operator only the access needed for the agreed duties and reviewing it when those duties change. Read in context.
AGENCY OPERATIONS

More decisions, written down.

Twelve added guides cover purchase approval, recovery, DNS, updates, storage, access and campaign closure. They complement the original project worksheets.

A GOOD PLACE TO START

Make room for your next project.

Find your starting point