Can you explain why you are concerned with the usage of AGPL? Are you hoping to make a closed-source hosted fork eventually?
This can get very copy-left philosophical very quickly, so I'll be brief. For transit technology, especially if adoption matters, the less a license infects downstream projects the better for ecosystem growth. For example, I have an open source Tor library that is MIT licensed and it statically links Tor. I want the world to use my library, commercial/closed and open alike. I would never be able to do that with Orchid and therefore would not touch the tech. Make what you build on your network AGPL, but the underpinnings themselves should be as restrictionless as possible. These are my opinions and I understand the other opinion of "if you want the right to use our stuff, you have to abide by our openness rules on your stuff" but just know that you are trading adoption for principles.
In case it helps immediately clarify: you absolutely will be able to use the Orchid platform to build commercial, closed source distributed, semi-distributed, and even centralized applications.
For philosophical background on this, I encourage reading the position of Richard Stallman on why the Ogg Vorbis library should not be licensed under GPL. Our mission (to decentralize software and communication) causes similar quirks.
https://lwn.net/2001/0301/a/rms-ov-license.php3
(Exactly what the boundaries are on the components and under what license they will be released is thereby not yet finalized as we continue to work on architecture, but there are at least a couple things we are building that will seriously be released under 0-BSD.)
