Your website / Your choice

We can handle the setup. You keep your website.

A one-off website includes its initial launch and a handover pack. Monthly care adds ongoing support. You do not need to learn how hosting works before we can build for you.

Choose how much you want to do.

• Set everything up for me. We choose suitable services with you, arrange a separate setup for your business and handle deployment, the web address and contact forms. You approve charges and complete any required email, identity or payment verification.
• Use my existing accounts. Keep your domain and hosting where they are if suitable. Invite us with the access needed for the agreed work.
• Help me manage it myself. We guide you through opening accounts, launch the site, and show you how to keep it running.

“Done for you” describes who does the work. Your business is still the domain registrant and owns the delivered website. Use an email you can access even if the website goes offline. We arrange owner or recovery access and keep your setup separate from other customers. Some providers require you to open the account or accept their terms yourself; we guide you through those steps.

We use invited access where supported. You should not email us passwords, card details or recovery codes. You never need our master account to retrieve your website.

Who pays for what?

The build: you pay Coding Upwards the agreed website price. The domain: the registrar normally bills you annually. Hosting: a suitable simple website may qualify for a free plan; paid hosting, email, booking systems and other services are agreed separately.

Monthly care is £39. It covers management, checks, backups before changes and three defined content updates each month. We credit a standard domain registration or renewal against your care invoices, up to £20 per 12 months while care is active. You pay the registrar directly and share the receipt. For example, a £12 domain bill and a £27 first care invoice total £39 that month.

For clients who want one managed bill, ask us to agree an arrangement in writing before setup. It must name the included services, usage limits, renewal prices and how provider billing transfers when you leave. It is not automatically included in the standard plan. Premium domains and unexpected provider charges need your agreement.

A domain is your web address. Hosting serves the site. Business email is a separate service. Buying one does not automatically include the others.

How to host a one-off website yourself.

We normally do the initial launch for you. These steps explain how to take over or redeploy later. Your handover pack contains the exact instructions for your particular website.

1. Find the handover pack. Keep the source ZIP or repository, approved images, licence notes, deployment guide and list of services. Confirm whether the project is a static website or needs a server, database or external form service.
2. Open the right accounts. Use your business details and an email independent of the new domain. Verify that email, enable two-factor authentication and keep recovery codes privately. Add your payment method only on the provider’s own billing page.
3. Choose a compatible hosting plan. A static website serves already-built files. An app with logins, bookings or saved enquiries may also need server functions, a database and email delivery. Check current limits and pricing before choosing a plan.
4. Deploy a test address first. Follow the build command and output-folder name in your pack. For a simple static export, upload the built folder containing index.html and its assets to a supported static host. With a connected repository, select the supplied branch and build settings. Uploading the source folder is not always enough.
5. Configure any backend. Use the runtime, database migrations and environment-variable names documented for your project. Add secrets through the hosting dashboard, never into public files. Restore agreed data exports and configure form recipients or email-provider permissions. A static upload cannot replace these parts.
6. Connect your domain. Add the domain in the hosting dashboard and follow its DNS instructions. Back up the existing DNS records first. Preserve records used by business email, including MX and relevant TXT records. Check both the main address and the www version. If nameservers need changing, copy existing records before switching.
7. Check the live customer journey. Confirm HTTPS works, images load, navigation works on phone and desktop, forms reach the correct inbox, and any booking or payment integration uses the correct live account. Check redirects from old page addresses before replacing an existing site.
8. Keep it running. Turn on renewal reminders, check provider billing and usage, retain a source backup, and test forms periodically. Back up databases separately from the website files. Keep software dependencies and external integrations maintained.

Cloudflare is one option, not a requirement. Its guides cover uploading a static site, connecting a domain and inviting someone to manage your account. A Cloudflare Pages Direct Upload project cannot later switch to Git integration in place; choose the deployment approach before creating the project. We record the chosen method in your guide.

What is in your handover pack?

• Website source, approved assets and applicable licence notes.
• Owner account and project links, domain expiry and billing responsibilities.
• Exact runtime, build and deployment instructions for the delivered version.
• DNS records, redirects, form destinations and external-service settings.
• For apps: database setup, agreed data export, backup and restore instructions, and how to configure your own credentials.
• A short check list for launching, testing, restoring a backup and inviting another developer.

The pack never contains another customer’s information or our shared account secrets. Third-party software and images retain their own licences.

What happens if I cancel monthly care?

Support ends at the end of your paid month. We confirm your access and future billing, provide the latest handover pack and remove our access once the handover is complete. Your site stays in your account subject to your provider’s plan and payments. Your paid domain registration continues until its expiry; you handle later renewals.

There is no surprise fee for the standard handover. Moving to a different platform, redesigning the site or adding features is separate work. If we agreed a managed billing arrangement, we confirm the transfer steps and costs with you before support ends; some platforms require a migration rather than simply changing a login.

Read the care terms or send us a setup question.