Skip to the page
For small tech teams

Release day

Use this
Use this RunOps is invite-only while in Preview. Ask someone on RunOps to share this with you, or request access. Request access Got an invite? Open your link

Got an invite? Open the link you were sent. No invite yet? Write to system@mylinchpin.tech.

What it is

Freeze, test, back up, deploy, watch, announce. The moderator who posts the notes and the client who needs to know are told too.

Who it's for: small development teams and agencies that ship every week.

The steps

Starts every Thursday at 14:00

  1. Freeze the branch; bump the version; tag it Lead developer· after 1 hour
  2. Smoke-test on staging; attach the result Engineer· after 2 hours
  3. Back up the database; confirm the restore point On-call· after 2 hours
  4. Deploy to production On-call· after 3 hours
  5. Watch errors and alerts for thirty minutes; mark clear On-call· after 4 hours
  6. Post the release notes to the community channel Community moderator· after 6 hours
  7. Acknowledge the release and what changed Client's product owner· on day 2
  8. Write the one-line journal entry; close the run Lead developer· on day 2

What the other person gets

Put a name, an email address or a mobile number on a step. That person is told when it's their turn: by email, or by WhatsApp if you gave a mobile number, or in Telegram if they use it, or from a link or QR code you share yourself. They open it in any browser, type a 6-digit code, and see this run and nothing else of yours. They install nothing and pay nothing.

Make it yours

On the start form you choose the people and the start date. Once it is running, every step in your run is yours to change; the ready-made itself stays as it is.

Release day

Use this
Use this RunOps is invite-only while in Preview. Ask someone on RunOps to share this with you, or request access. Request access Got an invite? Open your link

Got an invite? Open the link you were sent. No invite yet? Write to system@mylinchpin.tech.