Docs
DataCrunch HomeSDKAPILogin / Signup
  • Welcome to DataCrunch
    • Overview
    • Locations and Sustainability
    • Pricing and Billing
    • Team Projects
    • Support
  • CPU and GPU Instances
    • Set up a CPU or GPU instance
    • Securing Your Instance
    • Shutdown, Hibernate, and Delete
    • Adding a New User
    • Managing SSH Keys
    • Connecting to Your DataCrunch.io Server
    • Connecting to Jupyter notebook with VS Code
  • Clusters
    • Instant Clusters
      • Deploying a GPU cluster
      • Slurm
      • Spack
      • Good to know
    • Customized GPU clusters
  • Storage
    • Block Volumes
      • Attaching a block volume
      • Resizing a block volume
      • Cloning a block volume
      • Permanently deleting a block volume
    • Shared Filesystems (SFS)
      • Creating a shared filesystem
      • Editing share settings
      • Mounting a shared filesystem
  • Containers
    • Overview
    • Container Registries
    • Scaling and health-checks
    • Batching and Streaming
    • Async Inference
    • Tutorials
      • Quick: Deploy with vLLM
      • In-Depth: Deploy with TGI
      • In-Depth: Deploy with SGLang
      • In-Depth: Deploy with vLLM
      • In-Depth: Deploy with Replicate Cog
      • In-Depth: Asynchronous Inference Requests with Whisper
  • Inference
    • Overview
    • Authorization
    • Image Models
      • Flux.1 Kontext pro
      • Flux.1 Kontext max
    • Audio Models
      • Whisper X
  • Pricing and Billing
  • Resources
    • Resources Overview
    • Services Overview
    • Shared Responsibility Model
    • DataCrunch API
  • Python SDK
  • Get Free Compute Credits
Powered by GitBook
On this page
  • Shared Responsibility
  • Customer
  • Provider Responsibilities

Was this helpful?

  1. Resources

Shared Responsibility Model

Last updated 1 day ago

Was this helpful?

Shared Responsibility

Our goal with the shared responsibility model is to outline the critical and complementary roles that both DataCrunch and you, as a customer, play in ensuring the security and compliance of your projects. Our aim is to be a secure and reliable operator that you can trust.

Customer

As the customer, you are the most knowledgeable about your security and compliance needs and ensure that they are met. While working within our services, it is important that you understand and identify your usage of our services and how they impact your needs.

There are certain actions you must take to ensure your security and compliance. This will require appropriately configuring your implementations and services with secure best practices.

For example, if you deploy a GPU instance within our services, you are responsible for managing the configurations of the operating system, network, firewall, access management, and data encryption. You are also responsible for your backups, disaster recovery, and any continuity of service that falls outside of our responsibilities.

Provider Responsibilities

As the provider, DataCrunch is responsible for the operation and protection of the infrastructure in which we offer our services. Depending on the level of service, this can include the facilities, hardware, networking, and software that make up the collection of our service offerings.

For instance, if you deploy a GPU instance within our services, we will maintain and secure the physical infrastructure (e.g., power, network connections, location), access to the physical infrastructure, provisioning of the service, and provide a method for you to access your instance.

In the model above, the columns include but are not limited to:

  • Bare metal as a service - physical servers and bare-metal clusters,

  • Infrastructure as a service - virtual machine instances, storage,

  • Platform as a service - serverless containers,

  • Software as a service - cloud dashboard, billing, IAM,

  • Model - managed model endpoints.