Hosting with 20% off when you buy through the link

Client sites

Give a client or a colleague access to a site with a small file and no passwords. They connect with their own Claude and choose a full local copy or editing live.

An access file lets an agency hand a client, a freelancer or a colleague what they need to work on a site with their own Claude, with no passwords and no technical setup. It's a small file named after the domain, such as floresbakery.example.velk, with only public details: the site's address, the server and the folder. It carries no secret: access exists only once someone authorizes the client's Mac key on the hosting, so it can go by WhatsApp or e-mail.

The agency asks

Create an access file for this site, to send to the client.

In the site's project folder, where the deploy settings live. The AI writes the file and a message to forward: open Claude, in the Code tab, in a new folder, attach this file and say “connect this site”.

The client asks

Connect this site.

With the .velk file attached, in a new empty folder, which becomes the site's project folder.

What happens when the client connects

  1. The Mac

    The flow needs macOS 15 (Sequoia) or newer; on anything else the AI stops before doing anything.

  2. The site

    The AI shows the site, the server and who created the file, and asks you to confirm, which also guards against a forged file.

  3. Your name

    It asks your name, which appears on every publish and on a key it creates.

  4. The key

    It uses your Mac's SSH key, or creates one, and shows the public part with one instruction: authorize this SSH key on your hosting.

  5. The test

    Once you say it's done, it tests the connection.

  6. The way of working

    It asks whether you'll create pages and change the look, or make occasional adjustments.

What the AI runs
# at the agency, in the site's folder $ scripts/access/generate.sh --project . ✓ Access file written: /Users/ana/Sites/flores/floresbakery.example.velk # at the client, in the new folder $ scripts/access/connect.sh platform $ scripts/access/connect.sh inspect floresbakery.example.velk $ scripts/access/connect.sh setup floresbakery.example.velk --project . --identity "Marina Costa" $ scripts/access/connect.sh key --project . $ scripts/access/connect.sh test --project . $ scripts/access/connect.sh mode local --project .
The skill's scripts, in the scripts/ folder of the Velk plugin. The AI runs them one at a time and asks you the questions in between.

Authorizing the key

An SSH key is a pair: the public part goes to the server, the private one never leaves the Mac. Whoever has access to the hosting pastes the whole public line in the panel's SSH keys area (Hostinger: Advanced → SSH Access; cPanel: SSH Access): you, if the hosting is yours, or the agency, if it runs it.

One key serves every site the Mac connects to; a second site only needs it authorized on that hosting. A key the AI creates is labelled with velk, your name and the date, easy to find on the server, and deleting it there removes the access.

If the test fails, the AI says why: the key isn't authorized yet (or was pasted incomplete), or the server didn't answer. If it says the server's identity changed, stop and confirm with the agency: it can be a server move, or an impostor.

Two ways to work

ModeHow it works
Full local copyFor whoever builds or restyles pages: a copy of the site on your Mac, to see each change before publishing it. Needs PHP and MySQL, which the AI offers to install with Homebrew, the Mac's package installer.
Edit liveFor occasional adjustments. Nothing is installed: for each theme change, the AI downloads a fresh copy of the live theme, edits it, publishes it versioned and deletes the copy.

Switching, and the local copy

Switch whenever you like: “I want to run the site locally” or “I want to edit straight on the live site”. When you start iterating on a new page live, publishing and adjusting over and over, the AI suggests the local copy.

For the local copy, PHP has to match the server's version, since code that runs on a newer PHP can fail on the server's; the AI tells you when it can't. If Homebrew itself is missing, its installer asks for your Mac's password, which only you type, in Terminal. Then the AI builds the copy and gives you the local address, a login that exists only on your Mac, and how to start the site. Asking again refreshes the copy, but it stops first if your theme has changes not yet published.

What the local copy gets

From the live siteOn your Mac
The engineThe exact version the server runs, from the official release, never copied from the server.
The themeAs it is live, ready for the next publish.
Media library filesAll of storage/uploads/, which can be large.
Pages, posts, categories, options, languages and translationsAll of them.
Users, members, orders, form submissions and their attachmentsNever.
Form recipientsNever: a test on your Mac doesn't e-mail the real recipient.
Tracking scripts and conversion snippetsNever: localhost doesn't fire the client's pixels.
Secrets: the production database password, SMTP, Stripe, TurnstileNever. The content is exported on the server, so that password never reaches the Mac.

Common questions

Is the access file a password?

No. On its own it opens nothing: without the key authorized on the hosting, there's no access.

How do I remove someone's access?

Delete their key in the hosting panel's SSH keys area. From then on their AI gets “not authorized”.

Can the client edit content without touching the theme?

Yes. A post or a page's text goes through the admin, or by asking the AI (see Content by conversation), and never touches the theme.