ArcVault

Every object, logged and accounted for.

S3-compatible object storage, built and operated in India. Uploads, downloads and stored volume are recorded to the byte — so you can answer who moved what, and when, without building a logging stack around it.

Request a trial See pricing

Noida  /  Mumbai  /  Bangalore

prod-archive activity
09:41:02PUT2026/mar/ledger.csv18.4 MBbilling-svc
09:41:07GETmedia/hero-4k.mp4412.9 MBcdn-pull
09:41:11PUTbackups/vm-07.vbk2.1 GBveeam-01
09:41:19DELlogs/2025/app-334.log96 KBlifecycle
09:41:24GET2026/mar/ledger.csv18.4 MBfinance-ro
Every operation carries its object, size, actor and timestamp.

Three ways into the same bucket

Not every workload can be rewritten to speak S3, and not every user wants a command line. However a file arrives, it lands in the same bucket and the same manifest.

for applications

S3 API

Point the AWS CLI, an SDK, rclone or an S3-target backup agent at a new endpoint. No rewrite.

# any S3 client or SDK $ aws s3 sync ./reports \ s3://prod-archive/

for file workloads

NFS mount

The same bucket presented as a normal path, so software that only understands files needs no integration work.

$ mount -t nfs4 \ nfs.arcvault.in:/prod-archive \ /mnt/archive

for everyone else

Browser upload

Sign in to the console, open a bucket and drag files straight in. No client to install, no keys to hand out, nothing to configure.

# dashboard.arcvault.in Open bucket → drag files in

A single manifest for every bucket you run

Most consoles show a number for storage used. They do not show which objects moved, in which direction, at whose request. ArcVault records the transfer itself, so the console can answer questions that usually need a data pipeline.

Every PUT

Object name, size, project, bucket, actor and timestamp.

Every GET

Download volume attributed to the key that requested it.

Every byte

Stored volume and object count, sampled continuously.

Every actor

Which sub-user or access key performed which operation.

Control that survives an audit

Console sign-in is confirmed by a one-time code sent over SMS, delivered on V-Connect's own CPaaS platform. Everything below it is scoped, revocable and recorded.

  • Encryption everywhere

    AES-256 on stored data and TLS on every request in transit. Server-side encryption is applied by the platform as objects are written, so your application never handles ciphers or key material.

  • Multiple access keys

    Issue a separate S3 key pair for each application, team or integration, and revoke any one of them without disturbing the others.

  • Sub-users

    Delegate access at project level so teams can work in their own buckets without sharing the root account.

  • Bucket policy

    Public, private or scoped access is decided per bucket rather than per account, so one shared asset store does not loosen everything else.

  • Activity log

    An append-only record of every create, read, write and delete — the artefact most compliance reviews ask for and most storage platforms cannot produce.

  • Lifecycle rules

    Retention and expiry enforced automatically, so cold data ages out of primary storage without anyone remembering to move it.

Certified infrastructure, Indian data

Buckets are pinned to the region you choose, addressing residency and audit obligations for BFSI, healthcare, public sector and regulated SaaS workloads. When a reviewer asks for evidence rather than assurances, the activity log is the artefact.

ISO 27001 ISO 9001 PCI DSS Data localization DPDPA

Three Indian regions, one namespace

Data stays in the region you choose and is never moved offshore. Replicate a bucket into a second region when you need an off-site copy.

Noida

Primary console and control plane. Closest region for NCR and North India workloads.

Mumbai

Peering-dense financial hub region, suited to BFSI and low-latency west-coast delivery.

Bangalore

Southern region for product engineering, SaaS and cross-region copy targets.

Tier-1 connectivity

Tier-1 ISP links into each region for consistent, high-speed access, with India-based support on your clock.

Where ArcVault fits

  • Backup and archive

    An S3 target for Veeam, Commvault and native database dumps, with lifecycle rules moving cold data out of primary storage.

  • Disaster recovery

    Off-site copies of VM images, snapshots and configuration, held in a second Indian region.

  • Media and content origin

    An origin store for images, video and documents, served directly or fronted by a CDN.

  • Application assets

    User uploads, generated reports and attachments, offloaded from application servers.

  • Log and compliance archive

    A long-retention store for logs, statements and records, with an access trail auditors can read.

From first bucket to production

Migration is a credential change and a sync, not an application rewrite.

Step 1

Discovery and sizing

We profile the data set: volume, object count, access pattern, retention and residency requirements.

Step 2

Trial account

Opened by your V-Connect contact, or on request. Keys are issued so your team can validate the integration.

Step 3

Migration

Bulk seeding with rclone or the AWS CLI, followed by an incremental sync and a checksum reconciliation.

Step 4

Go-live and handover

Cutover, sub-user setup, billing activation and a walkthrough of the activity log and usage reporting.

Ask us for a trial account

Point your tooling at the endpoint and see the manifest for yourself. Speak to your V-Connect contact, or write to arcvault-demo@v-connect.in.

Request a trial