Live data from Hacker News

Launch YC S21: Meet the Batch, Thread #6

news.ycombinator.com

111–120 of 120 posts

Re: Launch YC S21: Meet the Batch, Thread #6

#111

This is Chris and Robert from HeyCharge ( https://heycharge.io/ ). We're developing low-cost EV charging for indoor environments like underground parking garages. Current indoor EV chargers are expensive to buy, install, and operate, especially because they need internet connections and cloud-based backends. They're also unreliable, because even if the charger's internet connection works, the user might not have one…

> We only provide a replacement token to the user in return for them bringing a complete charge session report. What prevents the user from reusing the token? Does the charger keep some state about previously seen tokens?

Exactly. This is something we can do because we operate semi-private (as opposed to public) infrastructure, and over its lifetime each charger will see a (relatively) small number of users.

Re: Launch YC S21: Meet the Batch, Thread #6

#112

This is Chris and Robert from HeyCharge ( https://heycharge.io/ ). We're developing low-cost EV charging for indoor environments like underground parking garages. Current indoor EV chargers are expensive to buy, install, and operate, especially because they need internet connections and cloud-based backends. They're also unreliable, because even if the charger's internet connection works, the user might not have one…

Why not just use a laundry card type system? Seems like a solution looking for a problem.

Replacing the RFID card is just one (small) benefit of our approach. The bigger ones are:

1. Eliminating the internet connection lowers both installation cost and setup complexity for the charger. The RFID card doesn't save you from having to take these (expensive) steps when setting up a site, and to pay for the connection on an ongoing basis.

2. Once you eliminate the external variable of configuring a charger to use an internet connection and a backend, the setup flow becomes virtually a plug and play. This substantially improves scalability as we don't have to train dedicated installers. Any electrician who can read a wiring diagram can bring up a site. And, of course, this translates into lower costs for the user.

Of course you could have a disconnected charger using statically-configured RFID cars that doesn't require #1 and #2 above, but then you can't bill people for what they consume or centrally manage access. This is OK for some small sites, but isn't really a scalable solution.

Re: Launch YC S21: Meet the Batch, Thread #6

#113

Earlier quoted context omitted.

> We only provide a replacement token to the user in return for them bringing a complete charge session report. What prevents the user from reusing the token? Does the charger keep some state about previously seen tokens?

Exactly. This is something we can do because we operate semi-private (as opposed to public) infrastructure, and over its lifetime each charger will see a (relatively) small number of users.

I see. Then the expectation is that the user charges only at one charger, as otherwise a token might be reused at a different charger. Thanks, sounds interesting!

Re: Launch YC S21: Meet the Batch, Thread #6

#114
post #93

Earlier quoted context omitted.

Great questions! The hardest part was probably getting our initial customer. This is inherently sensitive company info, and getting the initial social proof & trust from a big name opened a lot of doors for others to trust us. We have about 60 agencies verified with us so far. What's interesting about this problem is that the company dictates how government agencies contact them. As a result, the moment our customers…

> the company dictates how government agencies contact them What mechanism governs this? Are you standing in as their registered agent? Politely asking agencies to follow your process and finding that they tend to be willing to do so? Something else?

Companies provide points of contact for these types of legal process to be served on them - it is akin to the registered agent process. Govt agencies do not have the authority to dictate how a company accepts this legal process, only that they comply with the legal order itself. As a result, govt agencies follow the methods of contact that a company provides, whether its a fax number, email address, mailing address, etc.

Agencies are willing to follow the process that a company lays out because it makes engaging with that company easier. It is not in an agency's interest to make the process difficult (i.e. demanding to use fax machines when a company already has a lawenforcment@company.com email set up).

Re: Launch YC S21: Meet the Batch, Thread #6

#115

This is Chris and Robert from HeyCharge ( https://heycharge.io/ ). We're developing low-cost EV charging for indoor environments like underground parking garages. Current indoor EV chargers are expensive to buy, install, and operate, especially because they need internet connections and cloud-based backends. They're also unreliable, because even if the charger's internet connection works, the user might not have one…

If you want to create a user-friendly experience, how about making it so that I just plug my car in and it charges?

No phones, no apps, no access cards. The charger recognizes my car, the car has the billing info, done.

Sigh.

It was such a massive ball drop when the plug standard insisted on having the plug + car detection of the plug being inserted work in all conditions, but then failed to account for the simple fact that billing also needs to be solved.

It's like they thought of it as someone inserting a gas nozzle, or that the electricity would be free.

And now we've rolled out how many of these?

Re: Launch YC S21: Meet the Batch, Thread #6

#116
post #115

This is Chris and Robert from HeyCharge ( https://heycharge.io/ ). We're developing low-cost EV charging for indoor environments like underground parking garages. Current indoor EV chargers are expensive to buy, install, and operate, especially because they need internet connections and cloud-based backends. They're also unreliable, because even if the charger's internet connection works, the user might not have one…

If you want to create a user-friendly experience, how about making it so that I just plug my car in and it charges? No phones, no apps, no access cards. The charger recognizes my car, the car has the billing info, done. Sigh. It was such a massive ball drop when the plug standard insisted on having the plug + car detection of the plug being inserted work in all conditions, but then failed to account for the simple fa…

We agree. :)

So far, only Tesla really supports this at scale (and unfortunately it's proprietary so we can't really use it).

However, the coming wave of EVs will finally support ISO15118, which is a global standard that brings this experience to any EV. We'll support it as soon as there's a meaningful population of vehicles out there with the car-side support. Come to our labs in a month or two for a preview ;)

Re: Launch YC S21: Meet the Batch, Thread #6

#117

Earlier quoted context omitted.

Exactly. This is something we can do because we operate semi-private (as opposed to public) infrastructure, and over its lifetime each charger will see a (relatively) small number of users.

I see. Then the expectation is that the user charges only at one charger, as otherwise a token might be reused at a different charger. Thanks, sounds interesting!

More or less. We expect our users to charge at a relatively small number of chargers (you might have, say, 10 shared chargers in some buildings), and likewise for chargers to see a relative small number of users over their lifetime. Hope you'll get a chance to use it in a building near you soon!

Re: Launch YC S21: Meet the Batch, Thread #6

#118
post #93

Earlier quoted context omitted.

Great questions! The hardest part was probably getting our initial customer. This is inherently sensitive company info, and getting the initial social proof & trust from a big name opened a lot of doors for others to trust us. We have about 60 agencies verified with us so far. What's interesting about this problem is that the company dictates how government agencies contact them. As a result, the moment our customers…

> As a result, the moment our customers adopt Kodex, they automatically pull in any government agency that wants to contact them. Am I reading this right: agencies aren't reaching out to companies because it's kinda hard to because every company has their own process? Or at least, agencies are slowed down by this fact? So, couldn't adopting your product be seen as a bad thing? If a company prefers noncompliance to go…

Thanks for the comment!

I see what you're saying, but I think there is a fundamental misunderstanding - Kodex was made to make things easy for the company, not the government. Agencies are never deterred from reaching out to companies because it's "kinda hard," nor because it's different for each company. It actually doesn't even slow them down - data requests are already growing ~25% YOY. Govt agencies get more and more resources to serve subpoenas, but companies are left to fend for themselves with an ever increasing volume. The moment a company receives a subpoena, the company is now legally obligated to respond in one way or another. The nuance is that you don't necessarily have to comply and provide data - the company can push back on the legality of subpoena, but it will still need to be addressed one way or another.

Sure, you can certainly choose noncompliance through bureaucratic friction but that doesn't eliminate your problem as a company, that actually only makes it more burdensome for your company. At some point you still have to address the subpoena.

When a company does not have an intake method for these types of legal inquiries, it only makes it harder on the company...not the agency. The agency will just send the inquiry to any publicly known address, email, etc. In one way or another, if they want to send you a subpoena, they will...aka making the process hard does not prevent them from reaching out to your company, it only makes it hard on your company.

I think a perfect example is Facebook. They built their own Law Enforcement Portal because 1. there was nothing like Kodex that they could buy, and 2. They understood that making the process easier for themselves greatly helped their company with cost of compliance, protecting user privacy, and pushing back on overly broad requests. Did the Facebook LE Portal make it easier for agencies to send them subpoenas? Sure. But it's not as if agencies wouldn't still be sending just as many subpoenas to Facebook if they hadn't built their LE portal...Facebook would still be getting them, it would just be that much harder for Facebook to manage them.

In regards to your example, I understand wanting to do your part to stand up to government overreach. The government is not infallible - they've been on the wrong side of history more than once.

I think the answer to standing up for these issues, is not to create more friction, but instead to facilitate a streamlined process of engaging with government agencies - so you (as a company) can more easily push back on the legality of a subpoena that you don't agree with, and also more easily assist in the very real instances of identifying victims, or subjects, that end up saving a life.

I think this subpoena process has become so sloppy and overwhelming that it is easy to forget that there are victims at the end of this transaction.

If there are subpoenas sent to you regarding a user on your wiki, wouldn't you want to have a clear understanding of what the government is looking at, and why? What threats are on your wiki? Wouldn't you want to easily be able to prioritize a case involving child exploitation, or self-harm, and help protect those users, while also having a better avenue to push back on requests you find to be unjust?

There is a lot that can be fixed in government. This process is one of them. The goal is not to "help the government do their job more easily"... making the process easier for the company, forces the government to do their job BETTER, and helps society move forward.

Re: Launch YC S21: Meet the Batch, Thread #6

#119
post #118

Earlier quoted context omitted.

> As a result, the moment our customers adopt Kodex, they automatically pull in any government agency that wants to contact them. Am I reading this right: agencies aren't reaching out to companies because it's kinda hard to because every company has their own process? Or at least, agencies are slowed down by this fact? So, couldn't adopting your product be seen as a bad thing? If a company prefers noncompliance to go…

Thanks for the comment! I see what you're saying, but I think there is a fundamental misunderstanding - Kodex was made to make things easy for the company, not the government. Agencies are never deterred from reaching out to companies because it's "kinda hard," nor because it's different for each company. It actually doesn't even slow them down - data requests are already growing ~25% YOY. Govt agencies get more and…

A relief to receive a response like this, thank you for taking the time to write it up! Sometimes I feel like the technology sector moves quickly without taking the time to consider the ethical implications of developing technology, and it seems to me that you have taken that time and have a good ethical basis for your business.

Best of luck!

Re: Launch YC S21: Meet the Batch, Thread #6

#120
post #5

Hey everyone! We’re Juliana and Robert, co-founders of Parallel Bio. We're improving drug discovery by replacing animal models, in the hope of making cures for humans, not mice. The biggest reason why 92% of new drugs fail is that drugs are currently discovered in mice, which are not realistic models of human disease but are used due to the challenges of working in humans. We've created a human ‘immune system in a di…

This is a moonshot if I ever saw one. Exciting stuff.

Does your system also have epithelial lining, with all of the components of innate immunity which integrate with the adaptive immune system?

The role of the nervous system is more and more recognized as being integrated within the immune system - is there any way you can somehow include that in your system as well in the future?

Post reply on HN