A nearline private server ("NPS") is our spin on web hosting: account compartmentalization on an single operating system. Each account is assigned to a container on a server. Resources in each container are localized to that container. No container may overlap another container and each container is visible only to itself, which means your files remain secure and your site runs at optimal speed.
We take care of managing the server. You take care of managing your site. With an NPS account, you have full access to the hardware, all 72 GB of RAM and full access to all 16 cores. A virtual private server ("VPS") requires complicated system administration to maintain. Both isolate from neighboring accounts, but only an NPS by Apis Networks comes ready-to-host – like shared hosting – but without the inherent insecurities.
This is a standard feature powering every hosting account.
Machines only contain 2-3 virtualized hosts minimizing the possibility of resource contention.
Every account co-exists in the same user space thereby reducing the number of servers and instances to individually monitor.
Every account is compartmentalized into its own pivot-root. Every process that executes within an account may only access files within its pivot-root.
Every account shares a base read-only layer. Files can be injected into this base layer to propagate to all accounts. Adding new Ruby interpreters is a cinche!
A server split n-ways only requires 1 FTP server, 1 mail server, and 1 HTTP server cutting down on wasteful duplication of system services.
With hardware pooled among accounts, our clients can withstand traffic surges without compromising performance.
NPS blends the best of both worlds: bare metal capability as with shared hosting, without the awful overcommits and resource starvation that is synonymous with it, and account isolation as with VPS. All NPS servers are managed by us and undergo continuous monitoring. You worry about your web site's details, like what its background color will be.
|Root access permits access to modify all files and install software in system locations.|
|An immutable filesystem protects critical files from being accidentally deleted.|
|Every account operates independent of each other. Users can't view other processes by other users.|
|Every account has a filesystem visible only to its account.|
|All hardware on the server can be used in times of stress with NPS & shared hosting. VPS performance varies by cost. NPS utilizes resource enforcement to prevent overmonopolization of resources by "noisy neighbors".|
|VPS platforms burn precious CPU and memory running auxiliary system services, like syslogd and a mail server. Shared platforms provide fewer features, but cram more accounts onto a server.|
|Managed System Administration|
|NPS & shared hosting take care of configuring the server and keeping everything up-to-date; you just host. VPS requires documentation to get up and running.|
|Servers are locked down and secured against brute-force attacks. VPS requires some system administration experience to adequately lock-down (especially brute-force deterrents!)|
|Run daemons that listen on ports, like MongoDB, Redis, and Memcached.|
|PHP, MySQL, PostgreSQL, Ruby, Python, and Node.js are configured and ready to use without following cumbersome, outdated documentation.|