Accountless Deployment

An AI coding agent can put a Diode Vibe site on the internet before the person has signed up. The person claims that workspace afterward — password or the sign-in they already use — and the same agent keeps deploying. Containers, Nexus, and further projects unlock the moment they claim.

This is the path to use when someone says “just ship it” and they do not have a Diode Vibe account yet.

What the agent should read

The steps, proof of work, and URLs are on https://vibe.diode.io/agents.

What happens

  1. The agent solves a short proof of work and creates a temporary workspace. No account and no email are required.
  2. The agent receives a token and a claim link, once. It can publish one static site immediately and give the person the link and the live URL.
  3. The person has 60 minutes to claim. Opening the link does not use it up. Attaching an email sends a claim message and does not keep the site up longer.
  4. On the claim page they set a password (12 characters or more) or use an existing sign-in, and they accept the terms. The agent cannot accept the terms.
  5. After claim, that same token works for 6 hours (or until they revoke it on the first screen they see). Container projects and Nexus project generation start then. Confirming the email raises the balance from the preview credit to the normal starting credit.

Until they claim, a container create does not fail with “not supported.” The agent is told to give the person the claim link and to create the container with the same token as soon as they finish.

What Diode Vibe is for, beyond that first static site

https://vibe.diode.io/agents is the source of truth for the agent. In short, the person can grow in place on the same product:

  • Static sites on *.diode.link
  • Python and Node containers when they need an API, a database client, or server-side rendering
  • Larger containers on Standard and Enterprise, without changing the project
  • Their own servers — Remote Docker hosts registered for the workspace
  • Their own AI — Nexus pointed at the organization’s endpoint and models, including organization data and tools
  • Enclaves — named pools of those servers (HIPAA, ISO 27001, NERC CIP, SOC 2, or a custom pool) so containers stay on the machines in that pool
  • Shared infrastructure — an Enterprise workspace connects divisions, partners, or customers, who place work on the enterprise hosts and Nexus and can be paid for by the enterprise

A preview is one static site on purpose. The rest of the platform is what they unlock by claiming.

For the person

You will get a link from the agent (and an email, if you gave the agent an address). Open it, accept the terms, and choose a password or your existing sign-in. The first page shows the agent’s access and a revoke button. Revoke if you do not want that agent to keep deploying.