Set up your own evebots installation

Establish your owner identity

Each installation uses its own Vercel project, private Blob store, OAuth App and GitHub connector. A visitor cannot claim this deployment.

  1. Import your authorized copy of the source into your own Vercel account. Private source requires Git access; no public one-click claim is made. Import a repository.
  2. Attach your own private Blob store in project Storage. Storage instructions.
  3. Create your own Vercel OAuth App with an exact HTTPS callback ending in /api/auth/vercel/callback, openid and client_secret_post. App instructions.
  4. In your project’s protected environment settings, set FLEET_VERCEL_CLIENT_ID, Sensitive FLEET_VERCEL_CLIENT_SECRET, independently verified stable FLEET_VERCEL_OWNER_IDS, canonical FLEET_AUTH_ORIGIN and FLEET_AUTH_MODE=vercel. Redeploy after all values are set. Never put secrets in a URL or source file. Stage explicit token mode when migrating existing credentials.
  5. Configure rate limits for the OAuth start/callback routes per the canonical setup guide. Sign in as the preconfigured owner, then reopen this wizard.
Sign in with your configured owner account

Token fallback does not unlock setup. Setup uses expiring, revocable OAuth sessions and the explicit owner allowlist. If you do not control the deployment settings, ask its owner for access; there is no first-user enrollment.