Understudy serves two surfaces: the runtime, the public stand-in your app calls, and the editor, the private place where you manage simulations. The editor is protected by a login that needs no setup.
How it works
- First run: when no admin exists, the editor shows a one-time "create admin account" screen. There are no environment variables and no config files to set.
- After that: a normal username and password sign-in. It issues a signed token that is sent on every editor request.
- Sign out clears the token.
Where it is kept
The admin account, with its password safely hashed, and the signing secret are stored in the same store as everything else. Nothing extra to provision. Point Understudy at a shared store and your team signs in to the same editor, so a deployed stand-in is something the whole team manages together.