Governed chat, document drafting, agents, knowledge, and automations — one platform, deployed on your infrastructure, serving AI to your whole organization under your rules.
Live product capture
chat.yourcompany.com
No fake states, no demo shortcuts — every screen below is the real product doing real work.
Web-grounded chat with real citations, inline figures and images, work traces on every reply, and session-level token transparency.
Transfer any answer into a full drafting workspace — a real paginated editor with versioning, conversational revision, and Word export.
Reusable profiles that wire a model, instructions, knowledge, and tools into one assistant.
Tenant knowledge bases with vector retrieval and source-level ACL enforcement, cited directly in chat.
Scheduled multi-step model chains over chat and drafts, with honest run status and full transcripts.
Sync full provider catalogs, then control exactly which models flow down to tenants — layered allow, grant, and deny policy at runtime.
Provider posture, key vault metadata, usage analytics, and a full governance audit trail with CSV export — nothing fabricated, ever.
Built for organizations that need a real control plane: platform owners set service-wide ceilings, tenant admins govern their people, and users work inside explicit grants.
The service operator responsible for the deployment.
The workspace manager operating inside owner policy.
Features either really work or clearly say they aren't configured. Errors surface as real errors.
Outside local dev, the API refuses to start without a unique high-entropy signing secret — and dev conveniences are disabled regardless of flags.
API keys are masked everywhere by default. Reveal, rotate, and delete are owner-only actions — keys never reach responses, logs, or audit metadata.
Administrative and chat-governance actions are recorded with analytics dashboards and CSV export — authoritative timestamps included.
OIDC SSO with presets for Entra ID, Google Workspace, and Okta, SCIM 2.0 provisioning, JIT user creation, and IdP group mapping.
Outbound network access in deployed environments is restricted to operator-approved hosts. Your data doesn't wander.
Google Drive, Box, SharePoint, OneDrive, and iManage — each with a real “Test connection” that reports the provider's actual response.
Aperture Chat is free to use. Clone the public repository and start from the source whenever you are ready.
Aperture Chat now grows through its public repository. Use it inside your organization, adapt the interface and workflows, deploy it on infrastructure you control, and contribute focused improvements back through the staged review process.
The source is free to use. Start directly from GitHub, then adapt and operate the workspace for your company.
Create a unique signing secret, bring your own model providers, and keep runtime state in the persistent application-data volume.
Configure identity, model policy, connectors, roles, and branding while preserving the source-level license and provenance requirements.
External contributors fork the project and open a focused pull request to dev; inspected changes promote through test to main.
Use, study, copy, modify, and share under the Aperture Chat Community Source License.
The project is free to use, but it is not OSI-approved open source. Individuals, nonprofits, and commercial organizations may use it internally, create private or public derivatives, and rebrand the application.
Public forks and other public derivatives must keep the complete LICENSE.md and NOTICE.md, preserve existing notices, and identify Aperture Chat as the original codebase in both the root license notice and top-level README.
Selling or reselling bona fide AI-model token usage or credits through the platform is allowed, including a markup. Selling, licensing, hosting, deploying, supporting, consulting on, or white-labeling the application layer for a fee is restricted when the application layer is the material value being sold.
Forks may use their own product name and visual identity; the license grants no trademark rights. The software is provided as-is, without warranty. The repository license controls if any summary differs.
Clone the public source, follow the deployment guide, or contribute a focused improvement through the repository.
Questions, ideas, pull requests, and contribution guidance now live with the project on GitHub.