10.9. Candidate Decisions

Recorded decisions about proposed additions identify prerequisites for future integration. A proposal does not enable a service.

Dates identify recorded decisions, not fresh upstream qualification. See the Supported service catalog for supported Atlas configuration.

1. Browserless

Lifecycle: deferred. Recorded decision date: 2026-07-04.

Deferred pending a reproducible workflow that needs persistent browser sessions. Resource limits, authentication and license acceptance need a design before adoption.

Upstream project.

2. Docling MCP Server

Lifecycle: planned. Recorded decision date: 2026-07-03.

Planned as a document-tool bridge for agents. Transport, authentication, tool names and use of the existing Docling service need an integration design.

Upstream project.

3. Firecrawl

Lifecycle: deferred. Recorded decision date: 2026-07-04.

Deferred until a reproducible extraction gap justifies an additional crawler deployment. Operational ownership and license acceptance must be decided before adoption.

Upstream project.

4. Honcho

Lifecycle: deferred. Recorded decision date: 2026-07-04.

Deferred until existing memory options cannot meet a named cross-agent workflow. User isolation, consent, retention and deletion need an explicit design.

Upstream project.

5. imgproxy

Lifecycle: deferred. Recorded decision date: 2026-07-04.

Deferred until an asset-browser or media workflow can issue signed preview URLs. The initial design must keep source access and transformation requests controlled.

Upstream project.

6. Keycloak

Lifecycle: deferred. Recorded decision date: 2026-07-03.

Deferred pending an identity-provider choice. Consumer configuration, credential migration and route authentication require a coordinated design.

Upstream project.

7. mcpo (MCP-to-OpenAPI Proxy)

Lifecycle: deferred. Recorded decision date: 2026-07-03.

Deferred pending a curated tool set and an authentication model. Secret delivery, token scope and writable tool storage need an integration design.

Upstream project.

8. NocoDB

Lifecycle: deferred. Recorded decision date: 2026-07-04.

Deferred until a named human-review workflow needs editable operational rows. Review ownership, provenance and authentication must be defined before adding another user interface.

Upstream project.

9. OmniVoice (k2-fsa)

Lifecycle: deferred. Recorded decision date: 2026-07-04.

Deferred until a maintained serving endpoint can support Atlas integration. A library proposal does not establish a supported HTTP service or selectable TTS source.

Upstream project.

10. OpenLIT

Lifecycle: deferred. Recorded decision date: 2026-07-04.

Deferred until a named observability gap justifies another platform. Collector, storage, user-interface and retention ownership must be clear before adoption.

Upstream project.

11. Perplexica (Vane)

Lifecycle: deferred. Recorded decision date: 2026-07-04.

Deferred until Atlas chooses a distinct interface for cited web answers. Provider setup, route authentication, upload storage and overlap with existing applications need review.

Upstream project.

12. Redis Stack (redis-stack-server)

Lifecycle: deferred. Recorded decision date: 2026-07-04.

Deferred until a consumer demonstrates a tested need for module commands. Persistence, memory costs and distribution terms need review before changing the Redis variant.

Upstream project.

13. RedisInsight

Lifecycle: deferred. Recorded decision date: 2026-07-04.

Deferred until an operator workflow justifies another administration interface. Authentication, data exposure, credential handling and distribution terms require review.

Upstream project.

14. Supabase Edge Functions (Deno runtime)

Lifecycle: deferred. Recorded decision date: 2026-07-04.

Deferred until an edge-specific workflow needs another execution surface. Upgrade behavior, authentication and secret ownership need a design before adoption.

Upstream project.

15. Unmute (Kyutai)

Lifecycle: deferred. Recorded decision date: 2026-07-04.

Deferred pending client compatibility and resource qualification. Authentication, session behavior and coexistence with existing speech providers need a design before adoption.

Upstream project.

16. WhisperX

Lifecycle: deferred. Recorded decision date: 2026-07-04.

Deferred until a named audio-ingestion workflow needs speaker labels and word timings. Model access, resource limits, retention and transcript provenance need an integration design.

Upstream project.