S3-Compatible Object Storage

Bucket storage for Cloud VPS backups, App Hosting static assets, and log archives. Standard S3 API auth and tooling; talk to an engineer to size it.

S3 request flow

  1. App or backup job signs the request
  2. Scoped key checks the bucket policy
  3. Object replicates across NVMe drives
  4. Private or public-read path returns data
4.8Shopper Approved reviews
24/7Engineer support
23 yearsin business

How Object Storage Works

Bucket-based storage that speaks the S3 API. Authenticate with access keys, address objects by key, and access them from anywhere your application runs.

Start with the access pattern. Private backup target, internal app storage, CDN origin, or archive bucket. The bucket policy follows from that choice.

S3 API compatibility

Standard PUT / GET / LIST / DELETE operations work with the AWS SDKs, the AWS CLI, s3cmd, rclone, MinIO clients, and any tool that targets the S3 API. Replace the endpoint, keep your code.

Scoped access keys

Issue per-bucket or per-application access keys. Restrict each key to read-only, write-only, or full-control on the buckets it should reach. Rotate keys without touching production code paths.

Triple-replicated durability

Each object is written as three full copies on separate NVMe drives. The loss of any single drive does not lose data, and re-replication happens in the background without operator action.

Private network access

Cloud VPS instances and App Hosting nodes inside Togglebox can reach the storage endpoint over the internal network, so backup and asset traffic does not consume public bandwidth.

Public-read on request

Buckets default to private. Public-read can be enabled per bucket for asset distribution. For production websites we recommend pulling through a CDN rather than serving directly from a public bucket.

Engineer-assisted onboarding

An engineer helps you size buckets, plan access key scopes, and pick the right access pattern for your workload. No self-serve config required to start.

What It Pairs With

Both Cloud VPS and App Hosting write to and read from Object Storage through the S3 API. Pick the pattern that matches your workload, or combine more than one if you need to.

Good fit: durable objects, archives, generated assets, and backups. Not a fit for block storage, shared POSIX file systems, or latency-sensitive database files.

Cloud VPS backup target

Stream Cloud VPS backups off-server to an Object Storage bucket. Standard backup tools (restic, duplicacy, borg via rclone) work without modification. Pair with Disaster Recovery when you need ransomware-isolated backup nodes and DRaaS recovery points in addition to bucket-level archives.

App Hosting asset and static origin

Use a bucket as the canonical store for user uploads, generated assets, and build artifacts produced by your App Hosting environments. App nodes read and write through the S3 API; a CDN sits in front for public delivery. Bucket contents survive node redeploys.

Log and audit archive

Ship rotated logs, audit trails, and compliance exports to a write-once-style bucket with a write-only access key. Long-term retention sits outside production storage so it does not compete with hot workload IO.

Cross-environment handoff

Move large files between development, staging, and production without copying through a workstation. Each environment gets a scoped key on the same shared bucket or on environment-specific buckets, depending on your isolation rules.

Pricing

Straightforward per-GB-month storage with a generous egress allowance. Internal traffic between Togglebox Cloud VPS and App Hosting nodes is not billed as public egress.

$0.10 per GB / month Storage
1 TB egress / month included $0.001 / GB beyond

Trusted by businesses that rely on real support

Verified by Shopper ApprovedCustomer Reviews — Shopper Approved

Common Questions

Is Togglebox Object Storage S3-compatible?

Yes. Standard PUT, GET, LIST, and DELETE operations work with the AWS SDKs, the AWS CLI, s3cmd, rclone, and other tools that target the S3 API. Point them at the Togglebox endpoint provided during onboarding instead of an AWS region endpoint.

Can I use Object Storage as a Cloud VPS backup target?

Yes. Most backup tools (restic, duplicacy, rclone, native database dump pipelines) support an S3 backend, so they can stream Cloud VPS backups directly into a bucket. For atomic, ransomware-isolated backup nodes in addition to bucket archives, pair Object Storage with Disaster Recovery.

How do App Hosting environments use Object Storage?

Use a bucket as the canonical store for user uploads, generated assets, and build artifacts. App Hosting nodes read and write through the S3 API, so bucket contents survive node redeploys and are shared across every node in your environment. A CDN typically sits in front for public delivery.

How does pricing and egress work?

You pay for storage used (per GB per month) and data transferred out of the platform. Internal traffic between Togglebox Cloud VPS or App Hosting nodes and the storage endpoint is not metered the same way as public egress. Exact rates and any included quotas are confirmed during onboarding so we can size them against your actual workload.

How is access controlled?

Buckets default to private. Access is granted with S3-style access keys that can be scoped per bucket and per operation set (read-only, write-only, or full control). Public-read buckets are available on request for asset distribution use cases.

No matching questions found.

Ready to Plan a Bucket?

Tell us what you want to store, where it needs to be readable from, and how it integrates with the rest of your stack. We will size it and walk through key scoping with you.