chronoskin
Release rooms are now in beta

Every release in one calm view

chronoskin gathers deploys, checks and incidents for a small team into a single board, so shipping day reads like a checklist and not a group chat.

Free for teams of up to five. No card needed.

Features

One board, eight small tools

Each box does one job. Use the ones you need and ignore the rest.

Uptime

Checked every thirty seconds from four regions.

99.98%

Release timeline

Every deploy of the last two weeks on one axis, with the slow ones marked.

14 days 42 deploys

Alerts

Route each kind of noise to the right place.

  • Failed deploy
  • Slow check
  • Weekly digest

Deploy checks

A short list that has to be green before the button unlocks.

  • Tests pass on the release branch
  • Migration reviewed by a second person
  • Rollback note written
  • Status page draft ready

Integrations

Hooks for the tools already in your pipeline.

Git push Webhook Chat Pager Email

Command line

Open a release room, tick the checks and ship without leaving the terminal.

$ chronoskin room open
  room spring-12 ready

$ chronoskin check --all
  tests       ok
  migration   ok
  rollback    ok
  status      ok

$ chronoskin ship
  deployed in 48s

Roles

Owners ship, members prepare, guests watch.

Shipped Rolled back Paused Queued

Audit trail

Who pressed what and when, kept for a year and exportable as plain text.

Ship your next release from one box

Open a room in a few minutes and bring the team in when the first check turns green.

  1. Workspace
  2. Releases
  3. Week 14

Releases

Every room opened this week, with its checks and how long the deploy took.

  • Deploys this week 42 6 more than last week
  • Median duration 54 s Fastest 41 s
  • Checks passed 97% 2 rooms waiting on review
  • Rolled back 1 gateway, on Tuesday
ReleaseServiceOwnerStatusChecksDuration
spring-13billingInes OkaforQueued2 / 4-
spring-12billingInes OkaforShipped4 / 448 s
spring-11searchTomas ReylShipped4 / 461 s
spring-10gatewayMara LindqvistRolled back3 / 4132 s
spring-09billingInes OkaforShipped4 / 452 s

Changelog

What the board tells you

Messages stay inside the box they belong to.

A room is open for spring-13

Two of four checks are green. Shipping unlocks when the rest pass.

The gateway deploy was rolled back

Health checks failed in one region after 132 seconds.

No rooms yet for week 15

Rooms appear here when a release branch is cut. You can also open one by hand.

Open a room
  1. Workspace
  2. Releases
  3. spring-13

spring-13

A room for the billing service, opened by Ines Okafor this morning. Two of four checks are green.

Queued All releases

Checks

All four have to be green before the ship button unlocks for members.

  • Tests pass on the release branch Passed
  • Migration reviewed by a second person Passed
  • Rollback note written Waiting
  • Status page draft ready Waiting

Actions

Owners can ship before every check is green. Red undoes the last deploy.

Room log

  • Migration review passed 10:42 · Tomas Reyl
  • Tests passed on the branch 10:17 · automatic
  • Room opened from the template 09:58 · Ines Okafor

Rules for this room

Copied from the workspace template when the room opened.

Quiet hours

No deploys between 18:00 and 08:00 unless an owner overrides.

Set by workspace owners

Freeze days

Mark dates when the ship button stays locked for everyone.

Next freeze: 30 April

Close this room

Closing stops the checks and archives the log. The release itself is not rolled back.

  • Pause deploys for this room
  • Close and archive the room
  1. Workspace
  2. Releases
  3. Open a room

Open a room

Four fields and the room is live. Everything can be changed later from the room itself.

Room details

The name is usually the release branch.

Enter a full address, such as name@team.example.
CancelOpen room

What happens next

A room is live as soon as it has a name and an owner.

  • The checklist is copied from the template
  • The owner gets the first review request
  • The team channel hears about it
  • The ship button stays locked until checks pass
  1. Workspace
  2. Docs
  3. Release rooms

Docs

How a release room works, from the first branch to the confirmed deploy.

Release rooms

A room is a page that exists for one release. It opens when a branch is cut and closes when the deploy is confirmed healthy.

Opening a room

Run chronoskin room open or press the button on the board. The room copies the checklist from your workspace template.

What a room holds

  • The checks that must pass before shipping
  • A running log of every deploy attempt
  • The rollback note, written before it is needed

Closing a room

When the deploy has been healthy for ten minutes the room closes by itself. The log stays readable from the releases page for a year.

Labels

Pills mark state, squares count. Green, amber and red are status only.

Draft Beta New 12
Shipped Queued Rolled back

Further reading

Shown as a link looks when new, visited, under the pointer and pressed.

From the terminal

The same room, without the board.

$ chronoskin room open
  room spring-13 ready