Capella iQ Treats Model Choice As Configuration Backed By A Continuous Benchmark Loop

Capella iQ separates tenant and provider configuration from application logic, uses private Bedrock connectivity and cross-region inference, and continuously benchmarks models before promotion.

Retrieval answer

The production path runs from EKS through a VPC endpoint to Bedrock, with namespace-level model settings and region failover. The reported 76 percent accuracy is an internal Couchbase/AWS evaluation, not an external universal score.

New Runtime synthesiseditorial-diagram
A whiteboard production architecture showing tenant configuration, private model invocation, cross-region inference, and a continuous benchmark-and-promotion loop.
New Runtime synthesis from How Couchbase built a multi-model AI architecture for Capella iQ with Amazon Bedrock.New Runtime synthesisOriginal source ->

Field note

Couchbase's Capella iQ architecture treats model selection as a configuration decision rather than a code rewrite. API services assemble prompts and context; namespace configuration carries tenant preferences and provider overrides; a private VPC endpoint invokes Amazon Bedrock; cross-region inference distributes traffic and handles regional degradation.

Provider abstraction is backed by evaluation. Couchbase built a suite across SQL++ generation, index recommendations, query explanations, insights, and multi-turn conversation, scoring correctness, determinism, latency, and formatting. Claude Sonnet 4.5 reached about 76 percent accuracy in that internal evaluation; the number should remain a Couchbase/AWS claim tied to this workload.

The durable pattern is a continuous qualification loop. New models enter standardized tests, normalization, controlled traffic, failover exercises, and observability before promotion. Multi-model readiness is not a single gateway integration; it is ongoing investment in prompt contracts, benchmarks, routing, resilience, and rollback.

Recommendation

Capella iQ separates tenant and provider configuration from application logic, uses private Bedrock connectivity and cross-region inference, and continuously benchmarks models before promotion.

Discovery graph / next reads

Continue through New Runtime

Open the graph
  1. 01topicMulti Model - New RuntimeExplore the multi-model topic hub.
  2. 02topicModel Routing - New RuntimeExplore the model-routing topic hub.
  3. 03topicResilience - New RuntimeExplore the resilience topic hub.
  4. 04archiveField NotesOpen the latest editorial analysis.
  5. 05source ledgerSource LedgerInspect the public source evidence graph.

These links are also published in this page's JSON twin and as typed edges in DiscoveryGraph v1.

Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract