Owl + KestrelNest

Documentation / customer guide

Start with source.
Keep your way out.

Nest uses ordinary Git. The external alpha is designed so a new customer can import, clone, push, back up, export, and delete source without private O+K operator access.

01

Quickstart

  1. Create a Nest account and one organization.
  2. Create one repository or import one from GitHub.
  3. Choose visibility and create a scoped Git credential.
  4. Clone, change, and push using ordinary Git.
  5. Connect one GitHub backup destination and wait for verified backfill.
  6. Invite a person or add a bounded agent principal.

External account activation is not open yet. This guide defines the path being implemented and will become executable without changing its source-ownership model.

02

Nest is the source authority

After import, Nest owns the canonical repository and ref policy. GitHub is downstream. Local clients push once to Nest; a failed backup never asks a person or agent to dual-push or decide which remote is real.

03

GitHub lowers the switching cost

Import brings the selected repository's Git history into Nest. Backup sends later eligible Nest refs to one selected GitHub destination, verifies exact SHA equality, and exposes current, lagging, or failed state.

Connecting a destination creates a durable copy controlled by that GitHub account. Disconnecting stops future managed writes; it cannot retract source already received.

04

Free external-alpha limits

  • 1 organization
  • 1 repository
  • 100 MiB aggregate source storage
  • 3 human, agent, or service principals
  • 1 GitHub backup destination

Limits will be visible before enforcement. Reaching one must never block reads, export, or deletion of existing customer source.

05

Ownership and exit

Customers retain ordinary Git history and can clone or export it. Nest's paid boundary may add capacity, governance, automation, and support; it must not hold basic source access or export hostage.