Karl is a company born with a strong mission and defined targets. We are aware that to accomplish the mission and fullfill all programs, good intentions, skills and commitment are indispensable requirement but not enough; a straight and defined approach is needed. That’s why we had care to build a solid philosophy that inspires our research and development activities.
In 2 words with our solutions we pursue:
Karl solutions are oriented to gain flexibility and scalability in IT infrastructures. We are obsessed by efficiency and we are committed to find all possible ways to optimize dynamically the use of resources. In a world like the IT that is quickly moving to an “As a Service” model the capability of managing resources is a key factor with impact on costs, productivity and sustainability. Taking only what is strictly necessary on real time basis gives benefit to the organizations in terms of financial costs and to the planet in terms of environmental costs. This concepts, and the commitment to put them in practice leaded us in conceiving our technology and are still guiding us in developing usable solution on that.
When a Karl infrastructure is up and running each pod will be able to work using central nodes resources and taking only what the current real time processes need.
- Each single operator endpoint needs very few local resources. A raspberry py connected to a screen and a network is enough;
- If we assume that we have 5 operators currently working in a Karl infrastructure: 4 are involved in ordinary word processing activities and 1 is involved in rendering. The single endpoint involved in rendering will take all the available resources with the exception of the few needed by the other 4 operator activities.
This is the second topic of our Philosophy. Security is crucial to any IT infrastructure and we developed our solution taking it seriously in account.
When the customer calls up any type of desktop or web application, he establishes an RDP connection to a POD that was generated from scratch and which uses a ephemeral disc or a disc which through the copy on write technology does not keep any type of modification made on it, does not occupy space. At this point, two paradoxes arise:
- Let's assume that an attacker manages to get to the POD and install a ramsonware, it wills imply been enough to click on the reboot button of the machine to make it disappear in the event horizon with its ramsonware.
- The operator is working and needs to save data. Our technology has no impact on this part as the persistent and mapped part for the user according to the profile.
We specify that the recall time preparing and putting online a KARL POD fully configured to work is equal to 53 seconds, the disappearance time of the POD is equal to 6 .