Subprocessors | Arximus

Provider transparency

Serious customers need to know where operational dependencies sit.

Subprocessors may support cloud hosting, managed databases, object storage, billing, email delivery, monitoring, analytics, support workflows, and security operations.

The final public list should include provider names, purpose, location or region where applicable, and links to their security or privacy information.

Control and review

Subprocessor use should follow the security model.

Providers should be selected according to security, availability, data region, operational reliability, and contractual requirements.

Changes to critical subprocessors should be tracked and communicated according to customer requirements and legal obligations.

Subprocessor categories

The provider categories Arximus expects to document.

This page should be finalized with the actual providers selected for production.

Hosting

Cloud infrastructure

Application hosting, compute, networking, regional availability, and platform infrastructure.

Database

Managed databases

Database, cache, queue, and internal state services used by Arximus Cloud.

Storage

Object storage

Encrypted backup chunk storage, manifests, reports, and restore artifacts.

Billing

Payment processing

Subscriptions, invoices, protected site units, storage blocks, and billing communication.

Messaging

Notifications

Transactional email, alerts, support communication, and future integrations.

Monitoring

Operational monitoring

Uptime checks, logging, error tracking, and service health visibility.

Trust outcome

Customers get a clear view of operational dependencies.

Subprocessor transparency supports privacy, compliance, procurement, and risk review.

List

Document providers

Show provider name, purpose, region, and relevant security documentation.

Review

Evaluate risk

Review providers for security posture, contractual terms, and data handling.

Notify

Communicate changes

Define how customers are informed when critical providers change.

Control

Limit scope

Use each provider for a specific purpose and avoid unnecessary data exposure.

Launch note

Finalize this page when production vendors are locked.

The page structure is ready, but the final provider list should be completed before public launch.

Next step

Review vendor and region choices.

We can align infrastructure choices, data region needs, customer expectations, and legal documentation.

Request a briefing View platform

Transparency for the services that help operate Arximus.