Uptime
Checked every thirty seconds from four regions.
99.98%
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
Each box does one job. Use the ones you need and ignore the rest.
Checked every thirty seconds from four regions.
99.98%
Every deploy of the last two weeks on one axis, with the slow ones marked.
Route each kind of noise to the right place.
A short list that has to be green before the button unlocks.
Hooks for the tools already in your pipeline.
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
Owners ship, members prepare, guests watch.
Who pressed what and when, kept for a year and exportable as plain text.
Open a room in a few minutes and bring the team in when the first check turns green.
Every room opened this week, with its checks and how long the deploy took.
Messages stay inside the box they belong to.
Two of four checks are green. Shipping unlocks when the rest pass.
Health checks failed in one region after 132 seconds.
A room for the billing service, opened by Ines Okafor this morning. Two of four checks are green.
All four have to be green before the ship button unlocks for members.
Owners can ship before every check is green. Red undoes the last deploy.
Two checks are still waiting, so only an owner can ship now. The deploy takes about a minute and can be rolled back from this room.
Copied from the workspace template when the room opened.
No deploys between 18:00 and 08:00 unless an owner overrides.
Mark dates when the ship button stays locked for everyone.
Closing stops the checks and archives the log. The release itself is not rolled back.
Four fields and the room is live. Everything can be changed later from the room itself.
The name is usually the release branch.
A room is live as soon as it has a name and an owner.
How a release room works, from the first branch to the confirmed deploy.
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.
Run chronoskin room open or press the button on the board. The room copies the checklist from your workspace template.
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.
Pills mark state, squares count. Green, amber and red are status only.
Shown as a link looks when new, visited, under the pointer and pressed.
The same room, without the board.
$ chronoskin room open room spring-13 ready