Oracle Software / SaaS Global

Sphere Holdings

Document Processing · Enterprise Knowledge Search

Sphere needed a cost-effective but enterprise-grade data platform for its OrgBrain AI offering that could handle massive mixed-format data sets, support AI retrieval and generation, and satisfy stringent customer security and data residency requirements without forcing a small startup team to stitch together multiple specialty databases.

A first draft of a notice of funding opportunity dropped from a week or two to about five minutes
Processing time reduced from minutes to seconds

Reported impact

Business outcome

Sphere launched an enterprise AI platform without assembling multiple specialized databases, kept a lean development model, and sped regulated customer workflows such as grant proposal drafting from as long as one to two weeks to about five minutes while maintaining strong security and data residency controls.

  • Compliance
  • Productivity Improvement
  • Scalability

Solution

Sphere built its OrgBrain platform on Oracle Database running in Oracle Autonomous Database so one converged system could store and query relational, vector, spatial, JSON, and graph data without the operational burden of separate engines. Enterprise knowledge sources and diverse file types are centralized in Autonomous Database, where Oracle AI Vector Search and native large language model integration power retrieval across documents, audio, video, and structured records. Oracle REST Data Services exposes the database model to applications quickly, while Oracle JSON Relational Duality Views lets developers work with JSON representations backed by relational storage. The result is a secure, scalable AI platform with one data-layer security architecture that can support regulated enterprise workflows such as grant proposal drafting and compliance-oriented decision support.

Data flow

Enterprise documents, audio, video, and other knowledge sources are stored together in Oracle Autonomous Database; Oracle AI Vector Search and integrated LLM capabilities retrieve and rank relevant content; Oracle REST Data Services and JSON Relational Duality Views expose the results to OrgBrain applications that generate outputs such as evidence-based grant proposal drafts and governance workflows.

Solution architecture

5 components · 2 layers
  1. Storage
    • Oracle Database Provides the core database engine behind OrgBrain's converged data model for enterprise knowledge and workflow content.
    • Oracle Autonomous Database Runs the platform's centralized, self-managing repository for relational, vector, spatial, JSON, and graph data with enterprise security controls.
  2. Serving
    • Oracle AI Vector Search Executes semantic retrieval over vectorized enterprise content to support fast AI-assisted search and drafting workflows.
    • Oracle REST Data Services Maps OrgBrain data models into application objects and APIs, accelerating delivery for the small development team.
    • Oracle JSON Relational Duality Views Lets developers work with JSON-style objects while keeping data stored efficiently in relational structures.

Architecture clues

  • Converged database supports relational, vector, spatial, JSON, and graph data types
  • Security and permissions are managed at the core data layer for regulated customers
  • Sphere evaluated multi-database alternatives but chose a single-database architecture

Evidence from the source

Sphere created an AI platform using a single database that can draw on different data formats, including relational, vector, spatial, JSON, and graph.
The database’s AI Vector Search capability processes thousands of substeps in queries, reducing processing time from minutes to seconds.
government agencies using Sphere could cut the time to create a first draft of a notice of funding opportunity from a week or two to about five minutes.
Transparency Evidence & methodology 75/100 reference value · 72% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value75/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact0/25
    0 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence72%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence15/20
    3 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity8/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Oracle

    Sphere Holdings customer story

    First-party
    https://www.oracle.com/customers/sphere/
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • First archived Sep 26, 2025 · Internet Archive · Independent First Wayback Machine capture; confirms the page existed by this date, not when it was published.
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.