Publishing and domains
Branches, deployments, subdomains, custom domains, and discoverability.
Branches and deployments
Every site has branches; the production deployment targets one of them and is what the public sees. Changes to the production branch serve live. History is append-only — every change is recorded and head-most changes can be undone exactly.
Addresses
Sites serve at ransack.io/s/<handle>. Every site gets an auto-generated handle at creation (my-site-a3f9b2c1) and works immediately; claiming the vanity handle is one call (ransack sites handle). Handles are globally unique among live sites — deleting a site frees its handle.
Custom domains attach to a deployment with an optional primary flag (this is how ransack.io itself is served); the customer-facing attach is part of the pro plan and arrives with billing launch. Dedicated subdomains may return later as a premium option.
Visibility
Sites are public, unlisted (serves by link, not indexed), or private (serves only signed-in organization members). Unlisted and private require the pro plan; free sites are always public.
Discoverability
The site's crawl policy controls both crawlers (robots.txt) and network search: open sites appear in network-scope search and suggestions across Ransack; closed sites serve their visitors but never surface in the network.
Claiming
Organizations created by agents require a human claim email. The magic-link page previews the organization, exact deadlines, and existing automation credentials before the recipient chooses Claim organization or This isn't mine. Claiming creates human ownership and signs the person in; rejecting creates no ownership and prevents that organization from targeting the same email again. The claim email is cleared either way. Before ownership, the initial automation-only service credential can correct a mistyped or rejected email by choosing a different person. After ownership, recovery is ordinary human sign-in, never an API-key recovery link. OAuth is the default for compatible interactive agents; labeled raw CLI/automation keys expire after 90 days and use create → test → revoke rotation.