Run S3-compatible object storage on an offshore server you administer. Review storage capacity, transfer allowances and the API operations required by your clients before moving production buckets.
What you get
- S3-compatible access, validated against the operations and authentication your clients require
- Capacity planning you control: review server, storage and transfer limits for your workload
- A web console for buckets, users and policies
- Offshore, no KYC, crypto billing
Get it running
Size storage and throughput
Plan disk capacity, memory, CPU and network throughput for object size and concurrent requests. Allow for growth and for any versioning or recovery copies you intend to retain.
Install it in one click
Install MinIO from the catalog with a hostname for the console. The root password is generated for you and shown in the panel. See how one-click installs work.
Save the root credentials, then stop using them
Move the generated root credentials into your password manager immediately. Then create a dedicated user and access key per application, scoped to the buckets it actually needs.
Point your tools at it
Configure your S3 client, SDK or backup tool with your endpoint and the scoped key. Verify the S3 operations and authentication options your client needs before moving production data.
The generated root user has full control of every bucket and policy. Wiring an application, a script or a backup job to it means one leaked config file exposes everything. Create a scoped user per consumer, grant only the buckets and actions it needs, and keep root for administration.
MinIO serves the S3 API and the web console on separate ports. Decide deliberately what is reachable from where: a public console is an authentication surface you may not need, and an unrestricted API endpoint invites credential stuffing. Publish only what has to be public.
A self-hosted MinIO instance can serve as a destination for backup tools that support its S3 interface. Review the tool’s compatibility, encryption options and recovery procedure. Protect bucket access and keep another copy outside the failure domain of this VPS.
The integrated Impreza app backup service uses the Impreza S3 storage associated with your account. Deploying this MinIO app does not automatically make it that service’s backup destination. Moving an object store also requires validating buckets, objects, access policies and client endpoints; do not assume the generic app migration workflow alone covers a complete storage migration.
A single VPS is not a replicated storage cluster. Treat it as primary storage with a copy elsewhere, not as the only copy of anything you cannot lose.
Verify client access after maintenance
For supported deployments with the Impreza Agent online, use app inspection and maintenance, then test a dedicated non-production bucket with the same client configuration your application uses. Verify required operations and confirm that its scoped credentials cannot access unrelated buckets.
Keep object-store users and policies separate from delegated app access. A platform delegation is not an S3 access key and does not replace bucket permissions.
After recovery or an endpoint change, verify expected objects and access policies before moving application traffic. Retain an independent recoverable copy and review the separate storage-migration requirements described above.
Start now
Spin up an offshore VPS and install MinIO from the catalog, or read the documentation.