Spinnery
Sign up

Hosted onboarding / private build

Bring Spinnery to your first branch workspace.

Start hosted onboarding at app.spinnery.dev when your organization can use the standard first-release path. Use this private-build intake when you need repo review, access planning, or first-workspace setup help before spin up.

Open hosted onboardingEmail private-build intake
CLI entryspin up

Developers and agents attach to an always-ready shell before the runtime finishes waking.

Onboardingapp.spinnery.dev

Hosted onboarding starts the standard path while Auth0 identity and GitHub App access stay scoped to the repos you choose.

Billingawake runtime only

Runtime CPU and memory bill while services are awake; idle sleep keeps the shell ready without metering the VM.

workspace signupprivate-build queue

Open hosted onboarding for the standard first-release path. This form sends a JSON intake when configured; without that endpoint, Spinnery queues the receipt locally and gives you an email fallback.

First workspace path

A useful intake describes the product path.

The first conversation should produce a workspace plan that can be run, shared, secured, and priced. These are the questions that make the first handoff concrete.

  • Name what repo should become a hosted branch workspace first.
  • Name who can run spin up and who can issue signed links.
  • Name which service wakes the runtime first: web, /api, workers, checks, or resources.
  • Name what signed dev link a reviewer opens and which app routes it covers.
  • Name which costs stay outside Spinnery runtime minutes, including databases, buckets, queues, egress, retained snapshots, and third-party APIs.

What we will review

The signup asks for the workspace shape, not a generic demo.

Early access planning starts with the repositories, organization membership, first runtime size, and awake/sleep policy your team needs before agents rely on branch workspaces.

  • Auth0 organization membership and Spinnery product roles for CLI and dashboard access.
  • GitHub App installation scope for the repositories that should receive spinnery.yml setup PRs.
  • First spin up workflow: shell baseline, services, resources, signed dev links, and readiness checks.
  • Runtime billing expectations while web, API, workers, database, cache, mail, and storage are awake.

After signup

First-release onboarding should leave a receipt.

A private-build follow-up should end with a concrete first workspace receipt: who owns repo setup, which access policies are active, what signed dev link a reviewer opens, and what runtime policy controls cost.

Review first workspace docsReview signed dev links
  1. Repo setupspinnery.yml PR owners

    Selected repositories and spinnery.yml PR owners are named before the first workspace depends on generated setup.

  2. Access setupAuth0 + GitHub App

    Auth0 organization, Spinnery roles, and GitHub App install scope are agreed before CLI or dashboard access opens.

  3. First workspacespin up receipt

    The handoff includes the spin up command, resource readiness, and signed dev.spinnery.dev URL for the first reviewer.

  4. Runtime policysize + sleep + cap

    The receipt calls out runtime size, idle sleep, and cap posture so awake-only billing expectations are reviewable.