Augment Inc. was founded in 2022 by Igor Ostrovsky and Guy Gur-Ari and emerged from stealth in April 2024. The company announced a $25 million Series A followed by a $227 million Series B, for $252 million in total funding and a $977 million post-money valuation. Scott Dietzen led the company as CEO in the funding announcement. Augment is private and has not published audited revenue or ARR, so external revenue estimates should be treated as estimates. Its product evolved from context-aware IDE assistance into Auggie, code review, Context Engine services, Intent, and the Cosmos enterprise agent orchestration platform. The careers page reported more than 160 employees across four locations in August 2026.
- Founded in 2022. Co-founders are Igor Ostrovsky and Guy Gur-Ari.
- Total announced funding is $252 million. A $25 million Series A preceded a $227 million Series B.
- The announced post-money valuation was $977 million. That figure dates to April 2024.
- Revenue is undisclosed. Pricing, customer logos, hiring, and funding do not establish ARR.
- The product has moved up the stack. Context-aware coding became agents, retrieval services, review, Intent, and Cosmos.
- Careers data changes quickly. The live page showed 160+ people and four locations when checked in August 2026.
Company facts at a glance
| Fact | Verified public record |
|---|---|
| Legal and operating name | Augment Inc.; product brand Augment Code |
| Founded | 2022 |
| Co-founders | Igor Ostrovsky and Guy Gur-Ari |
| Leadership named at funding | Scott Dietzen as CEO; Dion Almaer among the industry veterans leading the company |
| Headquarters in announcement | Palo Alto, California |
| Series A | $25 million, led by Sutter Hill Ventures |
| Series B | $227 million, announced April 24, 2024 |
| Total announced funding | $252 million |
| Series B post-money valuation | $977 million |
| Revenue | No audited revenue or ARR publicly disclosed |
| Team size | 160+ on the live careers page in August 2026 |
| Current product center | Cosmos, Context Engine, Auggie CLI, Code Review, Intent, and enterprise workflows |
The company emerged from stealth with an unusually large Series B relative to its public product maturity. The investor group named in the announcement included Sutter Hill Ventures, Index Ventures, Innovation Endeavors, Lightspeed Venture Partners, and Meritech Capital. The capital was allocated to product, engineering, and go-to-market expansion.
Igor Ostrovsky previously served as chief architect at Pure Storage and worked as a software engineer at Microsoft. Guy Gur-Ari came from AI research at Google. The funding release described Scott Dietzen's leadership history across Pure Storage, Yahoo, and WebLogic or BEA Systems, and Dion Almaer's background across Google, Shopify, Mozilla, and Palm. Those details support the enterprise systems and developer-tool orientation of the founding team.
Funding and valuation math
Augment announced a $227 million Series B at a $977 million post-money valuation. Post-money means the stated company value immediately after the new capital enters. Simple subtraction implies a $750 million pre-money valuation for that financing: $977 million minus $227 million.
That arithmetic does not reveal the price of every share, liquidation preferences, employee option value, investor protections, secondary sales, or the ownership of individual founders. It is a high-level financing figure. Calling the company a unicorn would also be imprecise under a strict $1 billion threshold because the announced post-money value was $23 million below it.
| Item | Amount | Meaning |
|---|---|---|
| Series A | $25M | Earlier capital led by Sutter Hill Ventures |
| Series B | $227M | New capital announced in April 2024 |
| Total funding after Series B | $252M | Series A plus Series B |
| Post-money valuation | $977M | Announced company value after the Series B |
| Implied pre-money valuation | $750M | Post-money valuation minus new Series B capital |
| New Series B capital as post-money share | About 23.2% | Simple $227M divided by $977M, before considering detailed terms |
A large financing can buy time to build expensive indexing, model infrastructure, enterprise security, sales, and support before revenue covers the cost. It also raises the outcome expected by investors and employees. Augment's later pricing changes cited costly heavy-agent usage, which is consistent with a business operating model inference and compute at scale. Funding capacity does not remove unit economics.
Valuation should therefore be read as a dated investor agreement about expected future value. It says sophisticated investors were willing to finance the company at that level in 2024. It does not prove current product quality, profitability, revenue growth, cash balance, or a price at which common stock can be sold today.
What is known about revenue
Augment has not published audited revenue, annual recurring revenue, gross margin, net retention, cash burn, or profitability in the primary company sources reviewed here. It is a private company, so it does not file the public quarterly financial statements expected from a listed corporation.
Several public signals show commercial activity. The pricing page offers Business and Enterprise plans. The company lists customers and users from recognizable organizations. It maintains a sales team, support policy, security certifications, and enterprise deployment options. It has more than 160 employees according to the careers page. None of those signals resolves a revenue number.
| Public signal | What it supports | What it cannot prove |
|---|---|---|
| Business and Enterprise pricing | There is a commercial product and monetization model | Number of paying customers or realized revenue |
| Customer logos and case studies | Named organizations have used or evaluated the product | Contract value, duration, paid status, or company-wide deployment |
| $252M funding | Investors supplied substantial capital | Sales, ARR, profit, or cash remaining |
| 160+ employees | The company built a sizable operating team | Revenue per employee or sustainable burn |
| Usage-based pricing changes | Inference and compute costs matter to the business | Gross margin or overall unit economics |
| Traffic or extension installs | Audience or adoption interest | Paid conversion and retained revenue |
Third-party databases sometimes publish revenue ranges based on web traffic, employee count, job listings, comparable companies, or private submissions. Those can be useful for prospecting and market models. They are estimates unless the company confirms them or a financial document substantiates them. A factual Augment Code revenue answer is therefore: undisclosed.
A procurement team does not need invented ARR to evaluate vendor durability. Ask Augment for audited statements or a financial viability letter under NDA, customer concentration, runway, insurance, escrow or data export provisions, change-of-control terms, service levels, and the migration path if a product is retired. Those are direct controls on customer risk.
How the product changed
Augment's history is easier to understand as a steady expansion around one technical thesis: software agents need better codebase context. The delivery surface changed as the industry moved from completions to agents and from individual use to organization workflows.
| Date | Public milestone | Strategic movement |
|---|---|---|
| 2022 | Company founded | Build developer AI around codebase understanding |
| April 2024 | Emerged from stealth with $227M Series B | Fund product, engineering, and go-to-market |
| October 2024 | Public product introduction | VS Code and JetBrains assistant for large codebases |
| April 2025 | Augment Agent announced | Move from suggestions to multi-step task execution |
| June 2025 | Remote Agents generally available | Parallel containerized cloud workers from VS Code |
| September and October 2025 | Individual and credit pricing changes | Align price with variable agent and model cost |
| December 2025 | Augment Code Review launched | Use full-repo retrieval in pull request review |
| February 2026 | Context Engine MCP released broadly | Sell retrieval as a service for outside agents |
| March 2026 | Intent development and completions sunset | Prioritize coordinated agent work over predictive typing outside Enterprise |
| Mid 2026 | Cosmos leads company site | Organization-scale orchestration across the software development lifecycle |
The completion sunset is the clearest product signal. Augment said forward-looking developers were shifting toward agents, so it ended Next Edit and Completions for Indie, Standard, Max, and legacy users on March 31, 2026 while maintaining Enterprise support for then. The product ceased competing mainly on keystroke prediction and moved toward task, review, and workflow ownership.
Remote Agents show the migration cost. The 2025 product ran up to several independent cloud workers from VS Code. The current analytics documentation marks Remote Agent measures deprecated, while Cosmos now describes scheduling, sandboxes, shared files, experts, and triggers. Customers should ask whether sessions, APIs, logs, metrics, and workflow definitions migrate cleanly.
Intent represents the developer-facing coordination path. Its macOS workspace attaches a spec, repository, staged changes, files, terminals, activity, and specialist agents to one goal. Cosmos represents the platform path, turning review, incident response, migration, testing, ticket-to-PR, and other workflows into managed experts.
Current business model
The August 2026 public offer has two plan families. Business costs $100 monthly for up to 50 seats and includes $100 of pooled usage. Enterprise is custom for higher scale, security, deployment, and support. Model inference is charged at provider public API list price plus a 40 percent service fee. Context Engine and Cosmos compute also consume the shared balance, with compute metered without the model fee.
| Revenue component | Customer receives | Economic driver |
|---|---|---|
| Business subscription | Seats, platform, Context Engine, agents, tools, analytics, Cosmos, and security features | Workspace count and retention |
| Model service fee | Access to routed model inference within Augment workflows | Model token volume and provider price |
| Context Engine usage | Indexing and retrieval for agents and apps | Query and workflow volume |
| Cosmos compute | Agent execution environments and concurrency | Machine size, runtime, and number of sessions |
| Enterprise contract | Custom users, usage, controls, deployment, support, and discounts | Scale, requirements, and negotiated term |
| Professional support and services | Dedicated support and deployment assistance where contracted | Enterprise agreement |
The model mixes software subscription and consumption. Seat inclusion encourages broad organizational adoption, while active agent use generates variable revenue and cost. The 40 percent service fee creates a visible gross revenue layer above model provider charges. Context and compute can become larger parts of the bill as organizations automate more work.
This structure also reduces the mismatch between light and heavy users that Augment described under message plans. A tiny edit and a long agent task no longer consume an identical nominal message. The tradeoff is budget variability. The buyer needs usage dashboards, limits, top-up policy, workload forecasting, and enough accounting detail to attribute spend by team and workflow.
Customers, market, and competition
Augment targets professional engineering organizations, especially large codebases, several repositories, long-lived systems, security-sensitive environments, and teams adopting many agents. The current pricing page displays organizations including Adobe, MongoDB, Pure Storage, DXC, DDN, Tekion, Snyk, MoneyGram, Crypto.com, Webflow, and Pigment. A logo indicates a relationship or approved marketing reference. It does not specify the commercial scope.
The competitive set changes by product layer. Cursor and GitHub Copilot compete for editor adoption. Claude Code and Codex compete with Auggie for terminal and task execution. CodeRabbit, Cursor BugBot, and other reviewers compete with Augment Code Review. Sourcegraph and internal search platforms overlap with Context Engine. Factory, Devin, and enterprise agent platforms overlap with Cosmos. Intent competes with emerging multi-agent workspaces.
| Layer | Augment position | Competitive pressure |
|---|---|---|
| Editor | Extension in established IDEs | Cursor owns an integrated editor; Copilot distributes through GitHub and major IDEs |
| Agent | Auggie with several model families | Model vendors bundle capable agents into existing subscriptions |
| Context | Proprietary semantic retrieval exposed by MCP and SDK | Editors improve native indexes; code intelligence and open retrieval advance |
| Review | Repository-aware review and Cosmos fleet | Review tools compete on precision, recall, workflow, and price |
| Orchestration | Intent for team work and Cosmos for organization workflows | Fast-moving agent platforms and internal engineering systems |
| Enterprise controls | Broad security, identity, deployment, and audit offer | Large incumbents bundle governance with existing contracts |
Augment's defensibility depends on retrieval quality, accumulated organization memory, workflow adoption, enterprise trust, and the cost of moving indexed knowledge and automation. Model choice alone is unlikely to remain defensible because the platform already treats models as interchangeable providers.
Its exposure is the same modularity that creates opportunity. MCP lets customers attach Context Engine to outside agents. It also lets customers replace Context Engine if another retrieval service wins. Cosmos needs to create value in orchestration, memory, controls, and outcomes rather than rely on exclusive access to a frontier model.
Careers and organization
The live careers page reported more than 160 team members across four locations when checked in August 2026. It grouped roles under product and other company functions and emphasized work on agent infrastructure, Context Engine, CLI, Cosmos, security, and enterprise delivery. Open roles change continuously, so the careers page is the only reliable current list.
A candidate should evaluate the same transition visible in the product timeline. Augment is moving from an IDE assistant toward an agent orchestration company. That creates technical work in indexing, distributed systems, model routing, sandboxes, workflow engines, review, security, evaluation, developer experience, sales, and customer operations. It also creates prioritization and migration pressure as older surfaces change.
- Ask which product owns the roadmap. Context Engine, Auggie, Intent, and Cosmos serve related customers and different daily users.
- Ask how product sunsets are handled. Completions and Remote Agents provide concrete migration examples.
- Ask how quality is measured. Retrieval precision, agent task success, review signal, and customer outcomes need separate evaluation systems.
- Ask where models end and Augment begins. The answer defines technical ownership and defensibility.
- Ask about deployment obligations. VPC, on-prem, single-tenant, data residency, and many providers create operational breadth.
- Ask about financial stage. Funding is public, revenue is not, so candidates can request runway and planning context directly.
Job listings establish current hiring intent, not a guarantee that a specific team, manager, location, or compensation band remains available. Use the posting, recruiter, and written offer as the source of record. Ignore unrelated companies named Augment in logistics, supply chain, consulting, or augmented reality when researching roles.
How to assess company durability
Separate disclosed facts from estimates
Record funding, dated valuation, leadership, headcount claims, prices, and certifications with their source dates. Label revenue and current cash as undisclosed.
Map product continuity
List the features your team will depend on and the migration history for adjacent products. Put API, data export, session, and workflow portability into the contract.
Verify operating economics
Pilot actual model, Context Engine, and compute consumption. A vendor with strong funding still needs a product whose unit economics work for both sides.
Check customer concentration and references
Ask for customers matching your size, repository topology, security requirements, and deployment. Speak with them about renewal, support, migration history, and initial quality.
Protect the exit path
Define export, deletion, credential revocation, replacement, and transition assistance before the platform accumulates organization memory and workflows.
Funding gives Augment resources to pursue a technically expensive market. The Context Engine and enterprise controls show real engineering investment. Durable customer value still has to appear in retrieval quality, agent outcomes, renewal, and a product surface that teams can operate through change.
Questions people ask
Augment Inc. is a privately held company backed by founders, employees, and investors. Named investors include Sutter Hill Ventures, Index Ventures, Innovation Endeavors, Lightspeed Venture Partners, and Meritech Capital. Exact ownership percentages are not public.
Igor Ostrovsky and Guy Gur-Ari founded Augment in 2022. Ostrovsky previously worked at Pure Storage and Microsoft. Gur-Ari came from AI research at Google.
The company announced $252 million in total funding: a $25 million Series A followed by a $227 million Series B in April 2024.
Its April 2024 Series B announcement stated a $977 million post-money valuation. That is a dated private financing value. No newer primary-source priced-round valuation was found for this August 2026 guide.
Augment has not publicly disclosed audited revenue or ARR in the primary sources reviewed here. Third-party revenue ranges are estimates and should be labeled that way.
The announced 2024 post-money valuation was $977 million, which is $23 million below a strict $1 billion unicorn threshold. A later internal or secondary value may differ, but no newer primary priced-round figure is cited here.
The company careers page displayed a team size of more than 160 across four locations when checked in August 2026. Headcount changes, so use the live page for a current number.
Use augmentcode.com/careers for the current list. Verify the team, location, manager, compensation, and employment terms in the live posting and written offer because search copies become stale.
Sources
Every figure above was read from these pages on August 2026. Vendors reprice without notice; if you find a stale number, tell us.