Datadog, Inc. is a New York-headquartered public software company whose Class A shares trade on Nasdaq as DDOG; after an April 2026 conversion, it is domiciled in Nevada. This profile covers Datadog, Inc. and its consolidated subsidiaries; acquired businesses appear only where they explain platform expansion. Founded in 2010 by Olivier Pomel and Alexis Lê-Quôc, Datadog sells a cloud-delivered observability and security platform spanning infrastructure, applications, logs, user experience, security, service management, developer workflows, data and AI-related telemetry. Its stated mission is to give teams complete visibility across their entire stack. It earns primarily subscription revenue, using commitment and usage mechanics that support land-and-expand. By June 30, 2026, Datadog served about 33,400 customers through self-service adoption, direct sales and cloud marketplaces. It competes with full-stack observability vendors, cloud-native tools and specialist or open-source alternatives. Growth centers on customer expansion, AI product development, acquisitions and international selling; major constraints include third-party cloud infrastructure economics and usage variability among large customers. Evidence cutoff: August 10, 2026, using Datadog's June 2026 Form 10-Q and the April 2026 Nevada redomiciliation filing.
Datadog's Q2 2026 results and Form 10-Q provide the revenue, customer, ARR and adoption figures.
Datadog began in 2010 around a practical DevOps problem: development and operations teams were using fragmented tools and lacked a shared view of increasingly dynamic systems. It progressed from infrastructure monitoring into a broad software platform, went public in 2019, expanded into security and adjacent workflows, and in 2026 changed its legal domicile from Delaware to Nevada.
Pomel and Lê-Quôc had previously worked at Wireless Generation, where Pomel led technology and Lê-Quôc led operations. That shared experience matters because Datadog's original problem statement was organizational as much as technical: give developers and operators common, timely information instead of separate monitoring silos. The early product therefore emphasized quick setup, cloud-scale data collection and collaboration rather than a heavy professional-services implementation.
Pomel and Lê-Quôc founded Datadog; the corporation was incorporated in Delaware in June.
A $6.2 million investment supported product development and expansion of the young monitoring company.
Datadog priced its IPO and Class A shares began Nasdaq trading under DDOG in September.
Metaplane and Eppo acquisitions extended the platform toward data observability, product analytics and experimentation.
Stockholders approved conversion from Delaware to Nevada without changing Datadog's underlying operating business.
DASH 2026 introduced more than 100 capabilities spanning AI agents, security, operations and developer workflows.
History is supported by Datadog's 2025 Form 10-K, its 2012 funding announcement, the 2019 IPO announcement and the April 2026 Form 8-K.
Datadog explicitly described its mission in January 2026 as giving teams complete visibility across their entire stack. Its longer-term direction is broader than monitoring alone: official materials increasingly connect observability with security, data, AI and automated operations. Current engineering recruiting material also names pragmatism, honesty and simplicity as values of the engineering culture.
The consistency is visible in product choices. More than 1,000 integrations reduce the friction of collecting signals from heterogeneous environments; new AI agents are intended to move teams from detection toward action; and acquisitions such as Metaplane and Eppo extend visibility into data quality and product experimentation. Those actions broaden the surface area while retaining a common idea: put operational context in one place so teams can make faster, better-informed decisions.
Datadog says its mission is to give teams complete visibility across their entire stack, a formulation that links the original DevOps problem to newer security, data and AI workloads.
Engineering recruiting material identifies pragmatism, honesty and simplicity as culture values, while product materials emphasize low-friction deployment, integrated context and progressively broader automation.
The distinction draws on Datadog's mission statement and its engineering culture description.
Datadog is owned by public shareholders, but voting power is not proportional to economic share ownership because Class B shares carry ten votes each while Class A shares carry one. The March 31, 2026 proxy table showed co-founders Pomel and Lê-Quôc with 17.3% and 15.5% of total voting power, respectively, preserving substantial founder influence.
The same proxy reported 35.5% of total voting power for all directors and executive officers as a group. Vanguard, BlackRock and FMR were large disclosed Class A holders, but their voting power was materially lower than their Class A ownership percentages because they held no disclosed Class B shares in that table. Adding the two founders' reported voting percentages gives 32.8%, a transparent calculation from the proxy rather than a separately reported company metric.
The April 21, 2026 redomiciliation changed the law governing Datadog's internal affairs from Delaware to Nevada, not the operating business, jobs, management, properties, assets or liabilities. The Class A shares continued to trade on Nasdaq as DDOG, as documented in the redomiciliation Form 8-K. Governance therefore combines ordinary public-company board oversight with a dual-class structure that gives the co-founders outsized voting influence relative to their Class A holdings.
The March 31, 2026 proxy table shows founder voting influence exceeding that of the largest disclosed institutional Class A holders.
The percentages and one-vote-versus-ten-vote structure come from Datadog's 2026 proxy statement.
Datadog operates a cloud-delivered software platform that ingests telemetry from customer systems, correlates that data across observability and security products, and charges primarily through subscriptions with committed and usage-sensitive structures. The economic engine depends on easy initial adoption, rising monitored workloads, cross-product expansion and recurring renewals rather than implementation-heavy professional services.
The platform spans more than 20 products across infrastructure monitoring, application performance monitoring, log management, digital experience, security, service management and developer monitoring. It is cloud-agnostic and designed for public cloud, private cloud, on-premises, multi-cloud and hybrid environments. More than 1,000 supported integrations are a major distribution mechanism inside the product itself because they let customers connect existing cloud services, databases, containers, developer tools and infrastructure without building every collector from scratch.
A customer can start with one workload or product, then increase monitored usage and add products as more teams and systems enter the platform, turning product adoption into recurring expansion revenue.
- Self-service installation shortens time to initial value.
- Usage can grow with hosts, containers, logs and other telemetry.
- Additional products create cross-sell paths inside one account.
- Renewal and expansion determine the durability of recurring revenue.
Datadog describes this model in its 2025 Form 10-K.
Subscription terms are primarily monthly, annual or multi-year, with the majority of revenue coming from annual subscriptions. Customers may commit to contractual usage that is recognized ratably, commit to usage delivered as consumed, or buy monthly usage-based subscriptions; incremental usage can create extra charges. This mix means Datadog can benefit when customers' workloads expand, but revenue can also react to optimization or reduced consumption.
Agents and integrations collect telemetry from applications, infrastructure, users, data and security systems.
Datadog's cloud platform receives high-volume metrics, traces, logs, events and related signals.
Shared context connects signals across products so teams can investigate the same environment.
Dashboards, alerts, search and AI capabilities surface anomalies, dependencies and operating patterns.
Engineering, operations and security teams troubleshoot, remediate, optimize and coordinate responses.
More workloads, telemetry and products can increase account usage and recurring subscription value.
The product architecture and value flow are grounded in Datadog's 1,000-integration milestone and its annual-report platform description.
Major cost pools sit on the other side of that value flow. Datadog spends heavily on engineering and product development, sales and marketing, and the third-party cloud infrastructure and software needed to host and process customer telemetry. Because professional services are generally unnecessary and historically immaterial to revenue, the model is structurally software-centric; gross margin therefore depends strongly on infrastructure efficiency, data volumes and cloud-provider economics.
Datadog's 2025-2026 expansion is less about leaving observability than widening what can be observed and acted upon. Acquisitions brought data quality and experimentation into the platform, while 2026 launches added AI-assisted coding, chat, agent construction and automated operations. The strategic pattern is to make Datadog a shared control plane for increasingly AI-heavy software systems.
This matters because AI applications create new operational objects: models, prompts, agents, GPU workloads, data pipelines and autonomous actions. Datadog is trying to connect those objects to the same infrastructure, application and security context already used by engineering teams. That makes AI expansion both a product-development program and a cross-sell mechanism into an installed observability base.
How is AI changing the core platform?
DASH 2026 introduced more than 100 capabilities, including Bits Agent Builder and tools intended to automate remediation, reporting and operational workflows under customer-defined controls.
Why add data observability?
Metaplane, acquired in 2025, extends monitoring into the data lifecycle so data teams can identify quality issues and connect them with software and infrastructure context.
Why add experimentation and product analytics?
Eppo, also acquired in 2025, adds feature management, experimentation and product analytics, linking software delivery decisions with operational context and user-behavior signals.
The expansion is documented in Datadog's DASH 2026 announcement, Metaplane acquisition and Eppo acquisition.
The Q2 2026 results added another signal: Datadog acquired Adaptive ML to support AI research focused on world models and agentic LLM post-training for observability. These moves do not prove that every new AI capability will produce durable incremental revenue, but they show where product investment is being concentrated and why the company is trying to make autonomy a layer across the platform rather than a separate tool.
Datadog serves organizations across sizes and industries, but the operative audience is defined by responsibility rather than sector. Developers, SRE and operations teams, security teams, data and product practitioners use the platform; technical and functional leaders commonly choose or sponsor deployments; the organization purchasing the subscription pays; and the wider business benefits from more reliable and secure digital services.
The buyer map is multi-threaded because one Datadog account can cross engineering, infrastructure, security and business boundaries. A developer may start a technical evaluation, a platform or security leader may standardize the tool, procurement may formalize the commercial relationship, and finance ultimately bears the subscription cost. The same platform can therefore be practitioner-led at entry and executive-sponsored at scale.
| Decision role | Typical actor | Primary job |
|---|---|---|
| User | Developer, SRE, operations, security or data practitioner | Investigate systems, detect issues, analyze telemetry and coordinate operational response. |
| Chooser | Engineering, platform, IT or security leadership | Select standards, approve technical fit and decide how broadly the platform is deployed. |
| Buyer and payer | Customer organization through commercial and procurement processes | Contract for subscription capacity, products and incremental usage under agreed commercial terms. |
| Beneficiary | Digital teams, business functions and application users | Benefit indirectly from improved reliability, security, delivery speed and operational visibility. |
The role map synthesizes Datadog's audience and customer-use descriptions in its 2025 Form 10-K.
The company is geographically broader than its New York headquarters. In the first half of 2026, 27% of revenue came from outside North America based on customer billing address, and Datadog reported sales presence in Amsterdam, Dublin, London, Paris, Seoul, Singapore, Sydney and Tokyo in its June 2026 Form 10-Q. International expansion therefore adds both addressable demand and execution complexity across local selling, support, labor and regulatory environments.
Datadog combines product-led entry with enterprise selling. Free tiers and introductory trials lower evaluation friction, sales engineers support demonstrations and proofs of concept, direct sellers pursue larger accounts, cloud marketplaces add procurement routes, and customer success teams monitor adoption and renewal risk. Retention is then reinforced by usage growth and cross-product adoption rather than by contractual lock-in alone.
That mix is important because Datadog's agreements do not force customers to renew after their term. The company must repeatedly earn renewal through product utility, performance, price and breadth. Its trailing twelve-month dollar-based net retention rate was in the low-120% range at June 30, 2026, indicating that the retained cohort expanded in aggregate, but the metric can move with customer optimization and workload changes.
Free tiers, trials, content and practitioner awareness create low-friction paths into product evaluation.
Sales engineers use demonstrations and proofs of concept to test technical fit and value.
Customers buy subscriptions through direct commercial relationships or selected cloud-provider marketplaces.
Customer success monitors usage, adoption and renewal risk while teams add workloads and products.
Channel mechanics are supported by Datadog's sales-engineering role, customer-success role and annual-report disclosures on free trials, direct sales and marketplaces.
Marketplace distribution is strategically useful but economically different from direct selling. Datadog warns that a rising share of marketplace transactions could reduce direct commercial relationships and lower margins on those sales. That trade-off captures the broader channel logic: meet customers where they buy cloud software, while preserving enough direct engagement to understand needs, support adoption and expand accounts.
Competition is product-specific because Datadog spans categories that were historically separate. A buyer evaluating application performance may compare it with Dynatrace, New Relic or Cisco; a log buyer may compare Elastic or Cisco; a cloud-monitoring buyer may use AWS, Azure or GCP native tooling; and some organizations can build or assemble open-source and home-grown alternatives.
The shared decision boundary is whether a customer wants one integrated, cloud-agnostic platform or a narrower category tool, native provider service, internal stack or open-source combination. Datadog emphasizes unified context, multi-cloud support, deployment simplicity, integrations and a broad product set. Rivals can be stronger in particular categories, existing platform relationships, cloud-native economics or internal customization, so no single comparison applies across every Datadog product.
| Alternative | Primary overlap | Comparability limit |
|---|---|---|
| Dynatrace, New Relic, Cisco | Application performance monitoring and broader observability workflows | Feature breadth and platform scope differ by vendor and product generation. |
| Elastic and Cisco | Log management, search and related operational analysis | Buyers may compare only log workloads rather than the whole Datadog platform. |
| AWS, Azure and GCP native tools | Monitoring resources and services inside major public clouds | Native tools align to their clouds; Datadog positions across multi-cloud environments. |
| IBM, Microsoft and SolarWinds | Infrastructure monitoring, especially traditional or on-premises estates | Legacy infrastructure scope can differ from cloud-native application observability needs. |
| Open-source and home-grown stacks | Monitoring, logs, dashboards and telemetry assembled internally | Internal control can trade against integration, maintenance and operating burden. |
Competitor names and category boundaries come directly from Datadog's 2025 Form 10-K competition disclosure.
Competition also intersects with partnership. AWS, Azure and GCP can be alternatives in cloud monitoring while cloud-provider marketplaces can distribute Datadog. This creates a coopetition dynamic: platform providers are simultaneously infrastructure suppliers, procurement channels, integration partners and competitors. The practical competitive question is therefore not simply which vendor has more features, but which combination best fits a customer's architecture, buying path, operating model and desired degree of vendor consolidation.
Datadog's growth engine has four observable parts: adding customers, expanding usage inside existing accounts, selling more products per customer, and extending the platform into new use cases and geographies. Q2 2026 revenue rose 36% year over year, with about 70% of the increase attributed to existing customers and 30% to new customers.
GAAP revenue more than tripled from 2021 through 2025 under the same consolidated subscription-software business.
Annual revenue comes from Datadog's 2022 Form 10-K for 2021-2022 and 2025 Form 10-K for 2023-2025.
Within the installed base, breadth is still increasing. At June 30, 2026, about 85% of customers used at least two products, 58% at least four, 37% at least six, 22% at least eight and 13% at least ten. Those nested adoption figures show a platform that is increasingly monetized through cross-product penetration, not just through higher volumes in the first product a customer buys.
How does existing-customer expansion contribute?
Higher monitored workloads and additional products increase usage and subscriptions inside established accounts, making the installed base a primary source of incremental revenue.
Where can new demand come from?
Datadog continues to add customers, expand direct sales internationally and pursue EMEA and APAC, where the company still sees room for broader adoption.
What creates new expansion surfaces?
AI, security, data observability, developer workflows and experimentation add use cases that can attract new buyers or extend Datadog across existing organizations.
Current growth mechanics and product-adoption figures are detailed in Datadog's June 2026 Form 10-Q, while the Q2 2026 results provide the labeled full-year guidance.
As of August 6, management guided full-year 2026 revenue to $4.45 billion-$4.47 billion. That range is company guidance, not an actual result, and remains contingent on customer demand, usage patterns and execution through the rest of the year.
Growth also requires sustained investment. Datadog continues to spend heavily on research and development, direct sales and international coverage. The strategic implication is that product breadth alone is insufficient: the company has to convert new capabilities into customer adoption while preserving reliability, controlling data-processing costs and maintaining a sales motion capable of expanding within large enterprises.
Olivier Pomel remains chief executive officer and co-founder, while Alexis Lê-Quôc remains chief technology officer and co-founder. The operating team also includes functional executives responsible for finance, operations, product and marketing. The board oversees the company on behalf of shareholders; management executes strategy, with the founders retaining both executive roles and meaningful voting influence.
The founder pairing creates continuity between product architecture and corporate leadership: Pomel carries the top executive mandate, while Lê-Quôc anchors technology. Around them, Datadog has added executives with enterprise SaaS, cloud, product and go-to-market backgrounds. That matters as the company moves from a developer-centric monitoring product toward a multiproduct platform sold into larger and more cross-functional accounts.
| Leader | Role | Primary responsibility | Relevant experience |
|---|---|---|---|
| Olivier Pomel | CEO and co-founder | Top operating authority, strategy, resource allocation and overall company execution. | Former Wireless Generation technology leader; earlier IBM engineering roles. |
| Alexis Lê-Quôc | CTO and co-founder | Technology direction, architecture and long-term engineering capability of the platform. | Former Wireless Generation operations director; IBM Research and Orange engineering. |
| Adam Blitzer | Chief Operating Officer | Operating execution across the scaling enterprise SaaS organization and cross-functional processes. | Former Salesforce executive; co-founded B2B marketing platform Pardot. |
| Yanbing Li | Chief Product Officer | Product strategy and portfolio development across Datadog's expanding platform and use cases. | Former Google Cloud product and engineering leader; VMware executive. |
| David Obstler | Chief Financial Officer | Finance, planning, capital management, reporting and public-company financial discipline. | Prior CFO roles in enterprise software and financial-information businesses. |
| Sara Varni | Chief Marketing Officer | Go-to-market marketing, positioning and connection between developer adoption and enterprise demand. | Former CMO at Attentive and Twilio; long Salesforce tenure. |
Executive roles and biographies come from Datadog's leadership page, while governance and executive-officer status are cross-checked against the 2026 proxy statement.
Oversight is distinct from ownership and management. Shareholders elect directors under the dual-class voting structure; the board and its committees provide governance oversight; executives operate the business. Because Pomel and Lê-Quôc are both directors, executives and significant Class B holders, Datadog has more founder continuity than a company where founders have stepped away from either management or voting control.
Datadog's main constraints follow directly from its cloud-scale, usage-sensitive model. It depends substantially on third-party hosting infrastructure, must retain trust while processing sensitive operational data, and can experience material revenue variability when large customers optimize usage. It also needs continuous product and integration work because the underlying cloud, AI and security technology stack changes rapidly.
The Q2 2026 filing illustrates how operational dependencies reach the income statement. Third-party cloud infrastructure hosting and software costs increased materially, contributing to lower gross margin year over year. At the same time, the company's largest customer reduced usage beginning in the third quarter of 2026; Datadog said this could cause revenue growth to decelerate. The AI-native customer cohort that included that customer had contributed high-single-digit percentage points to Q2 year-over-year growth, making the usage change strategically relevant even without traditional customer concentration disclosure.
Why does cloud infrastructure matter financially?
Datadog outsources substantially all cloud-solution infrastructure, so provider capacity, outages, pricing and processing efficiency affect service quality, onboarding capacity and gross margin.
How can usage concentration create volatility?
Large, fast-growing customers can contribute disproportionately to incremental growth, but optimization or lower consumption can quickly reduce usage-sensitive revenue even when subscriptions remain active.
Why is technical change a standing dependency?
More than 1,000 integrations must keep pace with evolving clouds, databases, developer tools, AI systems and security requirements, making compatibility and R&D execution continuous obligations.
These constraints are described in Datadog's June 2026 Form 10-Q.
Other dependencies reinforce the same pattern. Security incidents could damage trust in a platform designed to centralize operational and security telemetry; marketplace distribution can pressure margins and weaken direct commercial relationships; and global expansion adds labor, regulatory and localization complexity. These are not separate from growth—they are the operating costs of Datadog's strategy to become a broader, more deeply embedded cloud software platform.
Datadog today is best understood as a founder-influenced public SaaS platform whose economic flywheel links telemetry scale, fast product adoption, customer usage and cross-product expansion. Its strategic challenge is to keep widening the platform into security, data and AI while preserving the reliability, cost efficiency and customer trust that made the original observability proposition valuable.
The company is no longer defined by a single monitoring category. Its current shape combines a broad technical data plane, more than 20 products, a product-led and enterprise sales motion, dual-class governance, active acquisition and AI development, and an international customer base. These elements reinforce one another, but they also make execution more interdependent.
Easy entry creates initial usage; growing workloads and additional products deepen customer accounts; recurring subscriptions convert that technical adoption into expanding revenue.
Datadog is extending one shared telemetry platform across observability, security, developer, data and AI workflows instead of treating those use cases as isolated tools.
The company must turn rapid product breadth and AI investment into durable customer value while controlling infrastructure costs and managing usage volatility.
This synthesis connects the business model, platform scope and risk factors documented in Datadog's 2025 Form 10-K.
Disclaimer
All information, articles, and product details provided on this website are for general informational and educational purposes only. We do not claim any ownership over, nor do we intend to infringe upon, any trademarks, copyrights, logos, brand names, or other intellectual property mentioned or depicted on this site. Such intellectual property remains the property of its respective owners, and any references here are made solely for identification or informational purposes, without implying any affiliation, endorsement, or partnership.
We make no representations or warranties, express or implied, regarding the accuracy, completeness, or suitability of any content or products presented. Nothing on this website should be construed as legal, tax, investment, financial, medical, or other professional advice. In addition, no part of this site—including articles or product references—constitutes a solicitation, recommendation, endorsement, advertisement, or offer to buy or sell any securities, franchises, or other financial instruments, particularly in jurisdictions where such activity would be unlawful.
All content is of a general nature and may not address the specific circumstances of any individual or entity. It is not a substitute for professional advice or services. Any actions you take based on the information provided here are strictly at your own risk. You accept full responsibility for any decisions or outcomes arising from your use of this website and agree to release us from any liability in connection with your use of, or reliance upon, the content or products found herein.