Products

Built for a single purpose, a server where nothing unnecessary runs

ParaBox is a Debian/Ubuntu-based Linux server platform that we set up for a specific purpose. It is not a ready-made image: whatever job the server will do, it is configured from scratch for that, and unnecessary services are never installed. This means few components, a small attack surface and a more predictable system. It runs on Proxmox VE in isolated virtual machines with dedicated resources.

Purpose-built configuration Hardened installation Snapshot and off-site backup On Proxmox VE

Approach

Purpose-built setup instead of a ready-made image

A general-purpose server does every job a little and none completely. In ParaBox the server's task is clear from the start and the setup is shaped around it.

Web server

A hosting server configured with the web engine and PHP version best suited to your application, including performance tuning.

Email server

Corporate mail infrastructure, together with spam and virus filtering, archiving and signature layers.

Database server

A database system configured for your application's load, with backups planned.

Custom application server

A system prepared to run an in-house application or a special service.

Infrastructure

The standard parts of the setup

The following are in every ParaBox installation; they are not sold as add-on options.

Hardening

Unnecessary services are not installed, open ports are restricted, and the firewall and access rules are defined from the start.

Backup and disaster recovery

Regular snapshots and backups do not stay only local; they are also stored on our central off-site backup infrastructure.

Isolation

Each system runs in a separate virtual machine on Proxmox VE; resources are separated at the hardware level.

Central monitoring

Resource usage, service status and availability are monitored centrally; we are notified in case of anomalies.

Update management

Security updates are applied in a planned way; a snapshot is taken before critical updates.

Documentation

At the end of the setup, the system's configuration is delivered in writing; knowledge does not stay with a single person.

How We Work

Not a call center, the team that does the work

We are not a provider that sells mass packages. We work with a small number of organizations, getting to know their setup. The feedback we hear most is this: "When we call, we reach the technical team without waiting."

You reach the technical team directly

There is no ticket queue, no operator reading from a script, no "I passed it on to the relevant department" answer. You reach the colleague who knows the subject and talk through the solution with them.

A team that knows your organization

You don't have to explain your system from scratch every time. Whoever set up your server is the one who looks at it when a problem occurs, and they approach it knowing its history.

Not a ready-made package, a setup built around you

If your need doesn't fit a standard package, we change the setup, not the package. As a team that has been in the field for years, we design the solution around your process.

Help

Frequently asked questions

Will the server sit in our data center or yours?

Both are possible. We usually host it on our infrastructure; if your organization has its own data center or virtualization environment, the installation can be done there too. Where it will sit is decided together according to your data residency and access requirements.

Will we have root access?

For managed installations, we remain responsible for the system and keep access controlled. If your team needs direct access, we define and document the authorization model from the outset.

How long does it take to restore from backup?

Restoring from a snapshot is generally quick; a full restore from an off-site backup depends on the data size. For critical systems we discuss the target time up front and design the setup accordingly.

Can our existing server be migrated to ParaBox?

In most cases, yes. We first review the existing system; applications, data and configuration are moved to the new system and tested, then a planned cutover is made. The cutover time is whenever you find suitable.

Can we increase resources later?

Yes. Virtual machine resources (processor, memory, disk) can be increased as needs grow. Because we monitor resource usage, we usually let you know in advance when you approach the limit.

Let's talk about what the server will do

Which application, how much load, which access needs? Let's work out the scope of the setup together.

Write to Us