Academy Documentation
  • Usage of Academy Documentation
  • Getting Started
    • Background Information
    • For Apollo Users
    • For Titan Users
    • For Scientists
    • For HPC Users
    • For Experienced Users
  • Cloud Computing
    • General Information
    • Cloud Computing for Scientists
    • Cloud Computing for HPC Users
  • Overview of the Platform
    • Overview of the Platform User Interface
    • Tool Library and App Introduction
  • Billing Access and Orgs
    • Orgs and Account Management
    • Billing and Pricing
  • Cohort Browser
    • Apollo Introduction
    • Overview of the Cohort Browser
    • Combining Cohorts
    • Genomic Variant Browser
    • Somatic Variants
  • JSON
    • Introduction
    • JSON on the Platform
  • Command Line Interface (CLI)
    • Introduction to CLI
    • Advanced CLI
  • Building Applets
    • Introduction
    • Bash
      • Example 1: Word Count (wc)
      • Example 2: fastq_quality_trimmer
      • Example 3: samtools
      • Example 4: cnvkit
    • Python
      • Example 1: Word Count (wc)
      • Example 2: fastq_quality_trimmer
      • Example 3: cnvkit
  • Building Workflows
    • Native Workflows
    • WDL
      • Example 1: hello
      • Example 2: Word Count (wc)
      • Example 3: fastq_trimmer
      • Example 4: cnvkit
      • Example 5: workflow
    • Nextflow
      • Resources To Learn Nextflow
      • Overview of Nextflow
      • Nextflow Setup
      • Importing Nf-Core
      • Building Nextflow Applets
      • Error Strategies for Nextflow
      • Job Failures
      • Useful Information
  • Interactive Cloud Computing
    • Cloud Workstation
    • TTYD
    • TTYD vs Cloud Workstation
    • JupyterLab
      • Introduction
      • Running a JupyterLab Notebook
  • Docker
    • Using Docker
    • Creating Docker Snapshots
    • Running Docker with Swiss Army Knife
  • Portals
    • Overview of JSON files for Portals
    • Branding JSON File
    • Home JSON File
    • Navigation JSON File
    • Updating Your Portal
  • AI/ ML Accelerator
    • Data Profiler
      • Introduction to Data Profiler
      • Utilizing Data Profiler Navigator
      • Dataset Level Screen
      • Table Level Screen
      • Column Level Screen
      • Explorer Mode
      • Accessing Data Profiler in ML JupyterLab
    • ML JupyterLab
      • Introduction to ML JupyterLab
      • Getting Started in ML JupyterLab
      • In App Features
      • Getting Started with ML JupyterLab
    • MLflow
      • Introduction to MLflow
      • Getting Started with MLflow
      • Using MLflow Tracking Server
      • Model Registry
      • Using Existing Model
      • Utilizing MLflow in JupyterLab
Powered by GitBook
On this page
  • Billing
  • Billing and Charges
  • Organizations and Billing
  • Resources

Was this helpful?

Export as PDF
  1. Billing Access and Orgs

Billing and Pricing

PreviousOrgs and Account ManagementNextCohort Browser

Last updated 2 months ago

Was this helpful?

Billing

Definition

Billing occurs monthly based on your use of the platform. These invoices are received at the end of the month

The relationship of DNAnexus and billing are highlighted here:

Billing and Charges

What are the charges?

  • Regions and Pricing can be referred to as the "Rate Card"

  • These are negotiated at the time of signing

  • This is the area of expertise of the DNAnexus Sales Account Director. For further details on this, please refer to them.

  • This can be useful for everyone else to decide the instances that you choose to run on the platform.

  • Here is an image of what a rate card looks like, and what each of the sections mean. The details of the rate card are subject to change

  • If you cannot access the rate card or are not an org admin, please see Appendix A of your order form.

Errors and Billing

  • Job Errors happen

    • Some of which are charged to you

    • Some of which are not

Organizations and Billing

Example: Orgs and Billing

  • Orgs can be used to consolidate and simplify billing.

  • An order can be associated with a billing account. This allows all users of the org to build projects and apps to the org billing account.

  • If you have a project bill to an org, this is useful. Say if you have users within a group or users within a particular lab, that are working with a shared budget, where each member needs to have the ability to work independently within their own project.

  • By associating a billing account with an org, this allows groups with a shared budget to consolidate all platform activities onto one invoice.

  • When a user makes a project billable to an account, a user assigns ownership of the project to this work.

  • And org admins in this case admins, A and D. They have the ability to oversee and discover all projects that are billed to the org and revoke permissions to a project build to an org

Resources

To create a support ticket if there are technical issues:

  1. Go to the Help header (same section where Projects and Tools are) inside the platform

  2. Select "Contact Support"

  3. Fill in the Subject and Message to submit a support ticket.

Error details are found in our

Documentation
Billing and Account management Documentation
Full Documentation