FRAME THE CHANGEKeep the scope
Keep the scope
in focus.
Record the intended change, target date, owner label, rollout plan, and rollback plan. Give the next reader a coherent starting point.
Explore release records ARCWEAVER / RELEASE READINESSShip with the
Ship with the
loose ends
tied.
Bring the scope, the checks, and the return path together. A focused workspace for releases that deserve a considered next step.
INDIVIDUAL PILOT / FREE TO START / NO CREDIT CARD
RELEASE / 002Ready
Worker runtime
refresh
Infrastructure · target Nov 3
- 01 Scope and rollout Defined ↗
- 02 Release checks 2 of 2 passed
- 03 Return path Documented ↗
A RETURN PATH IN VIEW.
ONE RELEASE RECORDScope↗Checks↗Rollout↗Rollback
A release is more
than a date
on the calendar.
The scope lives in one place. The checklist in another. The rollback plan is a question someone still needs to ask.
Release Desk gives the next change a single record: what is changing, what has been checked, and how the operator plans to return if needed.
See the complete workflowTHE WORKSPACESee what is ready.
See what is ready.
See what needs work.
Three connected views. A practical record of the release and the decisions still ahead.
◒ Release DeskILLUSTRATIVE WORKSPACEIndividual pilot
YOUR NEXT RELEASE / A CLEARER VIEWA place for the
+ New release
A place for the
whole release.
+ New release01
API access controlsProduct · 2 of 3 checks passed
In review02
Worker runtime refreshInfrastructure · 2 of 2 checks passed
Ready03
Reporting schema v2Data · checklist not started
DraftSCOPE → ROLLOUT → CHECKS → ROLLBACK FICTIONAL DATA
Try the interactive workspace The demo contains fictional examples. No deployment is executed.
CONNECT THE CHECKSMake the work
Make the work
reviewable.
Keep Quality, Operations, and Security checks linked to the release. Record evidence or the next step, then mark passed after your own review.
Explore release checksREVISIT THE CONTEXTA change deserves
A change deserves
another look.
Updating a checklist reopens affected Ready releases. Export a portable brief with the scope, plans, and evidence intact.
Explore readiness and exportsA BETTER HANDOFF STARTS HEREFor changes with
For changes with
moving parts.
Product releases, infrastructure updates, and data changes. One practical way to keep the preparation connected.
Find your starting pointFIELD GUIDESA clearer way
All field guides A clearer way
to prepare.
RELEASE PRACTICE
Before you call it ready.
A status needs an explanation, not just a green label.
Read the guide ↗OPERATIONSWrite the return path first.
A rollback plan makes the release conversation more concrete.
Read the guide ↗WAYS OF WORKINGA handoff worth keeping.
Give the next reader a coherent release record.
Read the guide ↗BEFORE YOU BEGINA few useful
A few useful
distinctions.
Does Release Desk deploy software?
No. It organizes manually entered release preparation. It does not connect to a CI/CD system, execute tests, change infrastructure, or deploy a release.
What makes a release Ready?
A rollout plan and rollback plan of at least 30 characters each, at least one linked check, and all checks passed. Ready is a workflow label, not independent approval or proof of safety.
Can I use it with a team?
The current pilot has individual workspaces. Owner labels are descriptive; invitations, shared access, and notifications are future directions.
Can I start without a payment card?
Yes. The individual pilot is $0. Business requirements use a separate inquiry and written commercial scope; no automatic paid subscription is created.
Tie up the loose ends.
Then take the next step.
Free individual pilot. No card required.