Our History :
By early 2010 Hani the founder of servaRICA was working on a website project that was supposed to be called postaRICA. when that project
code reached maturity level we started looking for hosting provider to host the new project. We were disappointed as at that time we couldnt find a
fully owned and operated Canadian host that is cheap (there where few options but they were all expensive) and since the project was server
intensive we had to find a solution .
We decided instead of going through hosts we can buy the hardware , colocate it and run our application from it , that solution seems significantly
cheaper than renting servers from pure Canadian hosts at that time .
Since in colocation you pay for electricty and space it made sense to go with the biggest server we can get as regardless of how beefy the server
you pay the same.
So we got our fist server which is an AMD Optron server with 24 cores and 128GB of ram .(at that time this is considered very big server)
by the time all of this happened it was clear that the origrinal project that we bought the server for was not ready for market (mainly because we
were late at that time and the idea was implemented partially somewhere else)
That shifted our attention to resolve the same issue we faced which is having a Canadian host with affordable price . At this moment we decided
to start web hosting company and servaRICA was born.
Why we named it servaRICA :
the name was choosen while in brainstorming session and we were looking for name that is musical and related to the field of webhosting. We got
alot of name suggestions untill one of us came with the idea of using the same name as the original project replacing the first part of it. So
postaRICA became servaRICA .
later actually it was suggested to change the name to serverI.CA or servarI.CA but at that time servarica was known what do you think ?
The automation issue:
Before start selling we faced the issue of automation , as we needed to keep everything automated as much as possible in order to decrease
human manual tasks.
while at that time there was some modules and tools to automate the VM lifecycle most of them where either not secure or too much restrictive
so we decided to build our own automation software. the first step we bought a small company that already did something like that. the code was
very bad but was doing the job.
within 2 months the code was completely rewritten to acceptable standards . this first module was working with xen OSS not xenserver.
although it was commercial module when we bought the company we didnt sell much of it (this module will be legacy later after we will develop
xenica for xenserver)
Xenica was born :
we started to grow and with time it was clear that OSS xen is too open and you need alot of automation to make it work and we needed
something with more stable working api.
based on that we moved to xenserver and started experimenting with it and it looked great,
then we rewrote the OSS xen module to deal with xenserver and thats how xenica was born (the name was different at that time)
servaRICA has gone through multi expansion phases , from having single server to multi servers all high in ram (each 256GB ram) to multi racks
we started using completely our uplink provider network and with time we had our own routers and our own ASN? and started to have multi