Make the
next release
a clear move.
Bring the plan, the blockers, and the final checks together. A focused workspace for software that’s ready to move forward.
“Almost ready”
is not a
release plan.
Software moves through systems.
Readiness moves through people.
Notes end up in one place. Blockers in another. The decision gets buried in a thread. Relay gives that final stretch a clear structure: what’s changing, what’s missing, and what the owner has reviewed.
Meet Bizartha RelayKeep the next move
in context.
A release queue, a readiness view, and a change history. Built around the work you enter, without pretending to deploy your code.
The next move,
in context.
Three steps.
Fewer loose ends.
Give the release
a clear shape.
Service, version, target date, owner label, and the context behind the change.
PLAN THE MOVE ↗02Make the open
questions visible.
Review five manual readiness checks. Keep blockers next to the decision.
REVIEW THE SIGNAL ↗03Record what
moved forward.
Track the release stage and see a dated history of the changes in your workspace.
CLOSE THE LOOP ↗Useful before
it gets complicated.
Personal workspaces for the builders who keep a release moving. Team invitations and CI connections belong to the next chapter.
Find your use caseFive checks.
No hidden score.
Ready and Released require all five checks and an empty blocker field. These are human-entered attestations. Relay does not run your tests, approve changes, or trigger deployments.
Understand the readiness ruleA little more thought.
A clearer way to build.
A release checklist that earns its place.
A short checklist is useful when each check names a real question.
Read the note ↗Plan the way back before the way forward.
A rollback discussion belongs in release preparation, while there is time to think.
Read the note ↗A clear handoff is a product feature.
The person reviewing a release should not have to reconstruct its story.
Read the note ↗A few clear
answers.
What is available in this release?
Individual accounts, saved release records, five readiness checks, blockers, stage tracking, a change history, search, filters, and CSV/JSON export. You can also explore a local demo without an account.
Does Relay deploy software?
No. It organizes the release decision. Your existing CI, repository, monitoring, and deployment systems remain responsible for execution.
Can I invite my team?
Current workspaces belong to one account. Shared access and role-based invitations are planned, as described on the roadmap.
How much does it cost?
The current early-access workflow is available without a payment card. Paid team capabilities are planned; no paid subscription is created by using this release.