A customer organization, including its name, address, industry, domain, and website address.
Terms related to account:  
Read more about account
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).
Terms related to capability:  
Read more about capability
An integration with an external system.
Connectors synchronize entities between systems, either bi-directionally or by creating objects in the source system.
Terms related to connection:  
Individual prospects or users associated with an organization's workspaces or accounts.
Contacts can be associated with an account or workspace, but not always.
Terms related to contact:  
Read more about contact
An interaction between the builder and consumer that may be escalated to a ticket.
Terms related to conversation:  
Read more about conversation
The consumer of a product or service, whether internal (dev) or external (rev).
Terms related to customer:  
Read more about customer
A DevRev user who develops, builds, or provides products or services to a customer (rev).
Terms related to dev:  
dev-users API reference
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
Interactions between employees and customers, encompassing communications across various channels and touchpoints.
DevRev links accounts, contacts, and employees to engagements. Additionally, they can be linked to opportunities if they are relevant to a specific opportunity.
Read more about engagement
A change to a part in the form of addition, deprecation, or transformation.
Terms related to enhancement:  
Read more about enhancement
A run time, either the customer's (for example, a browser) or the dev org's product or service.
A thing that your product does, that 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.
Terms related to feature:  
Read more about feature
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.
Terms related to identity:  
Read more about identity
dev-users API reference
A work item created by the builder or maintainer of a part or by automation.
"Autonomous issues" are created by automation.
Terms related to issue:  
Read more about issue
works API reference
A unit of functionality that is designed to be part of a system or application and not used directly.
These commonly refer to things like libraries or utilities that may be leveraged by multiple runnables.
Terms related to linkable:  
Read more about linkable
An app store for DevRev where creators and consumers come together to create, interact, and transact.
Read more about marketplace
A potential source of revenue for your organization.
Opportunities feature customizable states and stages that communicate their position within the sales pipeline.
Read more about opportunity
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 are 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.
Terms related to part:  
Read more about part
parts API reference
The part of the DevRev platform that directly enables communication with an understanding of your end users, including your customer success and support teams.
Read more about PLuG
The entity around which a business is organized and its profit and loss (PnL) is monitored.
Businesses may have multiple products.
Terms related to product:  
Read more about product
The customer of a product or service developed, built, or provided by a developer (dev).
Terms related to rev:  
A dev part that can be instantiated or do something and that has some direct execution or lifespan.
These commonly refer to things like macroservices, microservices, or functions (lambdas). A runnable may serve one or more features or capabilities.
Terms related to runnable:  
Read more about runnable
A mechanism to extend DevRev's value by connecting with external systems, automating workflows, or personalizing your experience.
Read more about snap-in
A work item that requires an owner and a single action to be performed.
Terms related to task:  
Read more about task
A record of a customer's request for assistance or support.
When a customer contacts a company with a problem or issue, the company creates a ticket to track the request and ensure that it is addressed in a timely and satisfactory manner. Also known as a "customer ticket" or "support ticket".
Terms related to ticket:  
Read more about ticket
works API reference
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).
Terms related to trail:  
Read more about trail
A member of a dev or rev organization.
Terms related to user:  
Read more about user
dev-users API reference
A list of objects in DevRev that you can sort, categorize, and share.
Read more about vista
The customer of a product or service.
Read more about workspace
rev-orgs API reference