From first clone to governed operation.

Provider routing: OpenAI-compatible, OpenRouter-style, Azure OpenAI chat completions, and Anthropic messages have runtime adapters. A registered provider can still report Adapter needed ; Amazon Bedrock is the documented example.
Connectors: configuration surfaces and tests are not blanket proof of end-to-end ingestion. Architecture notes identify Box as the first concrete client pattern and call out broader Google Drive, OneDrive, and iManage production clients/OAuth/ACL-preserving ingestion as continuing work.
SAML: visible but deferred; OIDC is the working sign-in protocol. SCIM is provisioning, not interactive sign-in.
Decks: saved locally on the device until export; they are not server-persisted documents.
Usage: token or cost figures appear only when providers report them. Unreported data stays labeled, never estimated as authoritative.

A searchable, collapsible field guide to Aperture Chat: source access, deployment, day-to-day use, tenant administration, platform ownership, security, and contribution.

Clone and run How to use this guide Contribute on GitHub

Free to useClone the public repository and begin without requesting repository access.

Self-hosted by designYour organization operates the web, API, model providers, identities, data, and persistent volume.

Source-available termsUse, modify, rebrand, and share freely, subject to application-layer commerce and provenance rules.

No matching subjects

Try a product area, role, control, or action such as “SSO”, “models”, “deploy”, or “memory”.