Dive into our documentation.

Whether you’re a developer integrating Atlas or a founder exploring advanced analytics, our docs walk you through setup, best practices, and real-world examples. Integrated with Stripe and QuickBooks for secure payment processing.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Key Terms

Here are some important terms to know as you navigate Atlas.

  • Merchant: Atlas customer - the entity that's using Atlas to bill their customers
  • Customer: The customer of the merchant
  • User: The individual who works at the customer
  • Atlas User: The merchant user who is using the atlas app
  • Plan: A bucket containing entitlements and/or metrics - most represent what the user is buying
  • Entitlement: Static capability or feature, can be granular or high level. Can also include non software specific items that are on a contract, e.g. support hours.
  • Metric: A set of events, filtered, and counted, summed, or averaged, etc. to be billed
  • Price: Price set on an entitlement or billable metric
  • Event: An event defined by our merchants that can be tied to a metric or feature
  • Price Type: Defines price structure (one-time, tiered, capped, etc.)
  • Credits: Pre-paid units that can be used to pay down invoices or unlock functionality
  • Subscription: Ties a plan to a specific user/customer and invoice
  • Invoice: What is billed to the customer. Contains terms and detailed line items.
  • Jobs Engine: Nightly procedure of reconciling usage with subscriptions, visitors, and accounts. Generates invoices, retries, etc.
  • SDK: Both client and server-side packages for calling Atlas API endpoints

Deploy your next pricing model in 10 clicks or less.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.