FAQ

Practical questions about private infrastructure

Clear answers about where the appliance physically lives, how it is configured and how pilot deployments work.

Before a pilot

The first decision is physical location. Then we define users, storage, backups, access, network and support expectations.

  • Office, home/private workspace or colocation.
  • Number of users and devices.
  • Storage and backup requirements.
  • Remote access needs.
  • Network, password and email requirements.

The dedicated appliance is deployed in a location agreed with you: your office, home or private workspace, or a professional datacenter colocation facility. It is not an unspecified shared server in someone else's public cloud. The primary location and backup arrangement are defined for every deployment.

No. The appliance can include storage hardware, but the product is a managed private business infrastructure platform: files, backup, secure access, network protection, password management, optional private email, configuration, monitoring, updates and support.

Yes. A pilot can start with a narrow scope such as files, permissions, backup and restore workflow, then expand into other modules later.

No. Private email is optional and should only be deployed when static IP, DNS and deliverability requirements are realistic.

The managed service layer is part of the value: setup, monitoring, updates, backup checks and support are not left entirely to the customer.

Yes. Hardware is assembled to match capacity, performance and redundancy requirements. The platform and managed service layer remain the product value.

Organizations, teams, offices and companies that need private storage, backup, secure access, network protection, password management and operational simplicity.

Still unsure where NanoCloudBox fits?

Send a short description of the office/team setup and we can recommend a practical pilot scope.

Request pilot