How much discount for whole year of contract ?
We offer 22% discount for a twelve-month billing period. BTW here's a review from one of our clients:
Quote
Well, I've been experiencing this hoster for some time now.
There are good reasons why one would pay much more for the same server than at other hosters.
One of these reasons is the included remote administration console which allows direct console access to the server starting with the BIOS menü.
This is particularly useful if you screwed up with your firewall, lost your root user password or have any other need to access the console rather than ssh (local login, single-user mode, boot loader menu etc.).
There is also a touch of knowlegde to expect since this hoster is the first ever I see to not allow remote root login by default and provide a less-privileged user account.
I know this is not much work to do, but it tells the customer that there is a certain understanding of UNIX best-practices and basic security approaches.
As for the protection included, I can tell that the server I am working on has never been totally cut from the network.
I have multiple IP addresses to separate public services from management access and even under heavy attacks the management SSH access always worked.
There was one exception when I messed up with IPFW which caused it to crash - but then again the remote console was very helpful to fix this without any support needed.
I do understand - and anyone else should, too - that a general-purpose protection cannot defeat all attacks.
When it comes to application-specific flooding you simply cannot reliably detect and block it from the perspective of the hoster because of the lack of knowledge about which packets might be legit and which not.
About performance there is nothing to complain.
The server has been stable for about 4 weeks without any downtime, crash, panic or similar.
The Intel CPU easily powers several FreeBSD jails with over 16 running daemons plus a MySQL backend (usually 75% idle under heavy load).
My MySQL server uses InnoDB with buffer caching which seems to work great.
Disk write operations under heavy load are slow (in terms of a few milliseconds) from time to time due to the fact that I did not decide for SSD storage but standard SATA2 hard disks.
Lags occured when inserting millions of rows per hour into a heavily indexed log table but that is understandable and was fixed after changing the logging verbosity of my application to a sane value.
The support is generally helpful. I can understand that it might take an hour for a response to a ticket opened at 4:00 in the night. At daytime, responses usually come in faster.
I hope I can give anyone interested a good first insight.
There are good reasons why one would pay much more for the same server than at other hosters.
One of these reasons is the included remote administration console which allows direct console access to the server starting with the BIOS menü.
This is particularly useful if you screwed up with your firewall, lost your root user password or have any other need to access the console rather than ssh (local login, single-user mode, boot loader menu etc.).
There is also a touch of knowlegde to expect since this hoster is the first ever I see to not allow remote root login by default and provide a less-privileged user account.
I know this is not much work to do, but it tells the customer that there is a certain understanding of UNIX best-practices and basic security approaches.
As for the protection included, I can tell that the server I am working on has never been totally cut from the network.
I have multiple IP addresses to separate public services from management access and even under heavy attacks the management SSH access always worked.
There was one exception when I messed up with IPFW which caused it to crash - but then again the remote console was very helpful to fix this without any support needed.
I do understand - and anyone else should, too - that a general-purpose protection cannot defeat all attacks.
When it comes to application-specific flooding you simply cannot reliably detect and block it from the perspective of the hoster because of the lack of knowledge about which packets might be legit and which not.
About performance there is nothing to complain.
The server has been stable for about 4 weeks without any downtime, crash, panic or similar.
The Intel CPU easily powers several FreeBSD jails with over 16 running daemons plus a MySQL backend (usually 75% idle under heavy load).
My MySQL server uses InnoDB with buffer caching which seems to work great.
Disk write operations under heavy load are slow (in terms of a few milliseconds) from time to time due to the fact that I did not decide for SSD storage but standard SATA2 hard disks.
Lags occured when inserting millions of rows per hour into a heavily indexed log table but that is understandable and was fixed after changing the logging verbosity of my application to a sane value.
The support is generally helpful. I can understand that it might take an hour for a response to a ticket opened at 4:00 in the night. At daytime, responses usually come in faster.
I hope I can give anyone interested a good first insight.
