Kin Browser
Build consoleOverview
Two-factor sign-in is required: add a passkey or the authenticator app under Security before anything else.
What is live
Last 30 days
How a release goes
- Build and upload:
node scripts/release.mjs, thenscripts/deploy-site.sh s3. The version appears under Builds. - New release: pick the build, the channel, the features and the packages, check, release.
- Machines on that channel take it within a day; on stable, the pricing and download pages show it at once.
- Old builds: delete them under Builds, or let the retention rule do it.
- 1 Build
- 2 Channel
- 3 Features
- 4 Packages
- 5 Check and release
Which build?
The builds in the release bucket, newest first.
Which channel?
A machine on an older build has only Lite's features, whatever its licence, until it updates. Builds before 1.6 have no licensing at all and cannot be changed; they are told to update.Which features does it ship?
ship: in the packages that include it. hidden: only for licences that name it (early access). hold: off for everyone in this release. Starts from what the channel has now.
Which packages go out?
Edit packages under Packages. The free one is what machines without a licence get.
Check, then release
The pricing page after this release (stable)
Builds in the release bucket
Keep or delete old builds
A build that is released on a channel is never deleted, nor are the newest few.
On each channel now
Invitations to beta and alpha
Make invitation keys for testers. A tester types one in Kin Browser's Settings, where licence keys go, and gets that channel's builds. One machine per key. Back to stable in their Settings returns them to the stable release, with the edition their licence gives.
History
People who downloaded
Everyone who gave an email on kinbrowser.com's download form, newest first. Market only to those who agreed to hear from us (Agreed): the mailing-list export has only them, and each email we send carries their unsubscribe link. Downloads from app updates and links shared directly carry no email, so they are counted on Downloads, not listed here.
Per day
By version
By platform
By country
By source
By campaign
People who downloaded
Their emails, names and companies are on the People page.
Latest from the form
Packages
A package is a set of features. One must be free (what machines without a licence have). Advanced packages show "Contact us" instead of a price. Changes go out with the next release.
Package
Sold online
Features
Issue a licence
More options: early access, air-gapped machines, a note
Make licence keys
Keys like KIN-XXXXX-XXXXX-XXXXX-XXXXX, for Mac, Windows and Linux. Each works on one machine: the first that uses it (kin-browser licence add KEY, or Settings in Kin Browser). Free its seat below to move it.
Licensed machines
Every machine using a licence: what it said about itself at activation and at its latest check, and from where.
Licences
Upgrade requests
From the Upgrade button in Kin Browser's Grid. Issue a licence under Licences, then mark it done.
Online orders
Coupons
A percentage off an online purchase, or a longer trial (kin-browser trial start --code CODE).
Machines using Kin Browser
From each machine's daily check (since 1.8, a short hash of its id, never the id). Earlier builds are counted by version only.
Per day
By version
By edition
By platform
Passkeys
Two-factor sign-in (authenticator app)
Backups
Connected services
Keys are kept encrypted in the console's data, and never shown again once saved.
Audit log
Tickets
Open merge requests
Add a user
owner: everything, and the users, connected services and security. admin: builds, releases, packages, licences, sales. viewer: sees everything, changes nothing. Admins sign in from the addresses the console allows (KIN_BUILD_ADMIN_IPS).
Users
Trials
One step up from what a machine has: Lite may try Pro, Pro may try Premium. Ultra is by purchase only, and Lite cannot try Premium directly. A Pro machine's licence comes back when its Premium trial ends.
The public key every build checks against: