Ask HN: Should investors have access to source code and servers?
I've seen opinions go both directions on this topic. I'm very curious to hear HN's input. It's a situation I'm dealing with right now.
In a standard venture capital investment arrangement, should an investor be allowed to have a copy of the source code to a product (and or have open access to all code), and root access to the servers the business operates (whether owned or rented)?
I think primarily this is an arrangement to be settled between the investor and the company, but I'm interested in what's considered normal practice.
(
9 comments
| 7 points
| on HN
)
Codebase, maybe; but that's because not-all projects have a convincing reason to keep the codebase private in the first place. (Think single-page applications where all the code is available to the browser anyway). If your competitive edge is based on the particular construction of your codebase, or you have some secret-sauce in there that is ahead of it's time (and not just standard-practice kind of code) then you should treat that codebase like a bank vault.
I'd err on the side of caution. Give speedy curated walkthroughs of the codebase (so they can see it and do some due-diligence to make sure your engineers are competent), then lock them back out.
But what is an "investor" in this case? Can someone buy a 1% equity and then walk away with your source code potentially worth significantly more than that? That isn't rational.
If they /buy/ the company they get access to the source code naturally but why would an investor? An investor is just staking capital for the chance that the company's venture will do well. SOME might be investing for the chance that the IP is worth a lot, and in that specific circumstance it might be rational to give them limited access to the IP (so they can verify claims).
However I'd never let an investor walk off site with the code or email them a copy of it to do with as they will. I would let them sit in a room and read through the code or even have people on their behalf do the same. I'd also do a code-review style thing where we talk through it together so they better understand the IP/project. Naturally this would all come with appropriate non-compete/NDA.
As to root access? HELL NO, that's insane. I don't even think programmers should have root on production servers let alone fucking investors. The only people who should have root are your system engineers (for maintenance) and your deployment lead (so they can pull from the master and deploy to prod' after it has hit test).
The investor in question is prominent, invests in a lot of companies, and owns let's say 20% of the company. I own a controlling interest in the business as the founder.
I've been out of contact lately with the investor, working on readying a product. The concern was about me as it turns out, due to the lack of communication. I play an integral role in the company and the product is my vision.
The investor had been pretty chill about requiring constant updates, and I got too relaxed about keeping that communication line where it should be. This is something at times I'm bad at, I have a tendency to bury myself in something and not come up for air for a long time.
So the request for source / server access was, in the investor's words, a precaution. Without actually knowing something was wrong, I don't know that it exactly justifies an investor having access to those assets directly, but it sheds light on the thinking. Clearly I need to re-instill confidence there.
Root access: never. What would be the use case?
Sad that some investors are so manipulative.