KeysFortress
Keyfortress is the new way of authorizing employees and machines at the same time.
Achievements
Team
Prototype
Users
Partners
Revenue
Investors
What we offer
Equal shares for all core members
Target group
Small to Enterprise level customers, interested in their digital privacy.
Challenges
I wont lie to there will be many challenges ahead, it's a massive initiative to come up with a system that can both secure unix based servers and employee credentials.
The first challenge that i see myself is the lack of business skills, i am developer and managing marketing or business related topics will be a new path that i will have to walk trough with your help, but i am stubborn, and creative so i am sure that we will cross the bridge together.
Our Story
During my short humble career of just 12 years in the industry at every company I've had the pleasure to work at, regardless if it's a big company or a small startup, the on-boarding process was always the same, chit chat with the team lead or the founder and then i send him my ssh key and i get access to wherever i need.
In most places everyone had access to everything when it came down to the server side and in certain cases ( I am really sorry Dean) some people had more privileges that they would ever need and that led to around 50 customer facing apps to get updated to our latest framework release despite running legacy code that is dependent on v1.2.
Access to the company accounts regardless if it was slack, teams, or matrix has always been trough email or other chat based message that just delivered the password in plain text, i am not going to go over why this is scary, just going to say that every process has access to the system clipboard, so not a good way to share credentials.
If you did read the story, now you know why we need a unified system that can control both the servers and the employee credentials and why it's actually a good product, i hope that you join me and together we can make something awesome and at the same time really good for the other people in the industry.
In most places everyone had access to everything when it came down to the server side and in certain cases ( I am really sorry Dean) some people had more privileges that they would ever need and that led to around 50 customer facing apps to get updated to our latest framework release despite running legacy code that is dependent on v1.2.
Access to the company accounts regardless if it was slack, teams, or matrix has always been trough email or other chat based message that just delivered the password in plain text, i am not going to go over why this is scary, just going to say that every process has access to the system clipboard, so not a good way to share credentials.
If you did read the story, now you know why we need a unified system that can control both the servers and the employee credentials and why it's actually a good product, i hope that you join me and together we can make something awesome and at the same time really good for the other people in the industry.
Team
