Skip to main content


Polykey's roadmap revolves around Polykey's 2 core concepts:

  • Secret Management Workflow
  • Decentralized Trust

Secret Management Workflow

  • Gestalt Sync
  • CQRS to GUI - end to end reactive architecture
  • Schemas File/Vault - impacts GUI/CLI/Vault History.. etc
  • Vault Automation
  • Vault Splitting and Joining
  • Vault History Management
  • Enterprise Audit Logging
  • Enterprise Policy Control with Signing Authenticity - ask enterprise PK node to sign actions to control what is allowed
  • M1 Mac Compatibility
  • Mobile Deployment
  • OAuth2 Integration with token management for API clients
  • CA to deal with PKI in general -
  • Expose crypto utilities for general use - replacing PGP -
  • Notification Delay-Tolerant & Store and Forward Protocol - Integrate into SMTP
  • Browser Extension - low priority because if PK sits in the middle between password management and machine secrets, then password management is well done by other companies and organisations, and this reduces the importance of GRPC web gateway

More usecases:

Make sure to classify by "local" to "global" spectrum. How significant is this usecase in these dimensions?

  • Market size - number of users
  • Market size - average size of each user (in terms of financial impact)
  • How easy it is to onboard, does it affect 1 person or the entire company. At what point is the scale-breakeven point? Is it too much overhead for 1 person but beneficial if there is an entire system built around it?
  • Dedicated single computer usage of multiple computer usage?
  • Is this a single-tool usecase or a multi-tool infrastructure usecase?


Employees, BYOD, Device Provisioning

Developer Workflow

DevOps and SSH and Configuration Management

DevOps and Microservices

[[/images/nsa google cloud exploitation.webp]]

These things will need to be read by people writing usecases.

Decentralized Trust

Invitation codes from backchannel can be used in our system for inviting to Polykey gestalt, or when sharing secrets directly via QR codes.

Creating Dependency Diagrams:

arkit ./src -o ./media/dependencies.png
typedoc --media ./media

The typedoc enables the ability to embed media that will be rendered by documentation. See:

In the comments we can write: media://file.jpg.


This can be useful for showcasing benchmarks which are written with JSON or CSV or HTML.