Augmented Intelligence

Name: Augmented Intelligence
Brand: Augmented Intelligence

Augmented Intelligence (AUI) provides Apollo-1, a neuro-symbolic model architecture and agent deployment stack that enables task-oriented conversational agents emphasizing controllability, explicit policy enforcement, and traceable decision artifacts.

Est 2017|Valuation $750M|Raised $63.1M|18 Ref Customers

LinkedIn 17K|Web traffic 5K|FTEs 58

MarketsAgent Builder Platforms

Published Oct 23, 2026

01Common complaints

- Early-stage startups or small teams needing a self-serve product - Organizations requiring a low-friction, self-serve tool with transparent monthly pricing may find AUI’s sales-led approach and gated access to be a poor fit. - Organizations with strict procurement compliance requirements - If procurement requires publicly documented SOC 2 Type II or ISO 27001 evidence prior to evaluation, AUI’s currently discoverable public posture may be insufficient unless reports can be provided under NDA. - Teams that need mature, widely reviewed platforms - If the RFP process requires a large body of public, independent end-user reviews and named customer references, established platforms (Kore.ai, Cognigy, Rasa, Dialogflow CX) are likely to provide more references. - Use cases where deterministic rules are not the core requirement - For brainstorming, creative assistants, or open-ended knowledge chat, general-purpose LLM-based approaches are likely to be less expensive and easier to deploy. - Publicly visible limitations - Limited public evidence of formal security certifications (SOC 2, ISO) - Limited independent user reviews specific to AUI/Apollo-1 - Lack of transparent public pricing - Roadmap / availability - AUI’s product page indicated general availability for Q2 2026; if GA is recent or in-progress, expect evolving APIs, packaging, and a limited set of integrations compared with incumbents. - Technical/operational risks buyers should test - Policy correctness under adversarial or ambiguous prompts - Tool execution correctness and error handling in integrations - Completeness and usability of audit logs (who changed what rule, when, and the impact) - Latency and throughput characteristics at peak loads

Deal disqualifiers (poor fit)

Requirement for fully transparent self-serve pricing and immediate onboarding via card payment
Requirement for publicly documented SOC 2 or ISO 27001 evidence prior to any pilot (unless the vendor can provide reports under NDA)
Use cases that are primarily open-ended conversational or generative chat without tool-based actions

02Why they buy

- Potential differentiators (subject to validation) - An architecture that combines generative components with explicit policy enforcement and orchestration - Platform features intended to expose reasoning artifacts or decision traces for audit purposes - Emphasis on controllability and grounded responses by combining rules and model outputs - Where competitors may have advantages - More mature marketplace and partner ecosystems - More visible security and compliance documentation - Larger, publicly visible customer-review footprints

03Field reports

Important limitation

Review platforms often returned results for other products named "Apollo" (for example, Apollo.io) rather than AUI’s Apollo-1. As a result, credible, product-specific end-user reviews for AUI/Apollo-1 were not found on major review sites (G2, TrustRadius, Capterra) in accessible search results.
This gap implies early-stage adoption, gated enterprise deployments, brand-name collisions with similarly named products, or a limited public review footprint.

Available community discussion (HackerNews/Reddit)

A Reddit discussion of AUI’s funding announcement included skepticism about vendor claims and architecture. For example, one commenter suggested that the underlying model likely combines transformer models with a state-machine or orchestration layer.

Vendor testimonials / endorsements (treat as vendor-provided)

AUI’s About page includes a quote from a named industry figure listed as an advisor/investor. This should be treated as vendor-provided material and not independent customer validation.

What would be expected but is missing

Independent customer quotes with named deployments
Third-party case studies with reproducible methodology
Public production reliability metrics or incident history

Public case studies available

AUI provides descriptive examples in documentation (for example, modifying a dispute blocking rule and pushing it live) and describes integrations into existing APIs. These materials are illustrative and were not independently validated as part of this research.

Benchmarks / reported results (critical view)

Press coverage reported Apollo-1 achieving strong results on specific benchmarks. The reported results appear to be based on vendor-shared data and press coverage.
Recommended validation steps for buyers:
- Request the exact benchmark configuration, prompts/policies used, and failure analyses
- Request reproducibility information and fair-comparison details (same tools and constraints)

Methodology gaps

Where metrics are vendor-published, methodology details are often incomplete in public materials. For production decisions, vendors should be asked to support a pilot using organization-specific workflows with clear acceptance tests covering policy compliance, tool accuracy, escalation correctness, latency, and audit logs.

04Best fit

Company sizes

Likely best fit: mid-market to large enterprises (and smaller organizations in regulated industries) with budgets for enterprise AI and governance.

Industries and verticals where adoption is likely strongest

Verticals cited in vendor materials and commonly aligned with policy-bound workflows include:
- Airlines
- Retail
- Banking and insurance
- Healthcare and hospitals (for policy-bound workflows)

Roles and personas

Decision makers
- CIO / CTO
- VP Customer Experience / Contact Center leadership
- Head of AI / Head of Data
- Compliance / Risk / InfoSec in regulated organizations
End users
- Customer support agents (as escalation targets)
- Operations teams managing policies, workflows, and tooling

Pain points and challenges addressed

Reducing unpredictable agent behavior and policy violations
Increasing task completion rates for structured workflows (refunds, booking changes, disputes)
Enforcing business rules while preserving conversational UX for customers

Qualification criteria (good fit)

The organization can clearly define policies and state models for high-volume workflows
Strong integration readiness (APIs, systems of record)
A need for auditability and consistent behavior over open-ended conversational capabilities

05The pitch

What the product does (core value proposition in objective terms)

- AUI (Augmented Intelligence Inc.) offers Apollo-1, a neuro-symbolic model architecture intended for task-oriented conversational agents that prioritize controllability and policy compliance over unconstrained generative behavior. - The product is positioned for agents that act on behalf of an institution (e.g., airlines, banks, insurers) and must follow explicit rules and policies rather than responding solely to user prompts. - AUI also offers an agent deployment stack (widget deployment, conversation analytics) alongside API access and a playground environment.

Target market and market positioning

Target: mid-market to enterprise, especially organizations deploying customer-facing agents where compliance, determinism, auditability, and steerability are priorities.
Positioning: AUI presents its approach as an alternative to transformer-based generative models, asserting that neuro-symbolic architectures address reliability and policy-adherence issues in high-stakes workflows.

Get a comprehensive analysis of Augmented Intelligence including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →