Hey everyone, it's been a while. To my fellow Americans, hope you had a pleasant Memorial Day weekend!
The Project
One of the biggest reasons I haven't updated more often is that prior to last week, not much has happened. Lots of design work, back-and-forths, and all the other joys of software development. Seems like a waste of all our time to post weekly saying "hey, nothing's changed". Well, I'm happy to announce that the design phase is now complete. Velvetech (our development partner) produced a final design spec, and I approved it last night. I've signed off on the first portion of development, and am waiting for a final SoW (Statement of Work) and invoice, which I was told will be provided this afternoon. After that, just requires my signature and 50% of the payment up front, and we're off!
Before I get to the details, I need to make a small comment. I don't want to give specifics on what exactly our product is going to be like, the exact technology stack being used, etc in a public forum. The sole reason for that is that I know our competitors read this regularly, and I need to keep them from "stealing" the specifics of our ideas. There's a European company specifically that has been particularly ... un-subtle in their attempts to steal proprietary info, and has been equally obvious in their attempts to discredit us online after I called them out on it. You know who you are.
Because of that, I can't give out too much information, but here's what I'm more than happy to do instead. If you have invested in Keyqo and want to review the full design document/jump on a call with me/whatever, just drop me an email. I'll have you sign a non-disclosure agreement, then I'll give you access to any details you would like. That way, you can see the details of our progress, without me having to deal with theft of proprietary info.
For the rest, here's a quick overview of the first product we're pushing out. For this first phase, we are developing a security monitoring tool, which tracks the transfer of sensitive data within and out of a given clinic's network. We have a small "agent" that gets installed on each machine on the network. It monitors all traffic coming in and out of that machine. It interfaces with an intrusion-detection system (IDS), which tells it certain "patterns" to look for, which indicate patient data is being compromised. If those patterns are detected by the agent, it will report to a central server with what it found. The server will take those logs, encrypt them, and store the information on a private blockchain (this is a requirement so we're HIPAA-compliant). So no matter if the machine is compromised by an attacker, the logs can never be modified. There's a dashboard/admin console that the end user utilizes to see any alerts or indicators of compromise, as well as separate tools for storing customer data, reporting, billing, and all the other fun stuff. If you've heard of security products called AlienVault or Cylance, conceptually, they're very similar. Beyond that, this will be cloud-based (a SaaS product), and we'd charge an customer per-dervice, per-month.
The first part to be completed is the IDS, data storage, and blockchain components. I'm still waiting on a final timeline - that will come with the SoW. The initial estimate I can give is about two months. Velvetech is very good about keeping on schedule, so I don't expect any delays at this time. The frontend/dashboard and agents will come after that's finished.
That's basically all the data I'm able to give at this point. If you have general questions, let me know. If you want specifics, just follow the process I outlined above.
Other Stuff
Some people have reached out, asking whether the Telegram group is still active. It's not. After the crowdsale ended, many of the people who were actually interested in what we're doing moved here to Steemit, email, or Twitter. That left the trolls and people wanting to sell us something. Got tired of banning them, so it's shut down. If there's enough demand, I'll create an invite-only group again. In the meantime, Steemit and Twitter are the best places to keep up to date on Keyqo the company. If you need it, I've also placed my personal contact info at the bottom of this article. I reply best to email and LinkedIn, but all of them work.
We're also redesigning our website, making it more geared towards sales of our products rather than for investors. I'm sure you'll have noticed I haven't really touched the old one in a long time. There's a dead link or two and some out-of-date info there, so I intend to eventually shut it down and merge the useful content to the new site. It'll be a while before the new site is live though; I had to prioritize the product with the funding we have left. I have no ETA, but it will be live when we start selling our product. Fingers crossed that will be by the middle of Q4?
A minor point on the SEC. We had an investor reach out last week, concerned about the harsher stance the SEC has taken on ICOs. He was worried that we were in legal trouble, and that's why we haven't abided by the timeline on the old website. That is not the case. I, Mark Rudnitsky, CEO of HealthHeart (D/B/A Keyqo), testify in writing that to the best of my knowledge, we are not in any sort of legal trouble, investigation, or anything similar. To be honest, I'm slightly confused as to why we would ever be. As a reminder, last year, we also had a legal opinion drawn up and published at the top of the website, which states we are abiding by all US securities laws. I'll keep you anonymous, but thanks for sharing your concern; I appreciate you caring enough to ask.
That's it for now. Take care everyone, and talk to you next month.
Thanks,
-Mark
Mark Rudnitsky
Chief Executive Officer
KEYQO (formerly HealthHeart)
Telegram: @keewenaw
Steemit: https://steemit.com/@keewenaw
Twitter: https://twitter.com/keewenaw
LinkedIn: https://www.linkedin.com/in/mrudnitsky/
Facebook: https://www.facebook.com/healthheartllc/
Email: hello [at] healthheart.io