Can pushd deploy to my existing web hosting?

If it runs cPanel (most shared hosting does - Bluehost, Hostinger, Namecheap, GoDaddy and co), yes. You connect it with your cPanel address, username and an API token.

What will my URL be on cPanel hosting?

https://yourdomain.com/site-name/ - each pushd site is a folder inside your public_html, so your sites live on your own domain.

Why does Chrome ask for an extra permission when I connect cPanel?

pushd can only talk to sites you've allowed. Your server's address isn't known in advance, so Chrome asks once to allow pushd to reach it. Deny it and pushd can't reach your server.

Docs

Deploy to your own cPanel hosting with pushd

Already paying for web hosting with your own domain? If it runs cPanel - and most shared hosting does - pushd can deploy straight into it, and your AI-built pages go live on your domain.

What you need

Web hosting with cPanel (Bluehost, Hostinger, Namecheap, GoDaddy and most shared hosts)
Your cPanel address and username - the ones you log in to cPanel with
A cPanel API token (created below)

Create the token

Log in to cPanel and go to Security → Manage API Tokens (search “API” in cPanel’s search box if you can’t see it).
Click Create, give it any name (e.g. “pushd”), and create it.
Copy the token (cPanel shows it once).

Connect it

cPanel is the one provider with three fields in pushd:

cPanel address - the address you visit to log in, e.g. yourdomain.com or server.yourhost.com
Username - your cPanel login name
API token - from above

When you connect, Chrome shows a permission prompt asking to let pushd access your server’s address. That’s expected: extensions can only talk to sites they’ve been allowed, and your server isn’t known in advance - so Chrome asks once. Allow it. (Deny it and you’ll see “pushd needs permission to reach your server - try again and allow it.”)

Credentials stay in your browser’s local extension storage and are sent only to your own server over HTTPS.

Where your site lives

Each pushd site is a folder inside your public_html: a site named sourdough-recipes goes live at https://yourdomain.com/sourdough-recipes/. Your existing site at the domain root is untouched - pushd only writes inside the site folders you deploy.

This is the one provider where your pages live on your own domain out of the box, no extra setup.

Updating

Same site name = same folder = same URL, updated in place. New name = new folder alongside it.

Errors you might see

“Couldn’t reach your cPanel - check the address (and that your host allows API access).” Wrong address, or the host blocks cPanel’s API (rare, but some budget hosts do - ask their support about “UAPI access”).
“cPanel rejected the login - check your username and API token.” One of the two is wrong - the username is your cPanel login, not your email.
“pushd needs permission to reach your server - try again and allow it.” The Chrome prompt was denied - reconnect and allow.

More fixes: Troubleshooting.

Add pushd to Chrome - it's free All docs