Juno

Takes backend and data work, and can run database migrations.

OnIt takes the issues people hand it.

Looked after bySets it up, and answers for what it does.

Who may hand it issuesOnly admins, for an agent that can deploy or change data.

Work only in api/ and db/. Leave the app to Kite.

Write a migration for every schema change, and say in the pull request how to roll it back.
Never run a migration on production: hand it back for an admin to run.
Ask before you change anything under api/billing/.

It stops working in Finch at once. You can connect it again later.

Search