DevRev Glossary

capability#

A collection of features that enable a customer to achieve a use case.

Capability is a unit of licensing and entitlement for the persona driving a particular use case. As a collection of features, capabilities are grouped into different buckets for tiered use cases (for example, starter-professional-enterprise).

Read more about capability.

Terms related to capability: feature, product

connection#

An integration with an external system.

Terms related to connection: snap-in

conversation#

An interaction between the builder and consumer that may be escalated to a ticket.

Read more about conversation.

Terms related to conversation: ticket

dev#

A DevRev user who develops, builds, or provides products or services to a customer (rev).

Terms related to dev: rev

DevCRM#

The operating system provided by DevRev to build a product-led and customer-centric company.

Read more about DevCRM.

Terms related to DevCRM: DevRev

DevRev#

A platform that brings developers (devs) closer to customers (revs) by providing a single system of record for development, customer-facing, and product teams.

DevRev's mission is to leverage design, data engineering, and machine intelligence to empower engineers to embrace their customers.

Read more about DevRev.

feature#

A thing that your product does, which should contribute to solving the overall problem the product is trying to solve. It is an individual experience or element of functionality.

Features are the smallest unit of entitlement (user) or deployment (developer, DevOps) that can be switched on or off, based on which tier the user is licensed to use, or which feature flag has been toggled in the production cloud. Features comprise sub-features and APIs.

Read more about feature.

Terms related to feature: capability, product

identity#

The mechanism to ensure that internal users (devs) get access to the correct data and have a personalized experience and to ensure that an organization can accurately maintain a system of record for their leads, customers, and users.

Read more about identity.

Terms related to identity: part, work

issue#

A work item created by the builder or maintainer of a part.

Read more about issue.

Terms related to issue: ticket, part, work

marketplace#

A app store for DevCRM where creators and consumers come together to create, interact, and transact.

organization#

The owner or customer of a product or service; also a workspace in DevCRM for a particular group.

A rev org is a customer organization of the DevOrg's products or services. A dev org is an organization that is DevRev's direct customer and who provides products and/or services to their customers (rev orgs).

part#

A component of a product.

A part can be made of other parts. Events and work items can be specific to any type of part. Rev parts related to how a product is expressed, integrated, or consumed. Dev parts are those built internally related to code or something the developer relies on or builds, or a service provided by an organization.

Read more about part.

Terms related to part: identity, trail, work

PLuG#

The part of the DevRev platform that directly enables communication with and understanding of your end users, including your customer success and support teams.

Read more about PLuG.

product#

The entity around which a business is organized and its profit and loss (PnL) is monitored.

Businesses may have multiple products.

Read more about product.

Terms related to product: capability, feature

rev#

The customer of a product or service developed, built, or provided by a developer (dev).

Terms related to rev: dev

snap-in#

A mechanism to extend DevCRM’s value by connecting with external systems, automating workflows, or personalizing your experience.

task#

A work item typically used to break down a larger ticket or issue into more manageable pieces.

Read more about task.

Terms related to task: issue, work

ticket#

A work item that comes from the front office (customer, employee, engineer).

A ticket requires an owner and some level of interaction or work to be performed. While incidents may be notification only, a ticket requires someone or something to take some action (triage).

Read more about ticket.

Terms related to ticket: conversation, issue, work

trail#

Connects dev parts (the code, service, or components built or used by the developer) and rev parts (how a product is expressed, integrated, or consumed).

Read more about trail.

Terms related to trail: part

user#

A member of a dev or rev organization.

Terms related to user: organization