← EAS / Free Help
Epic App Solutions // DIY Website Ownership Tool

OWN YOUR SITE.
USE AI AS THE CREW.

You can hire us. Or you can learn to run the thing yourself. This tool walks you through domain ownership, hosting access, website files, an AI handoff file, a safe development copy, backups, and deployment.

Start here

What do you already have?

Check what you already control. The tool will tell you what still needs attention.

Choose your AI

Use the assistant you understand.

OpenAI // ChatGPT + Codex

Use ChatGPT for planning, explanation, review, and Codex when you want an agent to work directly with code and engineering tasks.

Open ChatGPT Open Codex

Anthropic // Claude + Claude Code

Use Claude for planning and code review, and Claude Code when you want an agent working through a codebase and development tasks.

Open Claude Open Claude Code
The logo on the AI matters less than the workflow. The goal is to keep the business owner in control of the domain, hosting, files, credentials, backups, and final deployment decisions.
Guided setup

Build the chain of ownership.

STEP 1 OF 7

Own the domain yourself.

Buy your domain from GoDaddy or another registrar using your own account and your own email address.

Do not let a developer be the only person who controls your domain registrar account. Your domain is the address of your business.
GoDaddy Domains
STEP 2 OF 7

Get hosting access.

Call your hosting provider and ask:

I own this website and need access to upload and download my site files. Please show me how to access the hosting file manager or provide SFTP/FTP credentials and tell me which folder is the live web root.
Ask them whether they support SFTP. Prefer SFTP over plain FTP whenever it is available because the connection is encrypted.
STEP 3 OF 7

Download the whole site before changing anything.

Your first job is not editing. Your first job is getting a clean copy you can restore.

KeepHTML, CSS, JavaScript, images, fonts, configuration files, and any server-side files your site needs.
Also captureDatabase exports and environment/config information if the site is dynamic.
Never put passwords, API keys, SFTP credentials, database passwords, or secret tokens into files that will be publicly served by the website.
STEP 4 OF 7

Give the AI a handoff file.

Use the generator below to create a small EAS project JSON. This gives the AI context before it starts changing things.

STEP 5 OF 7

Clone first. Break the clone.

Never learn on production.

Tell your AI to make a separate development copy. That can be a local folder, a staging site, or a separate subdomain depending on the project.

Read the website and the EAS project JSON first. Do not modify production. Create a separate development copy. Explain the folder structure to me in plain English. We will make and test changes there first.
STEP 6 OF 7

Make changes, then force a review.

When the development version looks right, do not jump straight to upload.

Compare the development copy to the current production site. List every changed file and summarize each change. Identify anything risky. Do not deploy yet.

Then test links, forms, mobile layout, images, navigation, analytics, and anything tied to business operations.

STEP 7 OF 7

Back up production. Then deploy.

Create or confirm a current production backup first. Then deploy only the approved development changes. Do not overwrite unrelated files. After deployment, verify the live site and tell me exactly what was changed.
AI can make mistakes. You are still the owner and final decision-maker. For payments, customer data, authentication, legal/compliance systems, or anything you cannot safely restore, bring in a qualified developer before deployment.
EAS project handoff generator

Build the JSON you hand to the AI.

Starter prompt

Give this to ChatGPT/Codex or Claude/Claude Code.

Reality check

What AI does not magically fix.

Bad ownershipIf your old developer owns the domain, hosting, repository, or accounts, AI cannot magically transfer legal or administrative control.
No backupsIf production is destroyed and there is no backup, the AI cannot restore files that no longer exist.
Unknown business logicComplex payments, customer data, integrations, authentication, compliance, and databases deserve real review.
What EAS believes

A good developer should make you more capable.

We will build it for you. We will teach you to run it. Or we will hand you the files and show you the door. Any of those can be a successful project.

If the job becomes difficult, call us because the problem is difficult — not because somebody held your passwords hostage.

Call 209-672-0033 Email EAS Epic App Solutions
Session handoff

Generate a plain-English checklist.

Talk to EAS

Leave a tip, note, idea, question, or project thought.

What you type here is not public.
This is a local browser form. Nobody else sees what you are typing just because it appears on this page. Nothing is automatically posted to a website, social feed, database, or public comment system. Your text only leaves your browser if you choose to copy it or click Email EAS.
Report a bug

Something broke? Tell us exactly where.

Bugs are useful. Tell us what you clicked, what you expected, and what happened instead. Do not paste passwords, API keys, hosting credentials, private customer data, or other secrets.

Epic App Solutions // Website Ownership Tool v0.2
Build the asset. Own the asset. Keep a way back. Report what breaks.