Skip to content

README: replace outdated hosted key-isolation limit; note MySQL port #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
PradipNichite merged 1 commit into from
Oct 22, 2026
Merged

README: replace outdated hosted key-isolation limit; note MySQL port #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 11 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -141,16 +141,23 @@ requires HTTPS, matching login origin, secure cookies, and private datastores.

Use read-only source credentials: the existing execution path is not a general
SQL sandbox. Review generated queries and results. Query-time descriptions do
not automatically include PostgreSQL table comments.
not automatically include PostgreSQL table comments. PostgreSQL connections
accept any TCP port; MySQL connections are accepted on port 3306 only.

Flat and nested stacked-bar responses render through the same live and saved
conversation path. Stacked charts preserve individual series values, explicit
zeros and missing series. Invalid segmented data shows an explanation while
the supplied Data, Query and Raw views remain available.

Standalone login is for one operator. Broader hosted provider-key isolation,
shared website widget assets, and the retired external report-consumer lane
remain separate work. The in-process report option is included. Targeted
Standalone login is for one operator. On the hosted service (2026-10-22), each
account uses either its own provider keys or the platform key, set per account.
An account on its own keys uses them for setup, questions, charts and
embeddings, and gets a clear error, with no fallback to the platform key, when
its key is missing. That was verified on one bounded hosted journey: one
answered and one refused question, using a temporary key. It is not a load or
multi-tenant security assessment. Shared website widget assets and the retired
external report-consumer lane remain separate work. The in-process report
option is included. Targeted
installation checks do not establish general benchmark accuracy or load capacity.

## License and provenance
Expand Down
Loading