LoadON does not touch your data.

LoadON operates the compute control plane — not your data plane. You buy the compute, you deploy your workloads, you keep your data. Here's exactly how we enforce that boundary.

Control Plane vs. Data Plane

LoadON Control Plane

We manage the infrastructure lifecycle so you don't have to.

  • Resource scheduling and allocation
  • Order processing and billing
  • Runtime provisioning and startup
  • Access credential generation and delivery
  • Usage metering and cost reporting
  • Runtime destruction on window expiry
  • Supplier settlement and reconciliation

Your Data Plane

Everything inside your runtime is exclusively yours.

  • Your datasets — stored and managed by you
  • Your models — deployed and run by you
  • Your scripts and code — executed by you
  • Your input data — loaded by you
  • Your output and results — saved and exported by you
  • Your data source connections — configured by you
  • Your environment variables and secrets — set by you

Zero Data Access Statement

LoadON does not receive customer datasets.

LoadON does not read customer inputs.

LoadON does not store customer results.

LoadON does not process data on behalf of customers.

Runtime environments are destroyed on expiry.

Customers may choose dedicated isolated environments.

Runtime Isolation Modes

Self-operated VM

Standard
  • Dedicated virtual machine
  • SSH access
  • Isolated filesystem
  • Auto-destroy on expiry

Container Runner

Enhanced
  • Private container runtime
  • Custom image support
  • Network isolation
  • Ephemeral storage

Dedicated Cluster

Maximum
  • Reserved bare-metal resources
  • Private network segment
  • Security audit trail
  • Extended data export window

Runtime Lifecycle

1

Purchase

Customer buys a Compute Window. Payment confirmed.

2

Provision

LoadON provisions an isolated runtime environment with allocated resources.

3

Credential Delivery

SSH keys, API tokens, and access URLs are delivered to the customer.

4

Customer Operates

Customer deploys code, connects data, runs workloads. LoadON has zero visibility.

5

Warning

60 minutes before expiry: customer receives data export reminder.

6

Destruction

Runtime is destroyed. Storage wiped. No data retained by LoadON.

Best-Fit Assessment

Well Suited For

  • Non-core async AI workloads
  • Batch processing jobs
  • De-identified data tasks
  • Customer-managed data pipelines
  • Evaluation and benchmarking
  • Embedding generation
  • RAG indexing
  • Small-scale experiments

Not Recommended For

  • Highly classified model weights
  • Real-time core inference serving
  • Un-anonymized sensitive personal data
  • Finance/medical/government regulated workloads
  • Primary training clusters

Automatic Destruction Guarantee

When your Compute Window expires, the runtime environment is automatically destroyed. All storage is wiped. No data is retained by LoadON. Enterprise customers receive an extended 24-hour export window before destruction.