DataDefend Nerve · internal tooling

Builds the current main on GitHub Actions, uploads the images and the deploy bundle to S3, and records the release here. Takes about eight minutes. Whether any deployment is offered it is the checkbox below — a build that is not published is downloadable by version number, so you can install it on a box of ours and look at it first.

Loading…

Withdrawing stops a release being offered without deleting it — a version history with holes in it is worse than one showing a build that was pulled. Artifacts stay downloadable so an existing box can still be rebuilt onto that version.

Loading…

A re-install and a rollback can only reach a version whose bytes still exist, so this is what bounds how far back either can go. The newest few published releases are kept, and so is any version an install has reported running, however old — a client who never updates is exactly the one most likely to need a rebuild. Deleting is deliberately a manual aws s3 rm, not a button.

Loading…

One row per machine, not per customer. A licence is a file and copies of it all verify, so this is the only place a shared licence becomes visible — the count comes from the install identity each deployment generates for itself. Silent for more than 45 days and an install stops counting as live.

Loading…

Loading…

Loading…

Everyone here has the same access — there is one role, and any account can add another. An account can only be closed by whoever is signed into it, so removing someone who has left is a host command (./manage.py admin remove --email …) rather than a button. The last account cannot be closed: a Nerve with no admin can neither issue nor revoke.

Loading…

Removes your login permanently and signs you out. Clients, licences and issued keys are untouched — they belong to Nerve, not to you. This only works on your own account, and not if yours is the last one.