Platform configuration

Choose the data model that fits your environment.

Every deployment is different. MASReady supports four data handling models so your team can match security, infrastructure, and retention requirements without compromise.

🏢

Customer Hosted

Customer controls the full deployment environment. All platform components run within customer-owned infrastructure. Data never leaves the customer's perimeter.

Maximum control. Zero external dependency.

☁️

Assetize Managed

Assetize hosts and manages the platform on behalf of the customer. Governed data retention policies apply. Suitable for teams that prefer managed infrastructure without internal ops overhead.

Managed hosting with governed retention boundaries.

🪣

BYO Storage

Customer brings their own S3-compatible storage bucket. Assetize writes artefacts exclusively to the customer-owned bucket. No data stored in Assetize-managed storage.

Your bucket, your keys, your terms.

Zero Retention
🔒

Zero Retention Runtime Module

No data is stored by Assetize at any point. All processing occurs in-memory only. Customer data is never written to disk, logged, or persisted across sessions.

In-memory only. No persistence. No exceptions.

Mode comparison

At a glance — data residency, retention, and operational responsibilities across all four modes.

Capability Customer Hosted Assetize Managed BYO Storage Zero Retention
Data stays in customer environment
Assetize manages infrastructure ~
Customer controls storage bucket
Data persisted to disk
Governed retention policy Customer-defined Assetize policy Customer-defined None — no persistence
Suitable for air-gapped / high-security ~

✔ Yes    ✘ No    ~ Partial / depends on configuration    — Not applicable

Not sure which mode fits your team?

Talk through your security, infrastructure, and retention requirements with us. We'll help you map the right model to your delivery context.

Get in touch