ARCWEAVER RELEASE DESK

One release.
The whole preparation.

A focused individual workspace for the context you need before a consequential change.

◒ Release DeskILLUSTRATIVE WORKSPACEIndividual pilot
YOUR NEXT RELEASE / A CLEARER VIEW

A place for the
whole release.

+ New release
01
API access controlsProduct · 2 of 3 checks passed
In review
02
Worker runtime refreshInfrastructure · 2 of 2 checks passed
Ready
03
Reporting schema v2Data · checklist not started
Draft
SCOPE → ROLLOUT → CHECKS → ROLLBACK FICTIONAL DATA
01 / DEFINE

Give the change
a clear boundary.

Capture the release title, scope, category, owner label, target date, and status. Keep the rollout and rollback plans beside the intended change.

Each individual workspace supports up to 200 releases. The owner label is descriptive and does not invite, notify, or grant access to another person.

02 / CHECK

Keep every check
with the release.

Add Quality, Operations, and Security checks with a title, owner label, and evidence or next step. An optional HTTP/HTTPS URL can point to authorized external context.

Up to 2,000 checks per account. Passed is your manual attestation. The application does not fetch a URL, run a test, or verify its result.

03 / REVISIT

Readiness needs
current context.

Ready requires rollout and rollback plans of at least 30 characters each, at least one check, and every linked check passed. A change to the checklist reopens affected Ready releases as In review.

Adding, changing, moving, or removing checks can reopen review. A move can affect both releases. Readiness does not authorize or execute deployment.

04 / HAND OFF

Take the record
with you.

Export a release brief as TXT with scope, both plans, and all linked checks. Export all releases and checks as CSV, or the workspace and recent activity as JSON.

Search and filters help you inspect a subset. CSV and JSON always include all workspace records, regardless of the current filter.

AVAILABLE NOW

An individual release workspace.

Accounts, saved releases and checks, readiness controls, activity, search, export, password reset, and account deletion.

FUTURE DIRECTIONS

More connections, deliberately.

Shared workspaces, invitations, CI/CD integrations, and automated evidence collection are not enabled. No delivery date is promised.

MAKE THE NEXT RELEASE LEGIBLE

Tie up the loose ends.
Then take the next step.

Free individual pilot. No card required.

PRIVACY CHOICES

Only what the workspace needs.

No advertising trackers or third-party analytics are included. Accounts use an essential session cookie; demo edits stay in your browser.

Clear demo data to remove local examples and edits. Export anything you need first.

Read the Privacy Policy ↗