Sugarizer is distributed in the form of 3 components:
Sugarizer Thin Client is Sugarizer in a browser. Sugarizer Thin Client doesn't need any installation on the device but requires permanent access to a Sugarizer Server.
Sugarizer Client is Sugarizer installed locally on the device so it does not require any access to the Server - it works stand-alone. Server access could be required only when it needs network features.
Sugarizer Server is the back-end for network features of Sugarizer. It means: allow deployment of Sugarizer on a local server, for example on a school server, so expose locally Thin Client (without Internet access). Sugarizer Server can also be used to provide collaboration features for Client and Thin Client on the network. Sugarizer Server could be deployed on any computer with Apache2, Node.js, and MongoDB.
A test Sugarizer server instance is accessible here.