⚠️ Fluidkeys is no longer maintained. This page is kept for posterity.
25 January 2019
Protecting liberty by simplifying security
Recap: We’re building Fluidkeys to help teams safeguard their source code and protect sensitive data.
Hello, it’s great to be back!
We’ve had a stab at explaining how Fluidkeys will actually work for your teams. We’re really narrowly targetting our niche: small to medium engineering teams. We’re about to show how it looks (as a command line app) and how it works. I’m really pleased with what we’ve got done, take a look.
We’ll be testing this out with prospective users next week, seeing whether it’s getting closer to being something valuable enough to pay for!
Speaking of which…
This week we got our first paying subscriber. Well, in principle. Now the small matter of delivering the product, figuring out how to take payment, and incorporate. Lean! It’s great to have this, less so for the finances at this stage, but more as validation that we’re moving in the right direction.
Who knows, at somepoint the dashboard might stop shouting about how unsustainable our business is! 🔮
In light of the sale and our narrower focus on teams, we’ve realised to finish the product we need someway for admins to define who’s in their team. We’ve prompted this to be the next major release on our roadmap. We reckon this will be a simple text file listing team-mates and their fingerprints, signed by the team admin. On Thursday we worked up an idea that an administrator could also connect Github or Bitbucket, and pull a list of their team from there (we could also check if they’ve already got PGP keys). We then started sketching a flow of how the whole invite flow would work, along with the authentication.
It’s too early to show this here now, but you expect more on that next week.
Thanks for reading.
All feedback is welcome, pop us an email to firstname.lastname@example.org