Speaks S3
Path-style S3 with Signature V4: the AWS CLI, every AWS SDK, rclone and Laravel disks work by changing one endpoint. Multipart uploads, ranges and presigned URLs included.
Hive Vault puts Cloudflare R2, Backblaze B2, Amazon S3, Hetzner, MinIO and your own servers behind one S3 API, one console and one set of keys, with projects, tenants, versions and an audit trail built in.
https://storage.techiveet.com
PUT /media/hero.jpg 200 → B2
GET /media/hero.jpg 200 cached 7d
DEL /private/old-cv.pdf 204 → trash
One API in front of every provider, for every S3 tool
Inside an upload
Every request takes the same path through Hive Vault, whichever S3 tool sends it and whichever provider keeps the bytes.
Any S3 client does: the AWS CLI, an AWS SDK, rclone or Laravel’s s3 disk. It signs the request with a Hive Vault access key and sends it to one address, https://storage.techiveet.com.
The Signature V4 signature is verified, then the key itself: its project, the buckets it may use, read or write, and whether it has expired or been revoked. Anything else is refused.
Blocked file types and executables disguised as images are refused by their content, not just their name. Size limits and the tenant, project and organisation quotas are applied too.
Each bucket has a storage alias that decides where its bytes go: R2, B2, S3, Hetzner, MinIO, a Web Disk or this server’s disk. Big uploads go in parts, relayed to providers that support it.
The bytes land with the provider. The file record, its version and an audit entry are written, and a background job computes the SHA-256 and checks the content.
Public files come from https://storage.techiveet.com/<bucket>/<key> with seven-day cache headers. Private files go out through signed links that expire, and permanent /f/ links are there for your app to store.
Watch a file go in
An example upload with the AWS CLI, with what Hive Vault does behind it in honey.
Features
Stop wiring each product to its own bucket, keys and rules. Hive Vault gives every product the same storage foundation.
Path-style S3 with Signature V4: the AWS CLI, every AWS SDK, rclone and Laravel disks work by changing one endpoint. Multipart uploads, ranges and presigned URLs included.
Storage aliases route each project’s files to R2, B2, S3, Hetzner, MinIO, WebDAV or your own server. Re-point an alias and new files go there, with no change to your app.
Organisations hold projects, projects hold tenants. Give every customer their own bucket, with quotas at each level so nobody fills the hive alone.
Overwrites keep earlier versions, deletes go to the trash first, and legal hold freezes files that must never change.
Public files are served with long cache headers, private ones through signed links that expire, plus permanent /f/ links your app can store.
Uploads, downloads, keys, members and settings: every action is recorded per project with who, when and from where.
How it works
Add a provider in the console: R2, B2, S3, Hetzner, MinIO, a cPanel Web Disk or this server’s disk. Hive Vault tests it and learns what it can do.
A project holds your buckets, folders, tenants and keys. Storage aliases decide which provider each file goes to; buckets can be public or private.
Issue an access key, set the endpoint, and use the S3 client you already have. Files appear in the console as they arrive.
Developers
If it talks to S3, it talks to Hive Vault. Point the endpoint here and keep your buckets, keys and URLs working the way they always have.
# Any AWS tool works: point it at Hive Vault (AWS CLI v2)
export AWS_ENDPOINT_URL=https://storage.techiveet.com
export AWS_ACCESS_KEY_ID=TSAK… AWS_SECRET_ACCESS_KEY=…
aws s3 cp ./hero.jpg s3://my-bucket/images/hero.jpg
aws s3 ls s3://my-bucket/images/
aws s3 presign s3://my-bucket/report.pdf --expires-in 3600
import { S3Client, PutObjectCommand } from '@aws-sdk/client-s3';
const vault = new S3Client({
endpoint: 'https://storage.techiveet.com',
region: 'us-east-1',
forcePathStyle: true,
credentials: { accessKeyId: process.env.HIVE_KEY_ID, secretAccessKey: process.env.HIVE_SECRET },
});
await vault.send(new PutObjectCommand({ Bucket: 'my-bucket', Key: 'images/hero.jpg', Body: file }));
# .env: Laravel's own "s3" disk, unchanged
AWS_ACCESS_KEY_ID=TSAK…
AWS_SECRET_ACCESS_KEY=…
AWS_DEFAULT_REGION=us-east-1
AWS_BUCKET=my-bucket
AWS_ENDPOINT=https://storage.techiveet.com
AWS_USE_PATH_STYLE_ENDPOINT=true
AWS_URL=https://storage.techiveet.com/my-bucket
import boto3
from botocore.config import Config
vault = boto3.client('s3', endpoint_url='https://storage.techiveet.com', region_name='us-east-1',
config=Config(s3={'addressing_style': 'path'}))
vault.upload_file('hero.jpg', 'my-bucket', 'images/hero.jpg')
url = vault.generate_presigned_url('get_object', Params={'Bucket': 'my-bucket', 'Key': 'report.pdf'}, ExpiresIn=3600)
Security
Every key, member and file is accounted for. The defaults are the safe ones.
API keys are stored hashed and S3 secrets encrypted. Every key has its scope, buckets, expiry and a revoke button.
Console accounts can require an authenticator code, with recovery codes for the day a phone is lost.
Owners, admins, developers and viewers each see and change only what their role allows.
Blocked file types and executables disguised as images are refused at upload, by content and not just by name.
FAQ
Yes. Hive Vault speaks the Amazon S3 API path-style with Signature V4, so the AWS CLI, AWS SDKs, rclone and Laravel’s s3 disk work by setting the endpoint to https://storage.techiveet.com and using a Hive Vault access key. Virtual-hosted style (bucket.host) and Signature V2 are not supported.
On the storage your organisation connects: Cloudflare R2, Backblaze B2, Amazon S3, Hetzner, MinIO, a WebDAV or cPanel Web Disk, or the server’s own disk. Hive Vault routes, checks and records every file; the bytes live with the provider you choose.
Yes. Your apps talk to buckets and storage aliases, never to a provider directly. Point an alias at another provider’s bucket and new files are stored there, while your endpoint, keys and URLs stay the same.
An overwrite keeps the earlier version when the project keeps versions. A delete moves the file to the trash for the project’s trash period before it is purged, and files under legal hold cannot be changed or deleted at all.
Public files are served at https://storage.techiveet.com/<bucket>/<key>, with long cache headers so browsers and CDNs keep them. Private files are shared through signed links that expire.
Accounts are by invitation. An organisation owner invites you from the console (Members), and the email takes you straight to creating your account.
Bring every product’s storage into one vault you control, on the providers you choose.
Accounts are by invitation: ask your organisation’s owner to invite you.