Managed Private Environments (Dedicated Compute)

Some organizations need stronger isolation than the standard shared platform provides. A Managed Private Environment — the customer-facing name for the service also referred to as Dedicated Compute — is Everabyte’s optional managed isolation service for eligible EverBlaze companies. This article explains what is isolated, what remains shared, what Everabyte manages, and how to request the option.

In short

A Managed Private Environment is a dedicated application environment with an isolated PostgreSQL instance, fully managed by Everabyte. It is optional on EverBlaze Start and Scale, and can be included in EverBlaze Ultra enterprise configurations as part of the final agreement. It is requested through sales or support — there is no self-service activation, and availability is confirmed case by case.

What is isolated

By default, eligible companies use Everabyte’s shared application infrastructure. Their application data remains logically separated from other companies through the platform’s tenant isolation model, on centrally operated, self-hosted PostgreSQL. Shared does not mean public or unprotected: the platform applies the same encryption, access control and monitoring discipline described in Security at Everabyte.

When a company purchases the Managed Private Environment option:

• Everabyte provisions a dedicated virtual machine for that company;
• The company’s EverBox Business application runs inside that isolated VM environment;
• The company receives its own isolated PostgreSQL instance, hosted within the same dedicated environment with its own persistent database storage;
• Its application services and database are separated from the application instances and databases of other companies;
• CPU and RAM resources (Dedicated Compute) are allocated according to the contracted configuration.

The underlying infrastructure may still be hosted on shared bare-metal hardware. A Managed Private Environment is not a promise of physical server exclusivity unless that is explicitly contracted.

PostgreSQL architecture

Everabyte uses self-hosted PostgreSQL, operated entirely by Everabyte. There are two models:

• Shared environment: centrally managed PostgreSQL with logical tenant isolation between companies;
• Managed Private Environment: a separate PostgreSQL instance for the company, hosted within that company’s isolated application environment.

An isolated PostgreSQL instance does not by itself provide high availability, separate physical hardware or an independent disaster recovery setup — those depend on the contracted service, not on isolation.

File storage objects (S3-style storage and buckets) remain on Everabyte’s separate object-storage architecture. Objects are not stored inside the application VM or the PostgreSQL instance, in either model.

Who manages the environment

Everabyte operates, secures, updates and monitors the environment: operating system maintenance, PostgreSQL operation, infrastructure security, updates and monitoring are our responsibility. Database backup management and restoration are part of the managed service for activated environments; the backup policy applied to your environment — frequency, retention, destination and restoration scope — is set out in your service agreement.

The customer accesses EverBox Business through its normal application interface. The customer does not receive root access, SSH access, hypervisor access or Proxmox administrative access.

What the environment hosts

The VM hosts the managed Everabyte application stack and approved platform components — it is not a general-purpose VPS. Customers cannot run arbitrary applications, custom operating systems or unrestricted workloads inside the environment. If you need custom integrations or processing, they are discussed and approved as part of the agreement (see White Label for custom functionality).

White Label and Managed Private Environments

White Label (branding, domain, support identity) and a Managed Private Environment are independent options. White Label does not require a private environment, and a private environment does not include White Label. Either can be arranged separately under the applicable agreement.

Network capacity

Network capacity is independent of Dedicated Compute:

• Standard Network Capacity — up to 1 Gbps shared network capacity, included at no additional network-capacity charge on eligible EverBlaze plans, whether or not a Managed Private Environment is purchased. It is a shared capacity ceiling, not a guaranteed sustained or dedicated throughput commitment.
• Enhanced Network Capacity — optional paid service, from 2 Gbps up to 100 Gbps, subject to technical feasibility, region, architecture and infrastructure availability. Pricing on request; not automatically activated and not guaranteed in every location or configuration.

Network capacity (Gbps) is the possible transfer speed. It is distinct from your monthly data transfer allowance (TB/month), from your storage allocation (TB) and from CDN — buying more network capacity does not increase any of them, and enhanced network capacity can be discussed without a private environment.

Availability and requests

Managed Private Environments are offered through a tailored enterprise request — they are not activated instantly or automatically. Everabyte confirms infrastructure availability, the proposed configuration, provisioning requirements and commercial terms with you before activation. To request a Managed Private Environment or discuss isolation requirements, contact the team via the Contact page or at sales@everabyte.com.

Backups, restoration, disaster recovery and high availability

These are four different things, and a Managed Private Environment is not all of them:

• Database backup — a recoverable copy of PostgreSQL data created according to the agreed backup policy;
• Database restoration — restoring PostgreSQL data from a valid recovery point;
• Disaster recovery — restoring the application environment after a major infrastructure incident, which may require replacement infrastructure, configuration restoration and database recovery;
• High availability — an architecture that reduces service interruption through redundancy and, where implemented, failover.

Inside an activated Managed Private Environment, database backup management and restoration are part of the managed service; the backup policy applied to your environment (frequency, retention, destination, restoration scope) is defined in your service agreement. Isolation itself does not provide high availability or a separate disaster recovery site: a private environment separates your application and database from other companies — it does not add redundant servers or automatic failover. Your file-level storage protection (encryption, versioning, backup) is documented separately in How we protect files and How backup works.

Common issues

What is a Managed Private Environment?

A dedicated application environment with an isolated PostgreSQL instance, fully managed by Everabyte — the customer-facing name for the service technically referred to as Dedicated Compute.

What exactly is isolated?

The company’s EverBox Business application services and its PostgreSQL database run in a dedicated VM environment, separated from the application instances and databases of other companies. Tenant data on the shared platform is isolated logically.

Is PostgreSQL isolated?

In a Managed Private Environment, yes: the company receives its own PostgreSQL instance with its own persistent database storage. On the shared platform, PostgreSQL is centrally operated with logical tenant isolation between companies.

Who manages the VM?

Everabyte operates, secures, updates and monitors the environment, including the database. The customer uses the normal application interface.

Can customers access SSH or Proxmox?

No. Customers do not receive root, SSH, hypervisor or Proxmox administrative access.

Is this a general-purpose VPS?

No. The environment hosts the managed Everabyte application stack and approved platform components — not unrestricted customer workloads.

Does the company receive a dedicated physical server?

Not necessarily. The environment may run on shared bare-metal hardware. Physical server exclusivity applies only if it is explicitly contracted.

Is White Label required?

No. White Label and Managed Private Environments are independent options; each is arranged under its own conditions.

Can a company buy enhanced network capacity without a private environment?

Yes. Network capacity is independent of Dedicated Compute. Enhanced capacity from 2 Gbps to 100 Gbps can be discussed on its own, subject to availability.

Is network capacity included?

Standard network capacity of up to 1 Gbps shared is included on eligible EverBlaze plans, with or without a private environment. Enhanced capacity is a separate paid option.

What happens when the option is requested?

The Everabyte team confirms feasibility, configuration (CPU, RAM, storage, region) and commercial terms, then provisions the environment as part of the agreed deployment. There is no self-service activation.

Are dedicated environments immediately available?

They are provisioned on request and confirmed case by case — the option is described as available on request until provisioning is confirmed for your deployment.

Are PostgreSQL backups included with a Managed Private Environment?

Database backup management and restoration are part of the managed service for activated Managed Private Environments. Backup frequency, retention and recovery procedures are defined in your service agreement. Your application and PostgreSQL instance are operated by Everabyte, so your team does not need to manage database infrastructure.

What happens if the infrastructure hosting my private environment fails?

Everabyte manages the recovery process for your environment. The steps and recovery time depend on the nature of the incident and the recovery arrangements included in your agreement. A private environment provides application and database isolation; it does not automatically include redundant servers, instant failover or a separate disaster recovery site. See How backup works for how file backups are protected.