Public GitHub means public GitHub
The first repository connector only accepts a public GitHub URL. Do not add private material to a public repository to work around this limit.
Current data and access boundaries
The first connector accepts one public GitHub repository. Bounded document uploads stay inside the workspace. Krynia keeps source versions for indexing and links answers back to the material it used.

What the boundary means
GitLab, Drive, Slack, Confluence and private repositories are not available yet. Krynia does not claim to inherit their permissions or search their content.
The first repository connector only accepts a public GitHub URL. Do not add private material to a public repository to work around this limit.
GitHub links point to the commit Krynia indexed, so the evidence behind an earlier answer does not silently change with the default branch.
A replacement generation is prepared separately. The last successful version remains searchable until the new one is complete.
Prompts, retrieved source context, embeddings and answers are used to provide the service and are not used to train AI models.
How material is handled
Connect one public GitHub repository or upload a bounded set of Markdown, text or simple CSV documents.
Krynia stores the source material and version information needed to prepare and later remove the searchable index.
Only a focused set of indexed sections is used to prepare the answer instead of passing every stored document to the model.
The response links to the material used so a workspace member can inspect it before relying on the answer.
What the boundary means
Topics, source links and access-aware relationships.

Google, Microsoft, passkeys and one-hour email links cover account access and recovery.
An invitation can only be redeemed by an account using the same verified email address.
Only the owner can assign or remove an administrator. Administrators cannot change another administrator.
Removing a source deletes its vectors and stored source artifacts before its workspace record disappears.
Private GitHub, GitLab, Drive, Slack, Confluence and SharePoint require separate connector work.
Krynia does not claim certifications or contractual compliance commitments that have not been completed.
No. Krynia retrieves a focused set of relevant indexed sections for the current question instead of sending every stored document.
Krynia removes the source's indexed vectors and stored artifacts, then removes the source record from the workspace.
Not yet. The current GitHub connector accepts one public repository. Private repositories need a separate authenticated connector.
No. Default routes use hosted open-model infrastructure and customer prompts, source context, embeddings and answers are not used to train AI models.
No. Krynia stays honest: strong product guardrails first, then formal security reviews, regional commitments, SSO/SAML, SCIM and SLA as enterprise requirements justify them.
Start with the current boundary