Enterprise AI, independently operated
Your AI. Your infrastructure.
Your rules.
One workspace for chat, documents, agents, and knowledge, running on infrastructure you control.
Start with a question worth exploring.
Recorded in Aperture Chat · Waiting time shortened
Read the walkthrough
- Ask. Click Improve prompt, see the loading feedback, and open and scroll the expanded Artemis II request.
- Research. Send a source-grounded request, watch the answer stream, then scroll through NASA photography, the mission narrative, and a rendered route diagram.
- Draft. Click Transfer to Drafts, toggle web sources, and move through the illustrated document’s pages.
- Slides. Click Deck and Convert into slides, move through the converted slides, and open speaker notes. The editor follows the page’s light or dark theme.
- Team. Filter approved models, open Policies, expand the controls, and scroll through the configuration.
- Platform. Collapse and expand provider connections, switch to the model catalog, filter enabled models, and scroll the results.
Recorded in the actual product, with a visible pointer marking the recorded interactions. Long waits and intermediate editorial work are shortened. The prompt-improver preview is separate from the curated, NASA-grounded request used for the research; matching requests were run in both themes. Source photography keeps its credits in the work. Console actions change the view without changing access policies. Playback does not send model requests or change settings.
Workspace
Less switching.
More getting somewhere.
From a first question to finished work. Explore the real interface, one capability at a time.
Answers with receipts.
Web-grounded chat with real citations and a work trace you can inspect.
- Sources you can follow
- Visible work traces
- Session-level token transparency
The actual product with example data. Features depend on your deployment and access policies. Implementation boundaries
Product film
The whole picture.
In 60 seconds.
How conversation, creation, and control fit together.
Governance
Power where you need it.
Boundaries where they matter.
Platform owners set the ceilings. Tenant admins manage their workspace. People work within explicit grants.
PLATFORM OWNER
Run the platform.
Configure providers, models, and platform-wide policy for the whole deployment.
- Providers & masked API key vault
- Organization-wide model catalog & routing
- Branding & organization controls
- Platform analytics & audit
Platform policy sets the ceiling for tenant access. Tenant settings cannot expand it.
Security
Governance you can inspect.
Not just a promise.
Fail closed.
Deployments require a unique signing secret. Development shortcuts stay off.
CredentialsKeep keys controlled.
Masked by default. Only owners reveal, rotate, or delete provider keys.
AccountabilityFollow the trail.
Audit records, analytics, and CSV export for administrative activity.
IdentityBring your identity.
OIDC for Entra ID, Google Workspace, and Okta, with SCIM provisioning.
ConnectionsRead the real status.
Connection tests report what the provider actually returned.
InfrastructureOwn the foundation.
Your servers, your data, and outbound access limited to approved hosts.
Documentation
Find your way.
Then make it your own.
Guides for every role, from your first chat to a production deployment.
Open the guideClone it. Run it. Improve it.
Free to use. Adapt it, run it on infrastructure you control, and contribute improvements back.
Clone the public source
Start directly from the GitHub repository.
Configure a real deployment
Set a unique signing secret and bring your own model providers.
Make it fit your organization
Identity, model policy, connectors, roles, and branding.
Contribute through dev
Open a focused pull request to dev; changes
promote through test to main.
Use, study, copy, modify, and share under the Aperture Chat Community Source License.
- Public repository and source access
- Internal use, modification, rebranding, and forks
- Public distribution with license and provenance
- Bona fide AI-token commerce, including markup
- No paid commercialization of the application layer
Understand the Community Source terms Read controlling license
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.
Distribution
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.
Commerce
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.
Branding and warranty
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.
Make it yours