Storage
Object, file, block, and cold archive storage delivered across a managed multi-vendor public cloud. SLA-defined durability, encryption at rest and in flight, geo-redundant replication, and audit-ready restore evidence.
1,598
Data centers
Storage-capable facilities across 55 countries and 5 continents
99.999%
Availability SLA
Object storage availability with documented service credits
100Gbps
Throughput
Ingest and egress for data-intensive workloads and migrations
24/7
SOC & NOC
Continuous monitoring with tested restore drills and incident playbooks
Public cloud storage — explore solutions
Storage
End-to-end managed storage across object, file, block, and archive. Unified policy, monitoring, and billing across tiers and vendors.
Storage
S3-compatible scalable object storage for cloud-native applications, backups, media libraries, and data lakes.
Storage
Shared NFS and SMB file systems for applications, collaboration, home directories, and persistent workloads.
Storage
High-performance persistent volumes for compute, databases, and latency-sensitive transactional workloads.
Storage
Long-term low-cost archival storage for compliance retention, legal hold, and historical data preservation.
Storage
Parallel file systems, GPU-attached NVMe, tape retention, or sovereign-region storage. We scope and operate the combination.
Overview
intSignal's public cloud storage services give enterprises one operator across the major hyperscalers, sovereign regional providers, and our own managed platform — delivered with the same SLAs, change control, and reporting model.
Our engineering team selects the right storage class for each workload, sets encryption and lifecycle policy, monitors integrity, and runs scheduled restore drills against documented RTO and RPO targets.
Capabilities
Featured products and solutions
How it works
Objects are split into data shards and parity shards using Reed-Solomon erasure coding, then distributed across three zones. Any single zone can fail and the object reconstructs from the remaining shards.
Continuous background scrubbing verifies checksums and rebuilds shards before durability is impacted.
API
Drop-in compatibility with the AWS S3 API surface. Existing SDKs, tools, and ETL pipelines continue to work unchanged.
Durability
Erasure-coded across availability zones with continuous integrity scanning. Designed for 99.999999999% annual durability.
Protection
WORM retention, governance and compliance modes, and full version history for regulated workloads and ransomware resilience.
How it works
One file system mounted concurrently by Linux, Windows, and clustered workloads over NFS or SMB. POSIX semantics and Active Directory integration let existing applications run unchanged.
Per-share quotas, snapshots, and QoS controls keep noisy neighbors from impacting other tenants on the same volume.
Protocols
Native protocol support for Linux, Windows, and mixed environments. POSIX semantics and Active Directory integration available.
Scaling
Grow file systems online without provisioning headroom. Per-share quotas, snapshots, and quality-of-service controls.
Workloads
Engineered for home directories, build farms, content repositories, and applications that need concurrent shared access.
How it works
The volume presents fixed-size blocks to the guest OS over iSCSI or virtio-blk. The instance lays its own filesystem on top — ext4, XFS, NTFS — giving full control over allocation and caching.
NVMe-backed storage delivers sub-10ms p95 latency. Snapshots are crash- or application-consistent, and multi-attach supports clustered databases and HA configurations.
Performance
Sub-10ms p95 latency on premium volumes. Choose IOPS and throughput independently from capacity for database workloads.
Data protection
Crash-consistent and application-consistent snapshots with instant volume clones for test, dev, and recovery scenarios.
Topology
Attach a single volume to multiple compute instances for clustered databases and shared-disk HA designs.
How it works
Lifecycle policies move objects from hot to warm to cold based on age, access pattern, or object tag. The object's identifier and metadata stay constant — only the storage tier changes.
Retrievals from cold are queued and hydrated within documented restore windows, with legal hold and retention rules enforced throughout the process.
Economics
Sub-cent per GB monthly storage for data accessed less than once a year. Predictable retrieval and egress pricing.
Compliance
Legal hold, retention policies, and tamper-evident logs designed for regulatory archive obligations measured in years.
Redundancy
Optional geographic redundancy for archive data with documented restore-time expectations per region pairing.
How it works
Lifecycle policies, encryption, identity, telemetry, and SLA reporting are defined once in the intSignal control plane and applied uniformly across AWS, Azure, GCP, OVHcloud, and intSignal's own platform.
Operators interact through a unified console; CI/CD pipelines drive infrastructure changes through the same Terraform provider and REST API.
Control plane
One control plane across tiers, vendors, and regions. Identity-based access controls and policy-as-code integration.
Observability
Capacity, latency, error-rate, and durability metrics with thresholds tied to your incident response playbooks.
Automation
Terraform provider, REST API, and CLI for infrastructure-as-code workflows and CI/CD integration.
How delivery works
Every engagement follows the same four-stage delivery model with documented handoff at each gate.
Inventory workloads, classify data sensitivity, set durability and recovery targets, map regulatory scope.
Select storage classes, vendors, and regions. Define encryption, lifecycle, and access policies as code.
Controlled migration with parallel-run validation. Cutover plan with rollback path and acceptance criteria.
Monthly metrics by business impact, scheduled restore tests, capacity forecasting, optimization reviews.
Compliance & security
All storage tiers operate under intSignal's enterprise control framework with documented evidence aligned to common regulatory programs.
Audited controls for security, availability, and confidentiality across managed storage.
International standard for information security management aligned across regions.
PHI-ready storage with business associate agreements for healthcare workloads.
Data residency, controller agreements, and regional hosting for EU workloads.
Payment card industry alignment for cardholder data storage and processing.
Federal Risk and Authorization Management for U.S. government workloads.
FAQ
Frequently asked questions about intSignal's public cloud storage services.
We operate storage on AWS, Microsoft Azure, Google Cloud, OVHcloud, and intSignal's own managed platform. Multi-vendor design lets us match workload, region, sovereignty, and cost requirements without lock-in.
Object and archive tiers default to erasure-coded storage across multiple availability zones, with continuous background integrity scanning. We document the durability math and provide scheduled restore drill evidence as part of monthly reporting.
Yes. Lifecycle policies move objects automatically based on age, access pattern, or tag. We design these policies during the assess phase and tune them quarterly based on actual access telemetry.
All storage is encrypted at rest with AES-256 and in flight with TLS 1.3. You can use vendor-managed keys, your own KMS, or BYOK with HSM-backed key custody depending on compliance needs.
Our 24/7 NOC and SOC follow pre-agreed playbooks tied to your business-impact priorities. Incident timelines, communications, and remediation are documented and reviewed post-incident — not closed when the alert clears.
Provide environment, constraints, and priorities. We return scope, ownership, and a success criteria document.