XNS Relayer · What's New

What's changed since you last tried XNS

The Relayer app has been rebuilt and expanded since late 2025. The S3 Gateway reached general availability at v2.0.0 on June 16, 2026 and is now at v2.9.0 — here's what landed.

Full capability comparison

Relayer v1.1.0 vs v2.9.0 —
what changed across 76 features

Grouped by domain. ✓ = present · ✗ = absent · ~ = partial. Notes include version numbers and specific technical changes.

Feature / Capabilityv1.1.0 (.235)v2.9.0 (.109)Notes
S3 Protocol Surface
PutObjectv1.1.0: MinIO fork. v3.56.0: streaming; fixed 50 MB + 96 MB/upload memory ceiling
GetObject (inline + streaming)Separate inline/stream paths in v3.56.0; no 96 MiB cap on large GETs
GetObject byte-range (RFC 7233 / 206 Partial Content)~Added v1.3.0; v1.1.0 MinIO behavior not confirmed in research
HeadObject~v3.56.0: returns x-amz-delete-marker: true on delete markers with 405
DeleteObjectv3.56.0: versioning-aware; creates delete marker on versioned buckets
DeleteObjects (bulk / quiet mode)~Added v1.4.0; single-transaction; 1,000-key delete: ~30s → sub-second
ListObjectsV1v3.56.0 added v1.5.0; correct Owner, ContinuationToken echoed, MaxKeys=0 returns empty
ListObjectsV2 (continuation tokens)~V1→V2 translation; KeyCount correct (objects + common prefixes); NextContinuationToken on truncated pages
ListObjectVersions (pagination)Added v1.7.0; pagination cursor corrected v1.26.5
GetObjectAttributesAdded v1.5.0
GetObject / HeadObject ?partNumber=NAdded v1.31.0; returns 206 + x-amz-mp-parts-count
Multipart Upload (Create / Upload / Complete / Abort / ListParts / ListMultipartUploads)~v3.56.0: sessions persist across gateway restart (DB-backed v1.31.6); orphan reaper; idempotent part resend
CopyObject (physical streaming)~Added v1.17.0; all four x-amz-copy-source-if-* conditionals; COPY/REPLACE metadata directive
CopyObject (logical / sector-set reference counting)Added v1.19.0; shared objects skip gateway byte deletion; last-ref triggers physical delete; dedup-transparent billing
UploadPartCopy~Added v1.17.0

The biggest changes

Nine things that are completely different

Across the Relayer app and the new S3 Gateway — the wins that matter most to customers.

App

File manager rebuilt

Multipart uploads with no size ceiling, real-time progress, per-file error messages. Large files no longer buffer in RAM.

App

IAM built right into the UI

Create users, groups, access keys, and per-bucket policies from the dashboard — no MinIO CLI, no hand-written JSON.

App

TLS actually auto-renews now

The Let's Encrypt renewal daemon was never started. Certs silently expired at 90 days. Fixed — and renewal state now survives container rebuilds.

App

Five native monitoring dashboards

Node Health, Service Health, S3-API latency, Storage & Placement, and Repair & Durability — all with live charts and a time-range picker.

S3 Gateway

S3 Gateway 2.0 is generally available

Built from scratch March–June 2026. Spec-correct PUT/GET/DELETE at scale, concurrent writes, all AWS SDK default modes. Released June 16, 2026.

S3 Gateway

Multipart uploads survive restarts

Sessions persist across process restarts. Part re-uploads are idempotent. Browser form upload (POST policy) works including boto3 presigned-post.

S3 Gateway

Full IAM + STS + OIDC in one port

Users, groups, service accounts, temporary credentials, OIDC federation, and 11 IAM role + OIDC-provider provisioning verbs — all on the S3 data-plane port. No SDK changes.

S3 Gateway

Checksums that tools expect

CRC32, CRC32C, SHA-256, and more — validated end-to-end. AWS CLI v2, restic, and rclone no longer fail with KeyError on their default settings.

S3 Gateway

Object versioning and WORM compliance

Version-aware byte storage (each version is a distinct object), legal hold, compliance-mode retention — enforced on deletes and lifecycle expiration.

The Relayer app · late 2025 onward

A complete rebuild of the customer interface

From v3.0.2 (November 2025) to v3.56.0 (June 2026) on the app layer. Here are the changes that end-users feel.

File management
  • Multipart uploads with no size ceiling — large files stream instead of buffering in RAM
  • Upload progress always visible; per-file error messages on failure
  • Bucket stats are instant at any scale — exact counts and sizes load in milliseconds, not minutes
  • Object detail panel — click any file to see versions, retention locks, and restore history
  • Backup now covers the S3 and IAM database — bucket configs, users, and credentials were silently excluded before
Identity and security
  • IAM page: manage S3 users, groups, access keys, and policies entirely from the dashboard
  • Per-bucket scoped policies — assign read-only or read-write roles from the Create Policy modal
  • Service accounts tab for machine identities with templated policies
  • Session recovery on token expiry — 401 silently refreshes and retries; a visible sign-in prompt appears only if that fails
  • Signed-in user badge in sidebar with one-click sign-out from anywhere
TLS and connectivity
  • Let's Encrypt auto-renew fixed — renewal daemon was never started; certs silently expired at 90 days
  • Renewal state survives container rebuilds — acme.sh state is now volume-persisted
  • HTTPS no longer breaks plain-HTTP S3 clients — HTTP stays on port 9000 always; HTTPS is additive on 9443
  • CORS fixed for custom domains — running the Relayer at a public hostname no longer rejects its own API calls
Monitoring and observability
  • Five native monitoring dashboards: Node Health, Service Health, S3-API Health, Storage & Placement, Repair & Durability
  • All charts show human-readable units (IEC bytes, not raw integers)
  • Upload concurrency is auto-managed — the UI measures your connection and sets a safe value; no manual tuning
Disk management and first-boot
  • Attach, format (xfs/ext4), and mount external drives from the UI — mounts persist across container restarts
  • Fresh installs now reliably start all storage services on first boot
  • Dashboard shows a calm "Starting up" state instead of red alerts in the first 3 minutes
For node operators
  • Live provider map — world map of the global host network, health color-coded, with contract and network summary
  • Provider selection tools (VPD) — weight providers by speed, reliability, and geography; geographic bounding boxes now reach the backend correctly
Multi-tenancy
  • Multiple named tenants on a single Relayer instance — isolated S3 namespaces, credentials, quotas, and audit trails per tenant
  • Per-tenant quota enforcement: over-quota tenants get 403 on writes; reads and deletes always serve
  • Per-tenant rate limiting: noisy tenants get HTTP 503 SlowDown while neighbors keep running at full speed
  • Tenant lifecycle management from the UI: create, suspend, reactivate, and set quota/rate limits from the Tenant Management panel
  • Per-tenant usage export: bytes in, bytes out, bytes stored, request count — JSON or CSV
Webhooks & automation
  • S3 event notifications: create rules that POST to any HTTPS endpoint when objects are created, removed, or accessed
  • Filter by event type, key prefix, or suffix — one rule per use case
  • Cloud Sync: mount a local file system path and sync it to an S3 bucket in Backup mode (keeps local copy) or Archive mode (moves to bucket, removes local after confirmed upload)
  • Live sync progress with streaming status: advancing / stalled / idle / unavailable
Security improvements
  • Shell injection removed from all bucket and file operations (SEC-156)
  • Global rate limiter (600 req/min) and strict login rate limiter (20 per 15 min) protect the API
  • JWT audience enforcement — the server refuses to start if audience validation would be silently disabled
  • Credential-table Row Level Security: a misconfigured thread yields zero rows, never returns all tenants' data

S3 Gateway 2.0 · built March–June 2026

A B2B-grade S3 endpoint, built from scratch

The S3 Gateway did not exist before March 2026. It reached 2.0.0 general availability on June 16, 2026. Here is what it does.

Core compatibility
  • Spec-correct PUT, GET, DELETE — including large files, concurrent writes, and all AWS SDK v2 default modes (chunked uploads, checksum trailers)
  • Bulk delete batched in a single transaction — 1,000-key delete dropped from ~30 seconds to sub-second
  • Bucket listings that work at scale — no empty-page bugs, no 30-second timeouts on large prefixes (git .objects/ stores, rclone destinations)
  • Virtual-hosted-style addressing: bucket.s3.example.com/key in addition to path-style
Multipart and large objects
  • Full multipart lifecycle including abort, list-parts, and orphan cleanup
  • Sessions persist across process restarts — no more NoSuchUpload after a container bounce
  • Part re-uploads are idempotent — safe to retry any part
  • Browser form upload (POST policy / RFC 1867) — boto3 generate_presigned_post works
IAM, STS, and OIDC
  • Full IAM surface: users, groups, service accounts, inline and managed policies
  • STS AssumeRole with temporary credentials scoped to a bucket
  • OIDC federation (AssumeRoleWithWebIdentity) — verified against Terraform and Vault
  • Cross-account role assumption with trust-policy evaluation and ExternalId guard
  • 11 IAM role + OIDC-provider provisioning verbs (CreateRole, GetRole, DeleteRole, ListRoles, PutRolePolicy, GetRolePolicy, DeleteRolePolicy, CreateOpenIDConnectProvider, GetOpenIDConnectProvider, DeleteOpenIDConnectProvider, ListOpenIDConnectProviders) served on the S3 data-plane port — no second port, no SDK changes
Versioning, WORM, and data integrity
  • Full object versioning — each version stores its own bytes; GET ?versionId=X returns the exact data for that version
  • Object Lock: legal hold and compliance-mode retention enforced on deletes and lifecycle expiration
  • Flexible checksums (CRC32, CRC32C, CRC64NVME, SHA-1, SHA-256) — AWS CLI v2, restic, and rclone work without errors on their default settings
  • Conditional writes: If-None-Match:* (create-only) and If-Match:etag (optimistic lock)
Bucket policy, CORS, and access control
  • Stored bucket policies enforced on every request — IP CIDR conditions, prefix wildcards, deny-overrides-allow
  • Public Access Block — blocks wildcard-principal policies at write time
  • CORS enforcement and correct preflight handling — presigned-URL browser uploads unblocked
  • Authorization bypass closed on tagging and multipart paths
Audit and AI integration
  • Durable audit log (PostgreSQL) — every S3 event retained for 90–365 days; SIEM export via HMAC-signed webhook
  • MCP server for AI clients (Claude, Cursor) — 8 tools with per-principal IAM enforcement and full audit integration
  • S3 event notifications via webhook — filter by event type, prefix, suffix; HMAC-signed delivery

Ready to try the new XNS?

$6.00/TB-mo, $0 egress uncapped, 30-day minimum retention. Change one endpoint and everything that speaks S3 already works.

Claims on this page last verified
© Copyright - SCP, Corp | Xa Net Services and Affiliates